@david@weaknotes.com in what way, that the category is cleared out regularly? I think that happens often already with users auto-deleting their posts. https://activitypub.academy is another example of a test instance that is regularly cleared. Either way I take no offense if try.nodebb.org gets blocked here and there

Always something with my fingers. The number of times a problem I have is because of a typo...

A reminder that the Forum and Threaded Discussions Task Force is meeting in roughly 20 minutes at this Jitsi link, see you all there! https://meet.jit.si/ap-forum-wg

@squinky@teh.entar.net in all seriousness it's entirely up to you which FEPs to support. Some FEPs have more adoption than others, so it would be wise to adopt them over time as well. Others deal with aspects of the protocol that may not even apply to your specific use case. There is no expectation that one should implement every FEP. Think of it this way: an FEP is a way to document in public (not in code!) how one or more implementations have approached a problem that the ActivityPub protocol spec did not cover. There may be a lot of them, they may be needlessly complicated, but it's better than having to dig through someone else's code base.

Heute gab es ein Update von 2.4.5 -> 2.5.0 Das oben geschriebene funktioniert nicht git fetch git reset --hard origin/v2.x ./nodebb upgrade Ausschnitt der Konsole ~/nodebb$ git fetch remote: Enumerating objects: 244, done. remote: Counting objects: 100% (239/239), done. remote: Compressing objects: 100% (100/100), done. remote: Total 244 (delta 160), reused 212 (delta 138), pack-reused 5 Receiving objects: 100% (244/244), 55.57 KiB | 7.94 MiB/s, done. Resolving deltas: 100% (160/160), completed with 62 local objects. From https://github.com/NodeBB/NodeBB dd3e1a2861..01d276cbee v2.x -> origin/v2.x * [new branch] async-zxcvbn -> origin/async-zxcvbn 9260b4ef19..d06938d877 bootstrap5 -> origin/bootstrap5 884d40756a..8fe41d92a2 develop -> origin/develop a088eb19af..1076285dc9 master -> origin/master + b7d916c321...c85ac68373 renovate/ace-builds-1.x -> origin/renovate/ace-builds-1.x (forced update) * [new tag] v2.5.0 -> v2.5.0 :~/nodebb$ git reset --hard origin/v2.x HEAD is now at 01d276cbee chore: incrementing version number - v2.5.0 :~/nodebb$ ./nodebb upgrade Updating NodeBB...

Irgendwie hatte ich Differenzen zwischen meinen beiden Foren, die es eigentlich nicht geben dürfte!? Problem scheint zu sein, das das Plugin nodebb-plugin-ns-embed nicht richtig funktioniert. Da bekam ich den Tipp, das Plugin nodebb-plugin-embed zu installieren. Das ging aber nicht über das Admin Panel, da kam folgendes. [image: 1653559307844-plugin_error.png] Ok, dann von Hand npm install nodebb-plugin-embed Im Admin Panel aktivieren, danach Rebuild und Restarten. Aktuell in v2.0.0 nicht über das Admin Panle durchführbar, Fix ist schon fertig. Kommt wohl mit v2.0.1 ./nodebb upgrade ./nodebb restart Danach lief alles!?? Hoffe ich