Lemdro.id

2 points

21 hours ago

@BeAware@social.beaware.live 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?

BeAware :fediverse:@social.beaware.liveOP

report

[ - ]

2 points

21 hours ago

@tom@tomkahe.com https://mastodon.acm.org/@nikatjef/113159038341162925

I deleted the post that this is replying to.

You won’t find it on my instance. Yet, there it is.

Not sure what it is, but it doesn’t feel good.

report

Mike Johnston@mastodon.nervesocket.com

[ - ]

1 point

21 hours ago

@BeAware@social.beaware.live @tom I would like to think this is sorta a “if a tree falls in a forest” kinda thing or maybe just a relay not doing a good job. If you have a follower from that instance it absolutely should not happen…

report

[ - ]

2 points

21 hours ago

@ThaMunsta @BeAware 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

report

BeAware :fediverse:@social.beaware.liveOP

[ - ]

2 points

21 hours ago

@tom@tomkahe.com @ThaMunsta@nervesocket.com it should send delete requests to every instance that it was sent to. It should know that because my server has to actually send the post. Maybe I’m misunderstanding things but this seems like it should be an easy thing to do.

report

[ - ]

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

1 point

20 hours ago

@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

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

report

Show more comments

[ - ]

1 point

21 hours ago

@BeAware@social.beaware.live 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