julian

> @bentigorlich@gehirneimer.de said in A more private way to distribute votes: > > So my proposal would be: votes are only sent to the author of a post. The author then sends an Update activity to their followers and the magazine the post belongs to.

My concern is that this goes against the implicit assumption that the group actor (the community/magazine/category) is the source of truth.

The group actor is the clearinghouse of data in 1b12 style federation, and it would be a departure to change votes to only be sent to the target.

Fwiw when someone upvotes on NodeBB, it gets blasted everywhere too!

I would recommend that votes continue to be sent to group actors, who then decide whether to announce it (old behaviour) or keep quiet and wait for the update before announcing (new behaviour).

It would mean vote synchronization would be less reliable however.

Also this goes directly against @rimu@piefed.social’s vote batching proposal.

@panos@community.nodebb.org Was not able to resolve the post, but I don’t think it’s your fault, lemmy.world turned on CF bot protection and it’s blocking me :(

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

@rabiezaater@piefed.social 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.

To my knowledge, Catodon was started by @panos@catodon.rocks, who for the longest time was a Firefish advocate, but was disappointed by the bait and switch pulled by those devs.

With the advent of AI, Panos is taking it upon himself to fork Firefish and build the social media experience he wanted all long.

Can’t really argue with that :smile:

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.

Isn’t that basically a Piefed topic?

I’m talking to you from it right now 🤨

@ntn888@lemmy.ml yep, it’s a forum you can self host.

https://github.com/nodebb/nodebb

Or join activitypub.space (but that one is geared toward fediverse developers)

Different software can do this in a less privacy invasive way.

NodeBB has “popular” filters that show you what is generating discussion (per day, week, month, etc.)

The potential for abuse or culture clash comes when these disparate (yet related) communities are combined.

From a user perspective it may make sense to expose “related discussions” that you can browse to. Keeping the discussions separate yet linked could be a workable compromise.

> @emb@lemmy.world said in Pluralistic: The online community trilemma: > > a) A community of like-minded people; > > b) Useful information; and > > c) The largest possible audience.

Calling it now. Join @fediverse@lemmy.world to discuss the fediverse. Join the smaller @fediverse@piefed.social to discuss the fediverse and rag on tankies.

/s?

About batched votes? Yeah I did, just haven’t responded yet 👍

> @a_gee_dizzle@lemmy.ca said in Mastodon not federating to Lemmy?: > > So my question is, does anyone know what caused this and if so how I can fix it?

Mastodon doesn’t know to send replies to the community for distribution to the rest of the threadiverse.

Long story short if you’re not on the same instance as the community, Mastodon replies to you won’t make it to the rest of the threadiverse.

I experimented with a hack to see if I could fix this. NodeBB works around this by including a hidden mention to the community that Mastodon will then pre-fill in the text box, and then the reply will make it in successfully. If you have a Mastodon account try to reply to this comment, the community will be pre-filled as a mention.

Piefed, Lemmy, and Mbin will need to do this.

Does it work? Yes

Are we supposed do it? Technically no, it’s easier to blame Mastodon for not doing it right.

Should we do it? Probably, yes.

@rimu@piefed.social @nutomic@lemmy.ml @bentigorlich@gehirneimer.de @melroy@mastodon.melroy.org I tested this. It works perfectly fine. We can implement this today and remove it when Mastodon supports threadiverse conversations better (I’ll try to make that happen.)

Theoretically yes.

Practically, only sometimes. Mastodon doesn’t know to send the reply to the community (or even just a user from that community), so when replies are made that don’t include the community, then they don’t get make it through to the threadiverse.

Mastodon users (if they’re following the community) will get everything, but the UI for reading threadiverse content is abysmal 😝

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

Maybe it’ll help Piefed and NodeBB too!

@anthony@forum.unfinishedprojects.net did you just remove the privilege from “fediverse”? Leave it on for “registered-users”

Edit: oh I see what you mean. Let me take a look at this tomorrow.

A heartbeat activity! Or maybe a ping.

I like it! Maybe I’ll write an FEP for it, lol.

Thanks, I mean, how does this work in the backend?

How does this work anyway, and does it match with Lemmy’s approach?

I noticed crust was saying my dev instance was not federating anymore, which was neat. It was because I don’t leave my dev instance online all the time 😁