aka freamon
Codeberg: https://codeberg.org/freamon?tab=activity
Anything from https://lemmon.website/ is me too.
I assumed that was there because there are some sites (e.g. reuters.com) that make it difficult to automatically grab a thumbnail image to go with the article. So if you’re posting a link to somewhere like there, you’d find a relevant image manually, and use that field so the post you make will be more engaging.
I don’t think it’s for posts that are an image - in that case, the software can just use that to create a thumbnail, so it doesn’t need the extra help.
I think you’re remembering wrong. The communities that have moved so far have been a manual affair: a post on the old community with a “We’ve moved” post, locking that community, and starting up brand new somewhere else. It’s a fresh start - nothing is migrated. It’s very likely to be technically impossible to move communities in the way you’re imagining.
Oh wow - I never realised that lemm.ee had got so far behind. That problem seems to be in the past now, and posts will only be missing from there if they’re relying on world to send them.
As the post that Blaze linked mentions, LW is catching back up now (it’s only if the delay gets over 7 days that you need to worry about them being lost)
Hypothetically, sure: the info exists in one place - they’d just have to arrange a way to transfer it.
Votes themselves are a simple activity, but each one can cause a surprising increase in storage requirements (every vote has a user, every user has an instance, every instance has admins, and all these entities might have avatar and banner images associated with them). Most instances are run by one person as a hobby, and paying for DB and image storage seems to be the no. 1 reason for instances folding, so there’s generally a question of how much one instance should be an exact mirror of another one.
You’re correct in assuming that nothing is stuck in a queue.
Compared with other Fediverse platforms, a feature that Lemmy lacks is paginated outboxes. These would allow communities to list all the posts, because other instances could get them a page at a time (e.g. 20 for page 1, then the next 20 for page 2, and so on). Instead, they provide a non-paginated outbox with only the most recent 50 posts. An outbox for comments isn’t really feasible without pagination, which is probably why they don’t provide one at all. For votes, it’s even less practical, and irrespective of that, it would go against the familiar hang-up about votes being private.
So if you’re the first person to join a remote community, then 50 recent posts are brought in, but no older posts, no comments, and no votes. There’s no way to get the old votes. If your instance receives some activity that makes it realise that it’s missing something, then it will resolve it (e.g. it will often fetch an old post if it receives a reply to it, and fetch a comment if it receives a vote for it), but it will start that post or comment at score 0.
If you really wanted to be fully in-sync for comments, then you could script it to use the APIs for the remote and local instance. For the remote instance it would be something like: list the posts oldest to newest (limited by the amount you’re missing); get the ap_id for each one, then login to your instance and ask it to resolve it. Then do the same for the comments in each post. Everything it resolves would be a score 0 though, and it assumes that the author hasn’t deleted themselves in the meantime, or that their instance hasn’t disappeared. Given that, I don’t really see the point, other than trying to a completist about stuff.
(that link needs the ‘https’ part in to work)
The act of making a first post or comment is all that’s required for other instances to become aware of yours. Your site is already in their /instances page and at places like https://lemmy.fediverse.observer/redlemmy.com
From what I can tell re join-lemmy, the list there is just for that site, and it’s fed by the lemmy-stats-crawler (you’ll be able to see it in your nginx logs). There’s a restriction of needing 5+ active users a month though, which it doesn’t look like your site quite meets.
Federation delay from lemmy.ml to lemmy.world:
(It’s been a pattern of spiking up to almost 2 days before recovering).
It’s a LW problem (that they are aware of), and it’s unrelated to whether a comment has images or not.
FWIW: that post is not for 2 communities - it’s for one community (/c/test at sh.itjust.works) and one user (/u/test at lemmy.ml) - I’m guessing that it’s autocompleted to a thing that was different from your intentions.
(edit: the webfinger response from lemmy.ml for ‘test’ returns both a Person and a Group, which Lemmy can deal with, but Mastodon probably can’t, so it just grabbed the first one it saw)
The post is at https://lemmy.world/post/1285556 - it’s a link to GIF that’s been deleted at the source (it’s a 404).
Here’s a community node for mastodon
Should this be a link to something?
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).
No reason that I can see. Your instance is sending stuff out, LW is getting stuff in, you’re not banned on LW (as far as I can see), LW and feddit.org are likely in the same part of the world (so no fed delays). There’s been times when LW has received a post and federated it out, but not shown it itself, but that’s not the case either.
I don’t know. It might be worth asking on LW’s matrix channel, to see if an admin will look into it.
Frontends generate the main feed by querying api/v3/post/list. This doesn’t provide any crosspost info - for that you have to go into the post itself by querying api/v3/post. As such, frontends would have to do a fair bit of extra work to wrangle the required information for a main feed that combined crossposts. The only attempt I’ve seen at doing this was in a dev branch of Tesseract.
I’d argue that you have a problem as soon as you start saying ‘frontends need to do some extra work’ - it breaks the dynamic between backends and frontends. Backends should be big, complicated things, worked on by people familiar with the project, to provide all the logic, whereas frontends should be light, relatively easy to write, runnable on devices with limited resources, and mostly focused on how the information provided to them should be displayed. They should store the user’s preferences, and login details, and that’s it - everything else should come from the backend.
As for combining comments, this can lead to fraught situations. This link was posted to both ‘cars’ and ‘fuckcars’. This link was posted to both ‘taylorswift’ and whatever-the-fuck ‘barelower4thwomenmusic’ is: so the comments for a music video would be from Taylor Swift fans, as well as from people with a foot fetish. Moreover, if this is the expected behaviour, trolls can use it to get up to no good, and make a bunch of comments appear in a new crosspost to a community subscribed to by people guaranteed to disagree with them.
I think anyone trying to ‘fix’ this issue will run into the fact that certain assumptions have been made in a software’s design, and those assumptions determine how database relationships are formed. The real answer may lie in something like ‘ClubsAll’, rather than an attempt to fundamentally redesign existing platforms.
In the meantime, crossposting is being actively encouraged. Movie news is posted to 5 different communities, open-source news is posted to 8, Taylor Swift music videos are posted to 12. The useful crossposts (one that help you discover a new community) are in the minority - most of it just ends up being annoying. And it’s because there this idea, that some time in the future, there’ll be a tech solution to make it less annoying, and the suggestion that maybe you should just pick the community you like and post to that, is - to me - surprisingly unpopular. Not only might this solution never come, but anything URL-based can’t do anything about the same question being posed to ‘nostupidquestions’ and both ‘asklemmys’, or with an image being uploaded and posted to one community, and then re-uploaded to post to another.
This whole thing feels like trying to find a tech solution to what I see as a user problem of mindless posting to as many communities as you can find. To be honest, it’s a problem that makes me a bit disillusioned (I saw a post the other day that was posted to both ‘interestingasfuck’ and ‘mildlyinteresting’, and thought - if that’s the community names we’re going with, and this behaviour is apparently okay, then we may as well be on Reddit).
OP had an account at .ml and it was banned from the entire instance. Their LW account has been banned multiple times from .ml’s asklemmy community (this probably what this post is about, rather than .world’s asklemmy community but I didn’t want to get involved).
Congrats.
There’s also a !lemmyapps@lemmy.world, btw.
Oh. I subscribed to this post because I hoped someone would be able to give an answer too.
It’s been a day, so before I forget and on the basis that some answer is better than none at all, I’ll have a crack:
400 Bad Request isn’t much to worry about, it doesn’t mean anything is malfunctioning and it can happen for a gazillion reasons. One is you’ve joined a new community and someone Likes a comment you don’t have (particularly if it’s nested in other comments you also don’t have). Another is if someone Likes a post or comment by a user on an instance that you’ve defederated from (your instance is defed’d from lemmygrad and hexbear whereas lemmy.ml isn’t)
As for 499, that seems to be a client issue, and that client mostly seems to be beehaw, who are stuck on an old Lemmy version and being increasingly wonky (in the other direction, they often reply in HTML rather than JSON and randomly decide that their communities’ inboxes don’t exist, so I wouldn’t worry about stuff from them either)
Yeah. There’s no wildcard call. One thing you could do to script it would be pull JSONs from https://data.lemmyverse.net - use one for the initial effort, then subsequent ones to track new communities. You’d definitely want to filter it - as you’ve noticed the vast majority of that 30k are dead or spam or something you wouldn’t want for one reason or another (e.g. communities from instances you’ve defederated from).
As for what bots do, it depends on how they were programmed I suppose. There’s a bonkers one on https://leaf.dance that just seems to crawl comments and subscribe to any ! links it finds, but there are others (I can’t remember their names) where it’s more of a manual job (the mods of a community submit the details to it).
Luigi Mangione is the median American voter