aka freamon

Codeberg: https://codeberg.org/freamon?tab=activity

Anything from https://lemmon.website is me too.

  • 4 Posts
  • 94 Comments
Joined 11 months ago
cake
Cake day: March 27th, 2024

help-circle





  • If you fetch a community that your instance hasn’t previously heard of, you can typically query the community’s ‘outbox’ collection to get recent posts. So in Lemmy, you get 50 old posts, and then - once someone has subscribed - new posts start coming in.

    Different platforms have different formats for their outboxes - Lemmy uses Announce/Create/Page, a.gup.pe and PeerTube use Announce, with a URL that leads to a Note or Video, wordpress uses Create/Article. Because Lemmy already understands its own outbox format, it’s able to get old posts from other Lemmy instances. It doesn’t get old stuff for a.gup.pe, PeerTube, or wordpress though.

    So you might be wondering what outbox format nodebb uses - to which the answer is none. The outbox leads nowhere useful (they’re in good company with MBIN on this). Anyway - this is why fetching a nodebb community won’t come with any of its existing posts (but - as mentioned - new stuff will come in for subscribers)


  • I think some people were wanting the finale to be a little longer, but I’m fine with where they left things. I’ll be a bit less fine if there’s no Season 2, so hopefully there is.

    For a show that was literally “Maybe the real treasure was the friends we met along the way”, I’m surprised by how much enjoyed the whole thing. It was very well made, and I imagine that there’s some kids out there who think it’s the best thing ever, so that’s nice.


  • What’s unclaimsies and how badly does it break the lore?

    Skeleton Crew is set in the world of children as much as it’s set in the world of Star Wars, and is concerned as much with pirate lore as it is Star Wars lore. “Claimsies” and “unclaimsies” is just “finders, keepers!” and another child’s attempt to reverse that.

    There’s a key moment in the show where it combines those two concepts - the made-up words and rules of children, with the made-up words and rules of pirates -

    spoiler for episode 7

    A droid decides that a call of “unclaimsies” is “close-enough” to pirate lore that it will let them re-take a ship that’s been commandeered by a pirate.

    It’s all very delightful.



  • I caught up with this over Christmas. It’s surprisingly great. It’s very much a kids show - not in the sense that that phrase is used as a byword for shitness, but more like some of the best entertainment ever made is made for kids (e.g. Paddington 2, or Muppets Christmas Carol, or Bluey, or Princess Bride).

    There’s a lot to like as an adult - the kids act like kids, not weirdly precocious Hollywood brats, it doesn’t over-use the Volume, and it’s primarily reference points aren’t just other Star Wars projects. It was cute to see Aldanhi get a mention, but it’s more interested in evoking things like Peter Pan, the Wizard of Oz, and the various Amblin films (shockingly enough, even stuff that Disney doesn’t own).




  • The use of the word ‘radical’ by these Republicans is grimly interesting and perverse, since I associate this mammalian definition of gender with a subset of radical feminism (the RF in TERF). They presented the idea as liberating (in the sense that since your gender has already been singly defined by your reproductive role, everything else - e.g. your name / job / hobbies / how you present yourself - was irrelevant, and no-one should be able to use any of those to question your gender). I very much doubt that these measures by US politicians will ultimately be liberating for anyone though, since trans people are just the first on a list. (It’s not like no-one warned the ‘gender critical’ gang about who they were cosying up to)







  • We appear to be at an impasse.

    I’ve recently been adding an API to PieFed and forked the Lemmy Thunder app as way to test things. My position on this comes from tinkering with Thunder - I can’t claim to understand it all, but it seems to me that the API and the app are fundamentally interlinked in ways that make being too adventurous with it difficult. For that app, it would break the existing paradigm to do the kinds of things you’re talking about. Thunder uses its own version of an API client (written in Dart), but I’ve assumed that other apps are written in a similar way, and are essentially wrappers around Lemmy’s JavaScript client.

    Hopefully, someone else with more app development experience will contribute to this discussion, and set one of us right (I don’t mind if it’s me that’s wrong).


  • Most frontends already display available crossposts so you’re not wasting anything more than grabbing all the comment sections as well.

    We’re talking about different things. I’m talking about the view you get when you first open an app - the ‘home’ screen that lists the posts. The API response for api/v3/post/list doesn’t indicate whether something has been crossposted. You can see for yourself by getting a list of the 2 oldest posts on lemmy.ml:

    curl --request GET --url 'https://lemmy.ml/api/v3/post/list?type_=Local&sort=Old&page=1&limit=2' --header 'accept: application/json' | jq .

    For those 2 posts, you can only find out if they have crossposts by individually querying each post using the api/v3/post endpoint - the first one in that list would be:

    curl --request GET --url 'https://lemmy.ml/api/v3/post?id=2' --header 'accept: application/json' | jq .

    where crossposts would be in the ‘cross_posts’ array.

    So for an app to display whether a posts listed on the main feed have crossposts, they’d have to query post/list, and then for each entry, query /post as well. This isn’t the way these things typically work - there’s normally a 1-to-1 relationship between an API query, and displaying the results of that query on the page. Looping through the list you’ve been given, and making extra queries adds complexity and delay, when the expectation from the user is that this list should appear pretty quickly.

    What you’re talking about, is the view once a user has clicked on a post, not the post list. This provides the crossposts info. It’s important to realise though, that the cross_posts array provides everything an app could want to display info about the other posts. It’s not like they are pulling the data for one post, and then pulling data for each listed crosspost, so if they were to start getting the comments for each crosspost, that would be an extra effort (and a potential waste).


    I don’t agree at all. There’s space for complex frontends which attempt to adjust the feed according to their own logic, as well as minimalistic frontends which follow the backend’s design explicitly.

    My counter to that, would be that if you aren’t using the API in the way the developers expected, your app has ceased to be frontend, and is instead its own program that’s scraping data from it. There are already some heavy desktop-orientated frontends, and none of them do what you’re proposing. I think that the reason why, is because the proper way to do it is for the Lemmy’s backend to be changed to provide the information they need in one go. That’s unlikely to happen, but that doesn’t mean that hacking away at an improper solution is necessarily the right answer (you just end up supporting a project that isn’t supporting you in return).