Skip to content

NodeBB v4.0.0 — Federate good times, come on!

Uncategorized

  • 0 Stimmen
    6 Beiträge
    0 Aufrufe
    beaware@social.beaware.liveB
    @julian @rolle every instance has a public timeline.It would have just made it so I don't have to go to mastodon.social, which would be VERY nice.
  • Long-formers Activate!

    Uncategorized
    11
    +0
    0 Stimmen
    11 Beiträge
    1 Aufrufe
    julian@community.nodebb.orgJ
    @jiejie@mastodon.social good question! The answer ultimately lies in how you want to communicate with your audience. Each option is different and it's hard for you to know which software is the best fit. That's why even when I say NodeBB sits somewhere in between microblogs and blogs, NodeBB might not be the right solution, yeah? What kind of site do you want to build, how in depth do you want to go, etc.?
  • 0 Stimmen
    4 Beiträge
    0 Aufrufe
    julian@community.nodebb.orgJ
    @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.
  • 0 Stimmen
    10 Beiträge
    27 Aufrufe
    julian@community.nodebb.orgJ
    @hexaheximal@mastodon.social that's fair. I also feel a certain responsibility to protect and defend the fediverse from bad actors, so I get being on guard. I've also seen what happens when fedi brings out the pitchforks, though
  • Nodebb - Forum Crash

    NodeBB
    2
    0 Stimmen
    2 Beiträge
    2k Aufrufe
    FrankMF
    NodeBB hat Version 2.8.9 released. Wollen wir hoffen, das der Bug weg ist
  • NodeBB - Git Prozess

    NodeBB
    2
    0 Stimmen
    2 Beiträge
    106 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...
  • NodeBB - v1.17.0

    NodeBB
    1
    0 Stimmen
    1 Beiträge
    164 Aufrufe
    Niemand hat geantwortet
  • Portainer - NodeBB Container erstellen

    Linux
    1
    +4
    0 Stimmen
    1 Beiträge
    327 Aufrufe
    Niemand hat geantwortet