haganbmj

They start out somewhat similar, but the manga gets a lot more wholesome and less abusive as it goes on. Well worth the read.

Less engagement is exactly what I would want. Show me my new chronological content and then I'll get the hell out of there.

Not having a touch screen was a pretty sizeable component of my decision making process when I bought my 3.

https://www.youtube.com/watch?v=HLWY7fCXUwE

This is one of my favorite GDC talks and it's about this subject with a sizeable segment devoted to the second paragraph in this article comparing Video Games to the availability of classic Movies.

Just to pose these in a similar thread, I have a few questions as a casual observer, some of which I'm unclear if they're handled at the protocol or Lemmy level.

• As I understand it servers subscribe to other servers and everything is then push based?
• I assume ordering is not a guarantee. So there's probably no concept of offset tracking on subscriptions or replaying a time range?
• If ordering is not a requirement how do likes/comments handle out of order receipt? Everything seems to have a local ID, so can content get pre-liked before the root message arrives? Unclear if ID generation is based on any identifiers you'd have to work with or not - or whether remote content retains its origin IDs?
• Lemmy at least appears to have some retry mechanism, but I'm unclear the behavior on that - seems annoying with 1000+ subscribing servers.
• I seem to recall reading ActivityPub has some pattern for batching, but reading the spec again I'm not seeing it. Is that a thing?

Couple questions.

• Is there any pattern for backfilling on a new subscription?
• Direct accessing a post from an unsubscribed server doesn't appear to always load all comments from the host server, is this due to when the content was initially loaded (and maybe some cooldown on refreshing it)?
• Out of curiosity it looks like content is assigned unique ids against the local server, I assume these are internally mapped to their origin server and ids? Is there a way to direct link to correlated posts similar to the /c/name@server pattern? /post/id@server was my initial guess but doesn't appear to work.