Das löschen setzt nur einen Datenbank-Eintrag 'deleted: true`, aber die Inhalte sind weiterhin vorhanden. Ein Admin kann das also problemlos wieder herstellen.
There are countless feature requests for Lemmy, but we are only two fulltime devs. Our time is limited so we have to set some priorities, and no matter what we do, some people will always disagree with those priorities. And besides implementing new features we also have many other tasks like reviewing pull requests, or right now bug fixing to get already implemented changes out into production. The only way to implement more features faster is by having more developers. Either as volunteers, or by hiring people with donation money.
I think your proposal is reasonable. However it depends how exactly post tags will get implemented, which is still rather vague. I dont think it makes sense to implement federated hashtags before we have post tags in Lemmy figured out.
In any case your tool looks very useful as a stopgap, and can help to test how hashtag federation can work in practice.
The only thing to keep in mind with 0.19 versions is that they are meant to be used with 0.19 backend. This post has some info about supporting 0.18 and 0.19 from the same client, but Im not sure if lemmy-js-client supports that as lemmy-ui only needs to be compatible with a single backend version.
Alright I will post these updates to /c/announcements in the future.
lemmy-js-client already has versions for the latest Lemmy code. So you just need to upgrade to the latest version and adjust your code where necessary.
About your second point, there is !announcements@lemmy.ml where only Dessalines and I can post. We could post the updates there and you could follow the community via RSS feed to get notified.
Yes it includes community follows, saved posts, blocklists and profile data. Here you can see everything thats included:
https://github.com/LemmyNet/lemmy/blob/main/crates/apub/src/api/user_settings_backup.rs#L41-L60
Edit: I just noticed that instance blocks are missing from the export. Added here
Youre right, my mistake. Ive manually unhidden all his comments, except those in #234.
My comment about scheduling in clients was from January and that option was already discarded by dessalines on the next day. No use in rehashing the same thing ten months later. All you are doing is creating pointless notifications for everyone. I know its not ideal to close and reopen an issue, but really why is it a big deal? We closed hundreds of issues recently which were outdated, invalid or already fixed. I accidentally closed one that still needs to be implemented and dessalines reopened it, so everything is fine. Certainly not a "squabble", and your comments added nothing at all.
Its true that I shouldnt have given a warning first, but most likely you would have responded with another offtopic complaint so I didnt see any use in that. If you want to complain then do it somewhere else, not on the issue tracker which is meant for getting work done.
Löschungen und andere Aktionen werden sofort föderiert, sollte nicht mehr als ein paar Minuten dauern. Außnahme ist wenn kein Nutzer auf einer Instanz der Community folgt, dann wird auch nichts aktiv föderiert. Außerdem können Admins gelöschte Inhalte immer sehen.