|
Top-level
 Again with "Mastodon's integration with Threads", it's quite literally Threads wants to use ActivityPub and publish & receive messages with compatibility with Mastodon (and Misskey/Forkeys) That's legit it. There ain't no "integration" beyond speaking the same protocols the same way, as the protocols were designed to enable. 14 comments
 @PeterLG @thisismissem This thread doesn't connect to anything for me, what is she talking about? Out of context many things she says (like "you don't want those users anyway, be honest") sound incredibly shitty. @Natanox @PeterLG I've decided to not link to the original article. It's not particularly hard to find. But as for that quoted comment, the same group that derides Mastodon for the change of the default instance in their official apps, is the group that wants "small fedi" where people are excluded unless they know someone who runs a server or know how to deploy a Server themselves. They explicitly want mastodon to be hard for "normies" to use to retain their ideals for what it should be @thisismissem @PeterLG So I assume you're talking about this one. https://privacy.thenexus.today/mastodon-hard-fork/ I see who you're arguing against. Still, Mastodon's decision to strengthen centralization by leading everyone to the same instance isn't something worth defending in my eyes. @thisismissem @PeterLG Nothing speaks against a simple registry assistant, however it doesn't have to be just one server either. Users could literally be asked about their hobbies once with known good instances being automatically picked by your choice. Instead now the existence of the "official Mastodon" as well as "those others" is communicated, which is just awful and not in the spirit of the Fedi at all. @Natanox @PeterLG βknown good instances" is extremely hard to define, because different people have different needs & safety requirements. It's just like people going βgoogle mastodon -> mastodon.social -> sign upβ Perhaps the language could be changed, but when the software's reputation is built on people's first experiences, there does need to be some control over that experience, and the instances list just wasn't working, with some of them just *disappearing* @thisismissem @PeterLG Build a proper board with some oversight then, making sure every server provides the same level of safety and quality. But don't just slowly centralize itβ¦ that is and will always be the wrong approach. @thisismissem Within days of setting up a new instance and interacting with people on other instances using ActivityPub, I saw a data scrape of my public toots and CDN assets occur. I think it's reasonable that an organization that profits from user data will survey this social network graph of people existing outside their walled gardens. @bear "I saw a data scrape" by who, and are you sure it was a scrape? There's a misnomer that activitypub is push-only, this is incorrect & you will actually see a LOT of GET requests retrieving data from your server. Do you have authorized fetch enabled? It can help somewhat. Most fediverse User-Agents also advertise where they're from. @thisismissem Within the first week of operating an instance, I suddenly saw a walk of all of the CDN assets, including cached media from other instances. At first I assumed it was some kind of index, but I was able to corroborate this action by reviewing nginx logs. I did not see an uptick in Sidekiq. As a new admin, I wasn't sure how to gather more information to understand what would cause a 1:1 serving of GB of media from my CDN I had just set up. @bear read requests in ActivityPub won't necessarily correlate to an increase in sidekiq jobs (unless it's to verify the reader's signatures, but even that is generally done in the request/response lifecycle) As for a walk of your CDN, were there any user agents or IP addresses popping in the logs to indicate a crawl? Some fediverse clients behave in varying ways (proxying requests, requesting additional data, etc), so patterns would be important here. @thisismissem Good to know, regarding no increase in Sidekiq activity. I guess I still have a lot to learn. π What I recall from that moment was that everything stood out like a spike in the CloudFront dashboards. Within a short time window it looked like every asset was touched. I remember it being hard to determine who the client was, but that it looked like one client. @bear there are some fediverse software projects that'll try to backfill posts when they become aware of a user, perhaps it's this gone awry and is a bug instead of a bad actor? Though, also, Jortage is gaining popularity, which is an alternative to storing all the content yourself. |
Gregory's Server
@thisismissem
Thank you! Sick of the hyperbole.