this post was submitted on 07 May 2024
114 points (100.0% liked)
anime
11001 readers
173 users here now
Welcome to c/anime on Hexbear!
A leftist general anime community for discussion and memes.
Simple rules
-
Be nice.
-
Use spoiler tags.
-
Don't sexualise underage characters, including 1000 year old loli ones.
-
Don't post hentai here. This is an anime community.
High quality threads you should definitely visit
Gigathread: Good Anime Talks, Presentations, Conventions, Panels, etc
Piracy is good and you should do more of it. Use https://aniwave.to/ and https://4anime.gg/ for streaming, and https://nyaa.si/ for torrents. Piracy is the only means of digital protest that audiences have to fight poor worker treatment.
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Heyo the original is still visible from db0 using voyager app and it shows the edited version as the post body if that makes sense
I’m not advocating for any particular action, it’s not even my instance. Just wanted to share a possible federation issue
Huh. That's got to be code unique to db0 ? Why the hell would they implement something like that? Users should remain in control of their own content after posting. If someone posts dox details or credit card details they can't edit to remove it? AWFUL feature
there are two images for me on .ml as well (I use Eternity client, maybe that matters)
@dessalines@lemmy.ml is that an intended quirk of federation? Have we just not come across this oddity until now?
If it is I would caution against it, for the reasons detailed above ^
No, its because the post creator used the image twice, as a post URL, and in the post body. It only needs to be in the post url.
Ohhh I see what's happened, they removed the original post URL and put in a post body image instead. The Post URL image has federated and its removal hasn't been transmitted to elsewhere, so they've only received the post body addition while keeping the Post URL image.
Good to know that's no actually a solution then. Next time I'll just ask for a completely new submission and remove the post entirely. Might be worth considering allowing the removal by the owner to federate though.