Pretty sure if Obama, Clinton, Biden, or Harris said "praise be to Allah" in a tweet the media would crucify them no matter the context.

But when Trump does it, crickets.

It's a good approach, it's exactly how NodeBB operates as well.

We have a FOSS software and we sell managed services for those who don't have the technical know-how.

Win-win.

Yes. It is being worked on, and you are not far off.

Respondents here have mentioned that Piefed and Lemmy list cross-posts in places, sometimes in the community listing, sometimes in the post itself.

That's missing the point, which is that the conversations should be combined.

Take it a step further, though. You shouldn't have to combine posts, they should all be the same post.

So how do we get there? Both Piefed and Lemmy do this internally, and don't expose this to other instances. NodeBB (aka me) is hoping to explore this question and put in the protocol research to make this a reality. I'll be working together with members of the Forum and Threaded Discussions Working Group about these things. ([email protected])

The issue (as usual) is buy-in from Lemmy and Piefed (and don't forget mbin!) We all have to move in lockstep so that nobody gets left behind.

We've only just started discussions on how this might work, but hopefully we'll be able to make this a reality soon.

Indeed, this is where the majority of improvements to the Fediverse are shared for archival.

The very way Lemmy Piefed Mbin and NodeBB can communicate and synchronize communities is detailed in those FEPs. Check out FEP 1b12.

Instructions unclear, am now a politician, doctor, or lawyer.

NodeBB has a question and answer plugin that does something similar. We can adapt this functionality and make it work between Piefed and NodeBB as well.

One thing I'd like to see is a property on OP (or maybe the context!! 😁) designating the selected answer. Otherwise if the activity is missed then it won't ever be seen again.

In a weird roundabout way a disclosure gives me more reassurance.

If a software package went on for years and years without a peep with regard to security fixes or disclosures, I'd start to wonder what they're hiding.

Thanks for the link back, I appreciate it!

One neat side effect of this is that if the microblogiverse backfills from the threadiverse, and vice versa, then you have in effect built a bridge connecting the two disparate 'verses.

We're not there yet — this step only exposes conversational contexts so that consumers (like NodeBB) can backfill from them. Neither Lemmy nor Piefed have signalled intent to consume contexts yet, but as it is a relatively new extension, there is no telling what may happen in a week, a month, a year... :)

Also [email protected] is pretty darn responsive and if you as (very) nicely that would go a long way.

I mean, yes, but there's also an implicit social contract with fediverse software that you probably shouldn't scrape without federating back...?

Curious... Can you share more details about what they changed that fixes federation with Lemmy?

Maybe it'll help Piefed and NodeBB too!

Very cool to see fresh new forums popping up! I've written a NodeBB-specific federation kickstart guide here that you may be interested in 🙂

https://community.nodebb.org/topic/19228/federation-community-kickstart-guide

There are comparatively few instances that federate, since we are new to the activitypub game.

I made the decision that if you upgrade to v4, AP is turned off. Install a new instance of NodeBB, and ActivityPub is enabled out of the box.

Side effect of that would be all instances running prior to v4 won't be federating, but at least there will be no surprises!

Here's a list, but it's not listed by topic or genre.

https://nodebb.fediverse.observer/list

triggered

> @[email protected] said in Rimu Mass Bans Users: > > Rimu pushed a piece of code into Piefed a few days ago specifically to silence criticism against him and to silently delete/block posts on Piefed.

Extremely concerning.

I knew there was hardcoded stuff to block instances, but this goes further... got a link?

I'll give some insight from NodeBB.

Adding in delays (x days until first post, y hours until upvote, etc.) do nothing to curb spam.

If your spam is manual, they will discover the waiting period, update their rulebook, and go to town when the waiting period is over.

If the spam is automated, it will work until the spammer admin discovers the waiting period, updates the script, and has the bots resume going to town when the waiting period is over.

At the same time it severly hampers usability at its most crucial (the first post).

The only thing that works to curb spam is a post queue with manual review... or locking the ability to post links behind reputation.

@[email protected] not all instances enable them. I think Piefed can restrict them in some manners (local users only, or something), and in NodeBB you can disable them completely.

It's not an all-or-nothing proposition, if you think downvotes are not good, run a software (or join an instance) that doesn't have them enabled.

@[email protected] very cool, and nice recommendation with deflect...

The pricing concerns me (especially since we using Cloudflare is a $0 cost)... At $10/5000 unique users, what if I get hit by a DDoS and my costs balloon?

Anyway I suppose that's a question for them, not you 😁

> is that an issue for the Threadiverse? I thought all replies are collected by the host instance of the community.

You're not wrong about that. Threadiverse software (Lemmy, Piefed, and NodeBB too) use something called 1b12 to synchronize content between instances.

If you follow a community, you set up the synchronization from your server to that community from that point forwards.

This is similar, but not quite backfill, which is what happens if you follow a community mid-way and don't have any of that stuff from before.

Also you can't 1b12 synchronize with Mastodon, so that unfortunately is a dead-end, but you would hopefully be able to backfill from Mastodon.

I disagree. I think that you can have both.

I think big tech has proven that it cannot be trusted. Their priorities are simply not in alignment with our own. Legislation seems to be the only lever that can hope to rein them in (market forces are no longer strong enough).

At the same time, smaller networks do not have the resources to comply with government regulations to a T, and so they should be given a longer leash. Governments also do not have the resources to chase down every Tom, Dick, and Harry running a Lemmy server (well, they do, but they shouldn't.)

Whether reality will play out this way is uncertain.

Now this is a good reason to move a community to a different region.