rolle@mementomori.social I'm sorry this happened to you. It's so easy to hurl hurtful accusations with no accountability that one ought to treat them as you would treat drive by criticisms. I'm pretty far down the spectrum from a "tech bro" but I still got called one simply because NodeBB federated and dared to serve that content online (nevermind that every other fedi server does the same). In that scenario there was nothing I could do as an individual except wait for an instance mod to lay some facts out. Anything I said was instantly derided, even if it was the same thing. So if I reply with courtesy and I get back vitriol, why do I bother? I don't now. So maybe that's more tech bro-y.

jsit@social.coop Ghost? NodeBB? Just to name a couple

nutomic@lemmy.ml let me know if I got any of the details wrong. Much thanks to your team for the assist in debugging!

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.

@trwnh@mastodon.social but why must a separate account be made? Account fragmentation is yet another unsolved problem because the new user on account B is functionally useless: no followers, etc. and the content isn't automatically available to the followers of the user on instance A.

@willi@social.tchncs.de a VPS can be had from DigitalOcean or Vultr quite economically (although I know that isn't always the case in some countries) You can also use our referral link for an account credit too!