mastodon.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
The original server operated by the Mastodon gGmbH non-profit

Administered by:

Server stats:

377K
active users

@jesse @darius I think in pump.io, the server for the OP reshares all the responses to all addressees. But it's not perfect, by far.

@jesse @darius "all responses to all addressees" is not true. There are some checks.

@evan @jesse I don't know about clever but it's never been clear to me why mastodon doesn't just make a request to the remote server for all replies and then run them through your standard local filters. My guess has always been it's a perf issue but that's just a guess.

@darius @jesse I think that should work too. I should probably go look at how I did some of these things

blaine

@evan @darius @jesse this is one scenario where Bluesky's and SSB's approach is better in that it makes it obvious where to go looking for the replies (but presumably this is just a matter of doing an eventual-consistency load? cc @cwebber)

Related, the counts on everything (followers, replies, likes, etc) are totally inconsistent across instances. I *think* what's shown is "# of people who liked/boosted this from *this* server"

@blaine @evan @jesse @cwebber I think what's shown is "number of events this server knows about, which is guaranteed to be stuff from this server but also might be from other servers if for example a remote boost of this post landed in someone's timeline"

@darius @blaine @jesse @cwebber a boost should really CC the OP! That's just polite, but it also helps keep the stats up to date

@cwebber @darius @blaine @jesse I got it, don't worry

Also, bto makes a lot of sense for social software. Bto followers is probably more correct than to followers if they're not directly addressed.

@blaine @darius @jesse @cwebber also, since the op is not directly addressed, it should probably be BCC

@blaine @darius @jesse @cwebber

Every Activity object can have a replies property with a stream of all replies.

Every stream can have a count.

@evan @darius @jesse @cwebber if ActivityPub has a feature but E doesn't agree to implement it, does it make a sound? 🫣

(To be fair, scaling issues are real rn, re-fetching all the posts at even suitable intervals would be ... A lot)

@blaine @darius @jesse @cwebber yeah, that would be nuts. That is why the OP's server should keep a paged collection of all replies, and clients can request more as they need them, and keep a last-read cursor so they don't have to refetch anything but the newest stuff.

@Staines @evan @blaine @jesse @cwebber @seb no idea but I certainly haven't heard of any movement on it and also the software would require significant work to make plugins realistic so I'm guessing: don't hold your breath

@darius does hometown keep posts local by reifying the server as a group or list and addressing activities to that group or list?

@darius

Like

```
{
"to": {"id": "https://myserver.example/", "type": "Group"},
"object": {
"content": "Hello, local group!"
}
}
```

@evan no it's not done through ActivityPub at all, it's controlled via the mastodon API and the federation controller logic checks for a boolean in the statuses table when deciding where to send

@darius OK. Thanks for building something that people like so much.

@evan to be clear, I just merged the already-open PR on mastodon (which is still open years later) and called it a fork (with permission of the PR author)