Patricia, to random
@Patricia@vivaldi.net avatar

There is no war that can be fought with a trapped civilian population. That is not war. If you destroy all infrastructure, bomb the hospitals, ban all media, disrupt the food supply and corral the remaining population into a tiny area and then go after them. That is not war.

SallyStrange,
@SallyStrange@eldritch.cafe avatar
oblomov, to random
@oblomov@sociale.network avatar

I can't seem to load https://journa.host/@w7voa/112412311556827606 so the obvious questions are:

  • is @w7voa blocking me or my instance?
  • is my instance blocking @w7voa or his instance?
  • are we having federation issues again?

cc @gubi

gubi,
@gubi@sociale.network avatar

@oblomov @w7voa

The of sociale.network is public and available here:

https://sociale.network/about

and here:

https://fba.ryona.agency/?reverse=sociale.network

As you can see, we are not blocking journa.host, and they are not blocking us:

https://fba.ryona.agency/?reverse=journa.host

From the admin console Journa.host looks like a known instance to sociale.network, with a working federation. I got the error in the screenshot when trying to follow @w7voa from the web but I can do the follow searching the account on the search bar.

image/png
image/png

splorp, to wordpress
@splorp@mastodon.social avatar

The latest update to my Comment for now contains over 55,000 terms and phrases to help keep your comment threads tidy.

https://github.com/splorp/wordpress-comment-blacklist

Widowild1, to opnsense French
@Widowild1@mastodon.xyz avatar
kushal, to golang
@kushal@toots.dgplug.org avatar

Added #blocklist support to my #DNS server. #golang

SallyStrange, to random
@SallyStrange@eldritch.cafe avatar

You've got anarchist flags and you're blaming the entire population of the state of Texas for the fossil fuel extraction that has taken place there? Fuck off. It's an "evil or incompetent" situation and I really don't care which one it is.

https://metrobus.masto.host/@dogzilla/112083478530394481

SallyStrange,
@SallyStrange@eldritch.cafe avatar

To highlight how ridiculous this is, allow me to share with you that EYE, born, raised, and currently residing in New York State, am currently benefiting from fossil fuel extraction that occurred in the state of Texas. This is courtesy of my maternal great-grandfather's investment strategy, which included buying stocks in Texas oil roughly 100 years ago. As a white man from new England, he had the resources to do that. Meanwhile, the people who live in Texas and work on oil rigs and live next door to oil refineries suffer the consequences of fossil fuel extraction far worse than anyone in my immediate family ever has.

But I'm cool in Dogzilla's eyes just because I was lucky enough to be born in a blue state? While Oscar, my former subcontracted coworker who traveled from TX to NY a couple summers in a row to work for a roofing company, deserves no sympathy?

Best case: unserious carelessness. Worst case: deliberately deceptive sowing of classed & racialized hostility between working class people

hrefna, to random
@hrefna@hachyderm.io avatar

I should probably also say about management:

I don't think you can have a perfect blocklist. I don't think that is achievable.

It is more a matter of "what is this blocklist good for, what will it be used for, and what precautions does it take?"

atomicpoet, (edited ) to random

Due to , I’m recommending these servers for :

All three servers have been used for pushing spam across the Feddiverse. In all cases, I’ve given admins time to moderate and remove spam from their servers, and none of them have taken action. Spam continues to be hosted on those servers, and will likely be used for more spam.

Additionally, admins allow open registrations on their servers. They demonstrate a complete disregard for moderation. I suspect that these are abandoned servers.

These servers are now on my .

hrefna, to random
@hrefna@hachyderm.io avatar

Side note: if you wonder why queer (and especially trans) people seem particularly sensitive about how a is constructed, in part it's because of the history of blocklists in these spaces.

We have a history of real harm being propagated under these lists.

It's also because many trans people have a special relationship to online spaces because of our relationship to both people and ourselves in "meatspace."

Not every criticism is going to be valid, but that fear has a very real basis

hrefna, to random
@hrefna@hachyderm.io avatar

To reiterate: my problem with consensus approaches is that they present a "false consensus" of the world.

Whatever biases are in the source lists? Are present in the output. Often amplified.

Whatever priorities are in the source lists? Are present in the output. Often amplified.

The idea is to remove biases, but that only works if biases in your source lists are normally distributed

Which they aren't. Thus: amplified

But this is obscured and it is presented as "more fair."

1/

hrefna,
@hrefna@hachyderm.io avatar

The lower the consensus needed? The higher the problem of amplification.

We've seen this time and again. It's not a new problem. It predates the fediverse by literally decades.

Sources that depend on each other or on your consensus need to be considered as an existential threat to the reliability of the list. Without protections against these most* consensus lists should be considered highly suspect or even completely invalid.

2/

hrefna,
@hrefna@hachyderm.io avatar

Anyways, again, management is an important topic and it is also important that we get it right and not just use choices because they are convenient.

You don't have to listen to me. Just look at the RFCs in this space.

You can also go through the wikipedia page:

This is not a new debate. There are longstanding best practices and considerations here. We don't need to reinvent the wheel.

9/9

atomicpoet, to random

Due to , I’m recommending these servers for :

In both cases, these servers continue to be used for an ongoing spam attack. I’ve given admins of both servers ample time to respond to reports, and they’ve taken no action. Spam continues to exist on their server, and continues to be sent.

Admins continue to allow open registrations on their site. With complete lack of moderation, spammers will continue to register.

Both servers are now on my .

SallyStrange, to random
@SallyStrange@eldritch.cafe avatar

Ain't it funny how I have to choose between believing my own lying eyes, or believing a guy named "Truth Sandwich"


https://babka.social/@truthsandwich/111972491158509209

atomicpoet, to random

Due to , I’m recommending these servers for :

All of these servers are vectors for an ongoing spam attack. Despite me giving them ample time to respond to reports, they refuse to respond. They show no inclination to moderate, and no action has been taken by them whatsoever.

In all cases, these are abandoned servers with open registrations. It is likely they will continue to be used for sending spam across the Fediverse.

Each of these servers are now on my .

18+ matt, to trustandsafety
@matt@oslo.town avatar

It's really great to discover so many new instances that I have never heard of before, but a bit disappointing to see how many of them are Open Registration and abandoned, leaving them subject to spam bots.

About 1 in every 5 accounts that oslo.town encounters seems to be a proactive spam bot now. It’s ridiculous.

(I say "proactive" spam bot because I imagine there are many more, but the passive ones don't @mention people)

matt,
@matt@oslo.town avatar

@dustin Yes! I haven't implemented it myself, but I saw this the other day which is a specific response to the recent .

https://github.com/Mastodon-DE/blocklists

atomicpoet, (edited ) to random

After the latest attack, I’m recommending these servers for :

Each of these servers served as vectors for the last spam attack. In every case, they have ignored my spam reports that I sent to their admins, and I’ve given them ample time to respond. Spam still exists on their servers, and no action has been taken whatsoever.

As well, I have investigated each of these servers individually, and have determined that they are still vulnerable to spam attacks. Likely, they will be used for spam again in the future.

In most (perhaps all) cases, these are abandoned servers with open registrations, and an admin who has done little or nothing to moderate new users.

Each of these servers are now on my .

bacon, to mastodon
@bacon@cheeseburger.social avatar

Ok so I've thrown together a python tool that you can use to retrieve a list of instances you federate with and then save the domain name, title description of the instance, and the version its running on to a sqlite database. you can then convert that to a csv file and use that to filter out out of date instances and upload it to your server as a block list.

I just threw it together this afternoon so its very crude.

right now its a very slow process for it to run through the list and save the info and I'm sure there is a better and faster way to make it work but im limited in my python skills.

I hope this is useful to someone .

https://github.com/grose1/mastoblock

aral, (edited ) to mastodon
@aral@mastodon.ar.al avatar

Folks on Mastodon, to hide the current deluge of spam:

  1. Settings -> Filters
  2. Add new filter
  3. Add a title (e.g., Spam)
  4. Select all the context checkboxes
  5. Set Filter Action to Hide Completely
  6. Add the following keyword with a hash (#) before it: 診断メーカー

martin,
@martin@openedtech.social avatar

@aral This is all too manual/complex to be sustainable of course, the spammers will win eventually. I hope eventually this will be something we can automate in with servers subscribing to someone we trust to keep such a up-to-date in real time.

Then again, I fear we’d slide into the same situation as email, where all-powerful blocklist companies control the flow of everything, and if someone puts you into one of those lists, enjoy the months of fighting it will take to get off them (if you can).

Anyone know some existing middle-ground solution/proposal that could work for collaboratively inoculating against spam in the ?

pgl, to ads

Weekly block list report: 3,804 entries; 3,783 valid / 21 invalid; 3 deleted

pgl, to ads

Weekly block list report: 3,807 entries; 3,786 valid / 21 invalid; 0 deleted

pgl, to ads

Weekly block list report: 3,808 entries; 3,781 valid / 27 invalid; 3 deleted

pgl, to ads

Weekly block list report: 3,810 entries; 3,782 valid / 28 invalid; 6 deleted

stratosphere, to random

Today's top 10 malicious IPs from our #AttackerIP #blocklist. Full list: https://bit.ly/StratosphereAIPBlocklists
91.205.93.69
15.235.181.139
46.29.227.46
92.63.197.97
49.88.112.72
139.180.138.223
79.124.62.86
185.45.194.176
139.180.129.34
79.124.62.82
79.124.62.130

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • magazineikmin
  • Youngstown
  • osvaldo12
  • khanakhh
  • slotface
  • tacticalgear
  • InstantRegret
  • ngwrru68w68
  • kavyap
  • DreamBathrooms
  • thenastyranch
  • everett
  • rosin
  • provamag3
  • Durango
  • GTA5RPClips
  • ethstaker
  • modclub
  • mdbf
  • cisconetworking
  • anitta
  • Leos
  • cubers
  • normalnudes
  • tester
  • megavids
  • lostlight
  • All magazines