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 7 months ago
cake
Cake day: February 17th, 2025

help-circle
  • I’ll just remove the ‘freamon’ one when the auto-generated one is up to date.

    The manually-generated one had 5 missing routes, which I’ve since added.

    The auto-generated one at crust has about 48 missing routes. It’s the right approach, and I’ll help out with it when I can, but - for now at least - it makes no sense to redirect people to it (either automatically or via a comment).


    Some thoughts for @wjs018@piefed.social

    /site/instance_chooser probably doesn’t need to be a route. It’s just the data format returned by /site/instance_chooser_search. As a route, it’s returning the instance info for the site you’re querying, so if you want to keep it as a route, it should probably be called /site/instance_info or something.

    In the query for /site/instance_chooser_search, nsfw and newbie are both booleans. With the rest of the API, these are sent as ‘true’ or ‘false’, but they are ‘yes’ and ‘no’ for this route. The newbie query should probably be newbie_friendly In the response, monthsmonitored should probably be months_monitored

    There’s no way to exclude communities for the response to /topic/list and /feed/list: If you don’t put ‘include_communities’ in the query, it’s defaults to True, but if you put ‘include_communities=false’ in the query it ends up being True also (because the word ‘include_communities’ is in the data).


  • What is the update delay for Fediseer?

    I don’t know. It’s not something I’m familiar with - it might just default to saying ‘closed’ if it doesn’t have the data.

    It’s interesting that the obvious bot accounts on those instances were set up in mid-March last year, so I’m guessing that these are somebody’s army that they’ve used before, but overplayed their hand when they turned it on the DonaldJMusk person. The admins can reasonably be blamed for setting up instances with open registrations and no protections and then forgetting about them, but I’d be wary of blaming them for being behind the attack directly. The ‘nicole’ person is unlikely to have used their own instance - it’s probably just someone with the same MO as whoever owns the bots, finding and exploiting vulnerable instances.








  • Clarkson has been trying to warn us for years, and we haven’t been listening. He punched a producer when his dinner wasn’t on time, to highlight the impending delays to food deliveries after Brexit. He left the BBC to work for Amazon, presenting a show that was a shadow of it’s former self, to illustrate how billionaires diminish everything they touch.

    He couldn’t be clearer with his messaging, but the UK continues to ignore him.




  • PieFed is just a Fediverse platform that aims to inter-op with Lemmy in much the same way that it aims to inter-op with any other Group-based platform (MBIN, PeerTube, NodeBB, Wordpress).

    Lemmy’s “quirks” are the reason why your account won’t see Polls from MBIN, or channels from PeerTube, or posts from NodeBB, or backfilled content from Wordpress.

    It’s not my intent to criticise Lemmy, but these are verifiable problems, whereas it doesn’t seem fair to criticise PieFed for problems that you can’t clearly remember.






  • 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.