Skip to content

Fun with Federation: Lemmy edition

ActivityPub
5 3 32
  • 0 Stimmen
    3 Beiträge
    101 Aufrufe
    julian@community.nodebb.orgJ
    @renchap@oisaur.com how does RFC9421 differ from Mastodon's existing support for HTTP Signatures? Does this mean you're moving away from cavage-12? That's important to know, and if you're looking for an implementor to handle double-knocking, that is something I can put together for you.. we don't do it at current.
  • Wix Forums being sunset, what's next?

    ActivityPub Test Kategorie wix nodebb migration
    1
    0 Stimmen
    1 Beiträge
    56 Aufrufe
    Niemand hat geantwortet
  • Updates to the world page

    ActivityPub Test Kategorie nodebbactivityp nodebb
    32
    2
    1 Stimmen
    32 Beiträge
    724 Aufrufe
    julian@community.nodebb.orgJ
    @projectmoon@forum.agnos.is said in Updates to the world page: > > > Also, are there plans to merge the federation synchronization and new remote category following stuff together into one cohesive set of functionality? Yes... the remote category functionality supercedes the category sync functionality in some ways, but there is still a use case for it. Most likely I will need to develop proper support for cross-posting (at least locally), and that would work well with the remote category functionality, so that topics are cross-posted to the synchronized category, instead of moved.
  • 0 Stimmen
    9 Beiträge
    175 Aufrufe
    julian@community.nodebb.orgJ
    @philipp@social.anoxinon.de I kind of think this is really missing the forest for the trees if your rational is CO2 emissions... I mean, a far greater generator of CO2 emissions would be every single Mastodon instance caching every piece of media it sees...
  • NodeBB - Security Vulnerability Notifications

    NodeBB nodebb security
    1
    0 Stimmen
    1 Beiträge
    93 Aufrufe
    Niemand hat geantwortet
  • NodeBB - Git Prozess

    NodeBB nodebb
    2
    0 Stimmen
    2 Beiträge
    146 Aufrufe
    FrankMF
    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...
  • Upgrade auf v1.19.0

    NodeBB nodebb
    1
    0 Stimmen
    1 Beiträge
    142 Aufrufe
    Niemand hat geantwortet
  • NodeBB - Upgrade auf v1.9.0

    NodeBB nodebb linux
    2
    1
    0 Stimmen
    2 Beiträge
    921 Aufrufe
    FrankMF
    Da oben fehlt ein Schritt. cd nodebb (or path to where nodebb is installed) ./nodebb stop git fetch git checkout v1.12.x git merge origin/v1.12.x ./nodebb upgrade Beim nächsten Upgrade testen.