@BeAware@social.beaware.live @ThaMunsta@nervesocket.com From glancing through the github issues it looks like it only does that for account deletions. Though I have no idea how many of these are resolved or no longer function as described in the issues

https://github.com/mastodon/mastodon/pull/22273:

One outstanding issue with Mastodon is that deleting a local account sends a Delete activity to the whole known fediverse to ensure everyone is aware that the account does not exist anymore. This is wasteful, and increasingly so with the growth of the fediverse. It is also a minor privacy concern, as servers who would otherwise not know about an account would learn about its (previous) existence without a good reason.

https://github.com/mastodon/mastodon/issues/22154

Currently, posts deleted over a week earlier on one server are still visible on others. For example, I can see (on both mastodon.social and mstdn.social) a post I deleted at the start of December on mstdn.jp. On both of those other servers, it looks like the post is still live and available on mstdn.jp.

https://github.com/mastodon/mastodon/issues/22070#issuecomment-1340711206:

To clear up some misunderstanding, Mastodon does not send a Delete to every known server for every deleted post, that would be too expensive. It does send a Delete to every known server for every deleted account though.
I do have some idea on how to improve that (keep track of which servers ever requested an account, using a bloom filter so it remains manageable storage-wise), but it will require some work and will only work for newly-created accounts, not ones that existed before the change was implemented.

https://github.com/mastodon/mastodon/issues/6849#issuecomment-1418688876

It’s retried a bunch of times, but once every retry is elapsed and the post is deleted, Mastodon stores neither the post’s previous existence nor who was supposed to see it, so such a feature would require the admin to provide:
the post’s author
the post’s exact ID
who to send the deletion notice to

@ThaMunsta@nervesocket.com @BeAware@social.beaware.live actually now that you mention it, I’m not sure how Mastodon decides where to send Deletes to

Like, does it maintain a list of all servers that requested your post? That feels excessive but also probably the only way to ensure that every server that has your data deletes it. Or does it just send it to all your followers and servers that boosted/liked it

@BeAware yeah weird, it’s gotta be a bug because I doubt acm.org is intentionally archiving posts lol

I would hope that mastodon notifies the server if they replied to a deleted post though, in case a delete message falls through

@BeAware which instance? That sounds more like a bug than anything, you’d have to go out of your way to reject deletes right or just never receive the DELETE message?

It’s pretty funny as a progression of photos

@jon@mysportgallery.com gotta defend the bowl

Not sure what happened with these 2 #cats but it looks cool

@stefan@stefanbohacek.online I was just thinking about how awful my network setup is because my basic router doesn’t have loopback. So I access my mastodon server through a vpn, which means the only place in the world where that iframe doesn’t work is if you’re connected to my home wifi

@stefan@stefanbohacek.online Also I’ve mentioned it before. But assuming news orgs do end up creating their own instances, it’d be cool to get a ‘boosted’ notification when your post is quoted in an article

@stefan@stefanbohacek.online Oh cool! that’s awesome

I haven’t seen any impact whatsoever, but I imagine if it was a more high profile article it might generate more traffic if I understand how embeds work? My server already has to handle traffic to a number of servers anyway whenever a post is published in probably faster succession than people opening up that article.

Tangentially related, I think the verge has been planning to integrate more deeply with the fediverse based on posts I’ve seen from them- and I think long term it’d be better if they just had their own AP server that they grabbed embeds from rather than individual servers? For traffic reasons, and for the fact that I think I have a lot of control over what those embeds look like. Also, my server’s probably a lot less reliable than any larger platform so theoretically that embed could just stop working

@FandaSin@social.linux.pizza @BeAware@social.beaware.live Yes this is possible and I think it’s been discussed as a solution. The concern, last time I was reading about it, is that malevolent servers could poison a link preview and send fake images along with the url (the argument against this is you’re already ‘trusting’ the server if you’re federating with them, so that trust should extend to link previews)

Another proposed solution was just having servers wait a random amount of time before fetching the link preview so not every server is requesting the preview at the same time

@BeAware@social.beaware.live
I’m not sure how easy it is to tell if a post requires you to be logged in if you’re already logged into bluesky

https://github.com/snarfed/bridgy-fed/issues/1267 this was proposed the other day though which would help

@BeAware@social.beaware.live which is absolutely a fair complaint! Like I said I don’t like the current popular suggestion. But that’s why it’s the opportunity for people (who are significantly better at design than me) to debate the logo because I also don’t like meta’s version for the exact same reason and that’s gonna be the one we end up with 5 years from now.

Hell, I’m sure there’s a way to take the current fedi logo and modify it slightly so it does work in flipboard’s (or tumblr or Ghost or whoever else joins in the near future) design language and I feel like it’s an important discussion to have now before everyone just ends up with Meta’s boring version.

@BeAware@social.beaware.live I get that and I also don’t particularly like ⁂ as the option. But the idea that we can’t find some more useful logo because it’ll confuse people when most people are unaware of the Fediverse’s current branding seems off. If there’s any time to debate the logo it’d be now before all these massive companies with hundreds of millions of users settle on a logo w/o the input of the open-source side of the fediverse.

I doubt Threads will ever move on from their version, but Flipboard has signaled they’re willing to change out the logo they’re using

@BeAware@social.beaware.live I dunno, personally I don’t like the current fediverse logo. Tried to make it look good on a site a couple months ago and gave up and just put the mastodon logo in there instead, which probably isn’t great for a network defined by many different servers.

Threads introduced their own fediverse logo probably for the same reason Flipboard adopted Threads’ version- that it’s pretty difficult to make it look good in different scenarios- which means assuming we stick with :fediverse: the default for everyone else will probably end up being Meta’s version