I am also ‘Andrew’, the admin of this server. I’ll try to remember to only use this account for posting stuff.

  • 0 Posts
  • 22 Comments
Joined 20 days ago
cake
Cake day: February 17th, 2025

help-circle

  • Do all filters have that 3 level system?

    Yes - that Trump/Musk form is just a shortcut to setting up your own filter - the options on that form equate to ‘hide completely’, ‘make semi-transparent’ (so you can see the post, but it’s faded out), or “don’t set up a filter”

    Also, do you know of an alternative front-end for Piefed?

    There’s the one I made (the one linked to by OpenStars), but I think the more promising development is that the Interstellar dev has made some progress supporting PieFed too (Interstellar is already the only app that supports both MBIN and Lemmy, and I like the idea of one app for 3 different platforms).


  • As a term, ‘instance’ is already baked into code, databases, and APIs.

    If I wanted to use an API to block ‘lemmy.world’, for example, I’d call ‘site/block’ with the relevant ‘instance_id’. That’s already 2 different terms for the same thing (‘site’ and ‘instance’), which isn’t great, but adding ‘provider’ into the mix means you’re now saying “if you want to block a ‘provider’, use the ‘site’ endpoint with the ID for the ‘instance’”, which is arguably worse.













  • Yes. PieFed federates with Lemmy, but in much the same way that it federates with MBIN, or PeerTube, or NodeBB. Federation is about the relationship between servers, using a common protocol (ActivityPub) to communicate. A mobile app like voyager is concerned about the relationship between a client and server, who communicate using something they’ve both agreed on (Lemmy’s V3 API in this case). PieFed can’t implement Lemmy’s V3 API (for a whole bunch of reasons), so mobile apps have to use PieFed’s own API to communicate with it (which is what I’m doing right now, as I write this comment).


  • Typically, if you see that one person is being banned from a bunch of communities at the same time, it just means that they are being banned from the instance.

    If an admin wants to ban one of their own users, it’s a single activity that’s federated out, but if they want to ban a remote user, the only way it can be done under the current system is for every community that the banned person has interacted with to ban them. It’s an automatic process, triggered by the admin pressing one button once. (it’s not a perfect solution, because nothing prevents the banned user interacting with other communities, at least as far as their local instance is concerned).





  • No. The app was forked from a Lemmy app (Thunder), so there’s not much PieFed-specific in it (e.g. there’s also no support for Polls). The exception is that it supports post / comment subscribing (I was notified of your comment, even though I’m not the OP of this post).

    I created a new instance for testing the app, and I didn’t create any Topics (partly laziness, partly because the whole area is being re-evaluated for user-created Topics, aka Feeds).

    The app will lag behind the site in features, 'cos adding stuff for direct HTML rendering will always be easier than adding stuff that’s got to come through an API.