CIRCLE WITH A DOT

And for today, a Bible verse reading from Quentin Tarantino, because I'm a very serious Christian.

@blogdiva Fuck his peacefully making paintings, he should wake up every night wracked with guilt. He should never sleep comfortably for the rest of his cruel, miserable life. So much of where we are today I can lay right at that asshole's feet.

@renchap @sovtechfund Super excited to hear about the FIRES work. Feel free to use https://fires.1sland.social for testing/consuming various datasets.

@Urban_Hermit @Strandjunker Back in 2016, the evangelicals who used to be in my circle (before I left Facebook) proclaimed a commonly held evangelical belief about Trump.

That he's like David.

And that "God uses sinful man to accomplish his will."

That's where the endless forgiveness for his transgressions comes from.

@jwildeboer Server side page generation is the dynamic creation of .html pages. The application server is just about allowing you to edit the content and then 'publish' it to static html.

That's my understanding of it.

Posty basically uses server-side page generation to take your Mastodon archive and produce a zipfile full of HTML pages.

@blogdiva I think not having the 'follow quota' also helps us defeat a lot of that that artificial limiting behavior.

I'm sure you ran into it there all the time, but I didn't even realize until after I left Twitter that the whole reason for 'follow back' was because you're not supposed to have a much higher ratio of people you follow than people who follow you, something asinine like that?

One time here someone got mad because they followed me and I didn't follow them back and I was like, "Wrong platform."

@Ashedryden

From "Break on Through" by the Doors:

"Ev-ry body loves my baby
"Ev-ry body loves my baby...
"Chicken!
"Chicken!
"Chicken!
"Chicken! Aaoaoaoaoh!"

https://youtu.be/gdnzBNMfZfo?si=Fldd36cs3ekcQ1R7&t=76

@fatsam I'd say that's what Facebook is for, nowadays. Seeing what you can push through the signal filter before they ban you for calling a spade a spade....

In the name of unrestricted free speech, of course. Maybe if you threw in an arbitrary r-word or two, alas.

He's the exact same motherfucker. He didn't magically decline over the last few months or days, it's just he's been so normalized that he has to threaten to eradicate an entire civilization before people wake the fuck up and go, "Oh wow, he's evil."

And then they go, "Well...maybe not evil. Maybe just deranged."

Oh FUCK YOU ALL.

@SecureOwl @GossiTheDog I mean, if this keeps up, we might have to reduce ICE's budget by 2% to show them we mean business.

@taylorlorenz @rwg <- that would be someone I'd talk to, since he did a lot of research on the Fediverse and wrote a book about it.

@thisismissem It's been a lot of fun. My next trick is to tie this into Fediblockhole so that FIRES just becomes another source you can pull in data from to build lists or push blocks to your server if you so choose--while also allowing Retractions to literally pull blocks off your server with it, adding a statefulness we didn't have before in Fediblockhole. Which I imagine is still a pretty common way to pull blocks, but imagine a Fediblockhole config like this:

blocklist_fires_sources = [
  # { server = 'https://fires.1sland.social' },  # all datasets on this server
  { server = 'https://fires.1sland.social', datasets = [
    '019d36a7-fb61-7d3d-9228-b0e658f7ef0c', # Oliphant Ad Hoc Fediblock list
    '019d36a7-3274-77a4-8ee9-9f26dd2faa4f', # Seirdy's FediNuke
    '019d36a7-f621-7842-a00b-35cc2fecc8d7', # Gardenfence
    # '019d36a8-024f-7f44-855f-dfdf5badf536', # The Bad Space 90% Consensus
    # '019d36a7-34e0-7515-9990-58196d3ab9eb', # FreeDNS (25k domains, very large!)
    '019d36a7-f91a-7837-aeea-fb2ae48b67fe', # IFTAS AUD
    '019d36a7-f9a1-7546-8dd8-e88b14834cdf' # IFTAS DNI
    ], retractions = true },
  { url = 'http://localhost:4444/datasets/019d37ae-8f62-74ec-95f5-92ce0dba4ea4', retractions = true },
  # { url = 'https://other-fires.example/datasets/019d3565-f022-777b-abbc-aabbccddeeff', max_severity = 'silence' },
  # { server = 'https://fires.example.com', ignore_accept = true },  # ignore 'accept' policies
  # { server = 'https://fires.example.com', retractions = true },  # honor retractions from this source
  # { url = 'https://trusted-fires.example/datasets/uuid', retractions = true },
]

You did nice work.

I'm working on a PR for this in Fediblockhole, too. It supports many formats, and talking to FIRES gives it state management for retractions it's never really had before--I mean, there's an explicit 'Retraction' type.

@thisismissem @iftas They are regularly updating their CSVs, I thought. I've been pulling updates:

https://archipelago.1sland.social/blocklist/IFTAS%2DDNI
https://archipelago.1sland.social/blocklist/IFTAS%2DAUD

And that means they now have a regularly updated dataset for it now, too:

https://fires.1sland.social/datasets/iftas-abandoned-and-unmanaged-denylist
https://fires.1sland.social/datasets/iftas-do-not-interact

For my linux nerds

curl -s -H 'Accept: application/ld+json' 'https://fires.1sland.social/datasets' | jq

The FIRES reference server does content negotiation, so hit https://fires.1sland.social/datasets in your web browser, and then hit it with a proper JSON header and you'll see different results.

There's also a labels endpoint:

curl -s -H 'Accept: application/ld+json' 'https://fires.1sland.social/labels' | jq

Which also responds as text/html.

@nlupo @thisismissem It's something different (csvs, json, and flatfiles) but it could use this. It would just be another (much more nuanced) format.

Every night the blocklists are updated, and now when that happens we'll also add new recommendations or retractions to the FIRES dataset as well, automatically. Pelago and FIRES are essentially married in my implementation now, able to pass some FIRES configuration to a Pelago instance, prefilling the IFTAS labels and seeding the data from configured/enabled blocklists.

Of course we can add other labels and stuff eventually, but I felt like IFTAS did a good job covering most of the bases rather than creating non-standard (albeit delightful) labels like 'edgelord' and 'fuckface'.

"But I don't like that blocklist project!"

That's why you completely ignore that dataset, then. Pick the dataset you trust and go from there. Eventually datasets will be created by more than just blocklists. They'll be organic community contributions, perhaps, authored by a council directly on the FIRES server--that can be a whole other dataset.

In the meantime, we've got a protocol for syncing moderation advisories, y'all. Just need the consuming software (ie., Mastodon, GTS, Akkoma, etc) to start ingesting it.

This is also how GoToSocial could take a filter advisory to disallow replies from an entire server or from specific accounts.

In fact, the Domain Limits, interaction control and (eventually) canQuote logic all fit into the filter advisories, and I suspect with an existing Domain Subscriptions model, connecting to a FIRES dataset or /changes endpoint is going to be possible, just needs to get on the roadmap.

FIRES allows for advisories against Fediverse actors, as well.

This is very, very similar to 'composeable moderation'. You subscribe to a dataset, and you can either grab the latest snapshot or subscribe and pull changes over time, so a retractions come in you can have things pulled off your blocklist.

It also adds a bit more nuance. Things start out as advisories and can escalate to recommendations, but even a recommendation of 'drop' doesn't mean autoblock, it's supposed to be a suggestion to your software (Mastodon, etc) to give you an option or to allow you to auto-accept. You might not care about things tagged with a label of 'Spam' so you let those through, for instance.

This is essentially the protocol the Fediverse has needed to allow for sharing nuanced moderation recommendations. All you need to do is find a dataset or datasets you want to subscribe to, and can pull in those changes.

This is all based on the work done by Em, the FIRES server I'm hosting is her reference server implementation, I'm just sideloading it from Pelago.

Everyone is free to use my fires.1sland.social server as a real FIRES server for development purposes, in terms of testing the protocol.

No retractions yet, but those will show up over time.