Piero Bosio Web Site

@darius @julian I vote for this - one or the other, never both.

IMO the summary is for index or thread views where the article is too long to display, and the author wants to make sure the part that gets displayed accurately reflects the content. If you're just gonna auto-truncate the content, better not to put a summary at all. The client would do a better job.

@mcc @alter_kaker "I would join the Bluesky API Touchers discord"

But... why are they not using... no OK never mind.

I'm so glad for this thread! I've had a bazillion questions about AT but nowhere to ask them. I really think there should be an "other protocols" channel on activitypub.space though. This is not "Technical discussion about ActivityPub-related topics" and sooner or later someone's gonna get angry at us.

@lrhodes @mcc @alter_kaker @esoteric_programmer My understanding is that relays have a "replay since timestamp X" functionality, so that consumers that go down for a while can get back up and running. Originally relays by definition had to support any X back to the beginning of time, leading to absurd storage costs. Today they are allowed to have a much shorter window, meaning in effect the storage cost is insignificant and it's the network cost that dominates. Unless I'm mistaken, the canonical store of a user's posting history is and always was the PDS.

@mcc @alter_kaker @esoteric_programmer I think the key point is: "Every Bluesky replica is, probably without realizing it, making a bet that Bluesky has already plateaued." This is a worthwhile experiment, as long as you can pull the plug at a moment's notice and lose nothing.