Co-Founder (NodeBB) | Husband 🤷‍♂️ and Dad 🙉 to three | Rock Climber 🧗‍♂️ | Foodie 🥙 | Conductor 🎵 | Saxophonist 🎷

✅ Small teams craft better code.
🇨🇦 Made in Canada
🗨️ Federating NodeBB with funding from NLNet ♥️🇪🇺

  • 12 Posts
  • 66 Comments
Joined 12 years ago
cake
Cake day: June 17th, 2013

help-circle


  • Hmm… considering that Piefed cross-posts are entirely separate posts, then if the original is edited, then the modification is not carried over to the cross-posted post, correct?

    I’m thinking that for NodeBB we could continue to have cross-posts reference the canonical topic. They’d simply be part of a separate audience as well.

    Whether this is local-only or not, I am not sure yet. Perhaps for federation purposes we’d still report the original category (if there is one) under audience






  • @scott@loves.tech Hubzilla is formatting its Notes in a manner I wasn’t expecting.

    • The group actor is the attributedTo, which is not possible in NodeBB
    • The note itself is not addressed to the group actor, only its followers collection
    • There is no way to discern without parsing the note content itself who authored the original note.

    So at present while I would be able to retrieve the note, without a proper backreference to the group actor, I don’t think I can slot it correctly.

    Not sure why the received activity is returning a 403, as well.


  • @scott@loves.tech can you share an example of a group actor from Hubzilla? Would be interesting to see how that’s handled. Likely it wouldn’t work properly because categories in NodeBB don’t author posts.

    Do your group actors send creates on behalf of regular users? That might work ok.

    Lastly, there’s no requirement that a NodeBB category be mentioned. It only needs to be addressed. A mention is the easiest way to do that because addressing is abstracted out of the Mastodon UI.

    But for things like PieFed, Lemmy, Mbin, and likely Hubzilla, you’re able to change addressing based on where you create the post.


  • @CWSmith hashtags in NodeBB are only relevant at the topic level — that’s just how it was designed years ago.

    You’ll note that on microblogs, tags can be added on any post. While we show them, we don’t consume or index them unless they are the original post.

    When you use tags in NodeBB, they are federated outward with the original post.

    Hope that helps!








  • @Kichae I worked on this for most of this week. You can follow along with that effort here:

    https://github.com/NodeBB/NodeBB/issues/13255

    How exactly to integrate categories into the NodeBB UX is an interesting question. It’s one thing to be able to render a remote as:Group actor as a category, and I think we’d want it to be searchable as well (otherwise how would you find them?)

    That’s the baseline.

    Being able to customize your /world page with a selection of subcategories is really interesting… I am not sure I’d want to allow users to customize the /categories page, so /world seems like a nice place for it.

    Maybe users can “pin” remote categories to their world page. Would that work?