There’s the problematic fact that open weight LLMs are still trained by these corpos, which definitely has some environmental impact. It’s troubling.

However what doesn’t? As long as I’m not actively burning absurd amounts of fossil fuels running queries…

It’s tough to know where to stand when it comes to AI. I don’t think anybody here is hoping that the fediverse be overrun with LLMs and bring about the dead internet theory.

A large part of why people join the fediverse (and the threadiverse, too) is to get away from corporatization, and AI is definitely part of that too.

I just don’t think we need to go to extremes to ban AI-generated content, but more importantly, this is not a decision that can be made globally. It must be done (and enforced, however we do that) instance by instance.

well there’s an NSFW Lemmy and Piefed instance now :smirk:

@[email protected] I think with public groups this is less of a concern. They’re public after all, votes included

In NodeBB votes (of the up variety) are de facto public, only downvotes are hidden.

> @[email protected] 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 @[email protected]’s vote batching proposal.

you betcha: https://docs.nodebb.org/api/write

Oh you definitely can!!, I’m able to browse and subscribe to Piefed and Lemmy communities as though they were categories 😁

@[email protected] does it work with NodeBB? :angel:

@[email protected] I’m also not able to fetch it directly

https://catodon.rocks/notes/akv4dziup8bz00hy sends HTTP 401 to my local dev instance. Might be because it’s a localhost address.

It loads on from a properly hosted instance though :)

@[email protected] 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 :(

Sure. I have found that the default botPolicy works fine for blocking the AI bots, but blocks federation.

At the reverse proxy level:

if ($request_method = POST) {
    proxy_pass http://nodebb/; 
}

Because Anubis can’t filter by HTTP method, unless I am mistaken. This just broadly allows all incoming activities. If you want to get specific, limit it to your shared inbox or individual user inboxes via regular expression or something. I didn’t find that it was necessary.

As for botPolicies.yaml

  # Allow /inbox
  - name: allow-ap-headers
    headers_regex:
      Accept: application/ld\+json; profile="https://www.w3.org/ns/activitystreams"
      Accept: application/activity\+json
    action: ALLOW

  - name: allow-assets
    path_regex: /assets
    action: ALLOW

The former allows those specific AP headers (it is naive, some AP impls. send slight variations of those two headers.

The latter allows our uploads.

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.

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

… and how, pray tell, are they supposed to do this, logistically?

Station inspectors in every maple syrup farm? Who’s paying for that?

@[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.

To my knowledge, Catodon was started by @[email protected], 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:

A bank probably would, but I don’t know if they’d do it for just anyone.

More importantly, if you’re crossing a border with large sums of cash, you must declare it at the border.

CBSA is not in the business of stealing money, but they will confiscate it if you don’t declare it.

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.

For a fediverse based technical support hub, have them post to @technical-discussion

More than happy to help. Fedify is good, but they might not be using js 🙂

Isn’t that basically a Piefed topic?