I just wanted to confirm from our meeting just now, did you want me to (some crazy shit that could cause problems)?

  • 0 Posts
  • 12 Comments
Joined 6 months ago
cake
Cake day: January 9th, 2024

help-circle

  • Akkoma and Pleroma are two popular “Mastodon style” Fediverse apps, I think born out of exactly this type of complaint about Mastodon, which you could get involved with if you wanted to be involved with better software without it being a one-man show.

    I think it’s made needlessly difficult by how sloppy a protocol ActivityPub is, such that different Fediverse apps can’t really interoperate with each other except at a pretty rudimentary level, so you kind of have to pick one of the leading ones and imitate it, in order to be a citizen in its community and not have to build your own little community from scratch. But that’s a problem without a real easy solution, I think.




  • API docs are at https://lemmy.readme.io/reference/get_post-list - I haven’t tested this, but to me it looks like you can get raw results for what you’ve liked by doing this (for $server set to whatever server address):

    1. Open web developer tools and go to the “Network” tab
    2. Load a page of Lemmy while logged in
    3. Right-click on one of the network requests, select Copy Value -> Copy as curl
    4. Paste the resulting value to command line in a place that has curl; that’ll give you a request that has the right auth tokens and etc
    5. Backspace over the actual URL so you can replace it with the API calls you need
    6. Use --request GET --url "https://$server/api/v3/post/list?liked_only=true" --header 'accept: application/json' to get liked posts as JSON
    7. Use --request GET --url "https://$server/api/v3/comment/list?liked_only=true" --header 'accept: application/json' to get liked comments as JSON

    Edit: Fixed comment link


  • You can make a protocol that allows for not-yet-defined behavior, or has parts that are prescribed to work in a certain way if you’re choosing to implement some certain behavior although you’re not required to. The 7-layer OSI model and SMTP-email headers are two good examples. Even grafting encrypted or multimedia email on top worked, more or less, reasonably well and was still interoperable for the most part. They could have used that type of thing as a starting point, instead of doing the equivalent of “well we don’t want to constrain what types of networking applications you might want to implement, so we’re just gonna specify the from and to addresses. You do your checksumming and MTU management the way YOUR application wants to do it.”

    I mean I’m not gonna sit too much in judgement of someone who created something which is working and producing good things but it’s hard not to be wistful about how much better it could be if the spec was specific enough that the different apps could substantively talk to one another.