@rimu@piefed.social interesting, how does this differ from tags?
Edit: I see the other post you made. I’m interested in this but hoping you’ll write up an FEP for this so it is more easily implemented by others.
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 ♥️🇪🇺
@rimu@piefed.social interesting, how does this differ from tags?
Edit: I see the other post you made. I’m interested in this but hoping you’ll write up an FEP for this so it is more easily implemented by others.
Let’s clarify something here. Mastodon follower only posts don’t have the “public pseudo user” addressed, do they?
That’s the important piece that this whole thing hinges upon
If it is present, Mastodon is a fault. If not, Pixelfed messed up.
Am I mistaken?
For example, a followers-only post is addressed to the followers collection of the author, at minimum. When NodeBB sees this, it doesn’t even consider it public, because the public pseudo user isn’t addressed. We also have no concept of “followers only”, but we handle them just fine.
@lost_my_mind@lemmy.world hate to break it to you, but Nokia sold their brand to HMD Global, and their new phones are … lacking in the indestructibility department. They are hefty though, I will say.
I owned two of them, and I got the ones that worked well. Some of the QC was wonky too.
@deadsuperhero@lemmy.world OMG roastmaster Sean, where can I subscribe to hear more of this.
@fxomt@lemm.ee this summary is gold.
I think the FEP process is overly complicated for what it is, but it’s definitely helpful if you have multiple implementors on board.
The easiest (but least accessible) solution is to document something on your own site, but that lacks the social proof that a finalized FEP has.
Just some food for thought 🙂 I’m looking to create an FEP for cross posting and would love to get the entire threadiverse dev community involved.