db0

Please take a look at the guarantee solicitations page and see if you can guarantee for some instances that you can tell are not spam

The Fediseer relies on crowdsourcing information about the fediverse, so the more of us doing this, the easier it becomes.

Cross-posted from "Threativore can now keep your blocklist in sync with your Fediseer censures" by @db0@lemmy.dbzer0.com in !lemmy_integrations@lemmy.dbzer0.com

The new release of Threativore adds Fediseer integration. It will allow you to keep your instance blocklist in sync with your fediseer censures. Not only that but the integration can be as fine-grained as you want, supporting collating multiple instance censures, filtering only censures with tags you want, or only censures collaborated by 1+ other instances etc.

Check out the usage manual for all the variables allowed.

For people who only want some basic protection, the default settings will by default protect you from all CSAM and bigoted instances as tagged by lemmy.dbzer0.com, lemmy.world and lemmings.world. This should provide a good initial blocklist even if you don't populate fediseer yourself Bbut you can of course mix&match according to your needs.

This integration also prevents too many changes happening at one go in your blocklist. If threativore detects too many changes about to happen, it will ask for admin approval via DM before proceeding.

This sync will run every 10 minutes, so if you're following the censures of other instances and they discover a new bad actor, you'll be almost immediately protected, thus converting a fediverse weakness (information distribution) into a strength (information collaboration).

Let me know if you wish to see any improvements.

Let's go for 5 and 10 at least!

There's a few open solicitations. Please take a look and guarantee for whoever doesn't look like spam to improve the health of the chain.

I should arrange somehow so that the newest instance to be guarantee'd automatically gets pinged when someone solicits one, just to keep things going as nobody pays attention.

Taken from microblogging

Some extracts:

Stunningly, Automattic’s CEO Matthew Mullenweg threatened that if WP Engine did not agree to pay Automattic – his for-profit entity – a very large sum of money before his September 20th keynote address at the WordCamp US Convention, he was going to embark on a self-described “scorched earth nuclear approach” toward WP Engine within the WordPress community and beyond. When his outrageous financial demands were not met, Mr. Mullenweg carried out his threats by making repeated false claims disparaging WP Engine to its employees, its customers, and the world. Mr. Mullenweg has carried out this wrongful campaign against WP Engine in multiple outlets, including via his keynote address, across several public platforms like X,YouTube, and even on the Wordpress.org site, and through the WordPress Admin panel for all WordPress users, including directly targeting WP Engine customers in their own private WordPress instances used to run their online businesses

During calls on September 17th and 19th, for instance, Automattic CFO Mark Davies told a WP Engine board member that Automattic would “go to war” if WP Engine did not agree to pay its competitor Automattic a significant percentage of its gross revenues – tens of millions of dollars in fact – on an ongoing basis. Mr. Davies suggested the payment ostensibly would be for a “license” to use certain trademarks like WordPress, even though WP Engine needs no such license. WP Engine’s uses of those marks to describe its services – as all companies in this space do – are fair uses under settled trademark law and consistent with WordPress’ own guidelines. Automattic’s CFO insisted that WP Engine provide its response to this demand immediately and later, on the day of the keynote, followed up with an email reiterating a claimed need for WP Engine to concede to the demands “before Matt makes his WCUS keynote at 3:45 p.m. PDT today.”

In parallel and throughout September 19 and 20, Mr. Mullenweg embarked on a series of harassing text messages and calls to WP Engine’s board member and also its CEO, threatening that if WP Engine did not agree to pay up prior to the start of Mr. Mullenweg’s livestreamed keynote address at 3:45pm on September 20, he would go “nuclear” on WP Engine, including by smearing its name, disparaging its directors and corporate officers, and banning WP Engine from WordPress community events.

They... they have text message captures. In the pdf. Matt Mullenweg was trying to extort them ... by text messages. They seem to have the entire thing in the writting.

In the final minutes leading up to his keynote address, Mr. Mullenweg sent one last missive: a photo of the WordCamp audience waiting to hear his speech, with the message that he could shift gears and turn his talk into “just a Q&A” if WP Engine agreed to pay up

They finish requesting Automattic to "preserve, and not destroy, any and all documents or information in their possession, custody, or control that may be relevant to any dispute between WP Engine and Automattic". They are going to war, big time.

All this crap is just because they refuse to pay his protection money. And the guy has been stupid enough to put everything in writting.

There's a bunch soliciting guarantees. As part of fediseer, it falls on all of us to maintain it. So please check the new instances and guarantee for any that are not spam (which should be most).

Click this link to guarantee for some instances

Also reminder if you're the admin of an instance requesting a guarantee, by specifying who should be your guarantor, you will send them a PM to ask them.

New instances require a guarantee to use fediseer to its max capability. If you see an instance and you validate it's not spammy, go ahead and guarantee for it.

If you yourself want to solicit a guarantee, remember that you can input a target instance when you do so, and their admins will receive a PM from the fediseer to do it for you.