social.dk-libre.fr is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
“No corporation should have the power to dictate how we teach our children.”
Futurism: Mamdani Blasts Google for Using Monopoly to Bully Schools That Ban AI https://futurism.com/artificial-intelligence/mamdani-blasts-google-bullying-schools @Futurism #Google #bots #education
#Reticulum web #tcp interfaces can get hammered by all manner of malicious web traffic and non-reticulum hits (just like any open #port or service). Do you run an interface? e.g. #backbone or #gateway ? e.g. #port4242 ? Would you use, if available, a maintained central database containing a shit-list of bad IPs ( ipv4 ipv6 ) for updating a firewall regularly? #ids #scrapers #bots #pentesting
| No way: | 0 |
| Yes for sure: | 4 |
| Depends: | 5 |
| Other: | 1 |
What do you call this? A cop-out? An opportunity to fire the professors or reduce their salaries? I feel sorry for the kids who won't see the spark of intelligence or wonder in their mentors' eyes, who won't be able to follow up on facial expressions and body language.
"The university’s business school and Imperial College London create AI digital replicas of some of their professors. Concerns center mainly on intellectual property and the fear that AI will attribute words to them they do not agree with."
El Pais: The time of avatars in the classroom has arrived: Harvard clones its faculty https://english.elpais.com/education/2026-10-19/the-time-of-avatars-in-the-classroom-has-arrived-harvard-clones-its-faculty.html @elpais_america #education #bots #copyright
After the destruction of data centers in Russia, the majority of divisive posts in my social media feeds have disappeared.
This is doing the rounds as "OMG bombing Yandex killed the Russian bots" but it's based on cloudflare stats. All "bot" means in this context is web requests that don't come from a human-operated browser. Could be legitimate crawlers, AI scrapers, form stuffing spam, exploit scanners etc. Since Yandex is a cloud provider, it's no surprise most of the traffic originating from their network is not human. Doesn't say shit about social media "bots" though
https://mastodon.social/@TomsHardware@flipboard.com/117422830599800124
#Zelensky: "When our strikes reached #Yandex’s #datacenters, it suddenly became a little easier to breathe on many #socialMedia platforms. A lot of people noticed it. There was less hate, less division, and fewer provocations. Because there were fewer #bots. It’s pretty clear where those bots were"
#Zelensky: "When our strikes reached #Yandex’s #datacenters, it suddenly became a little easier to breathe on many #socialMedia platforms. A lot of people noticed it. There was less hate, less division, and fewer provocations. Because there were fewer #bots. It’s pretty clear where those bots were"
Russia's Yandex bot traffic nearly eliminated overnight after Ukraine drone strikes cripple multiple of 'Russia's Google' data centers — Ukraine intensifies bombing of Yandex data centers in response to Moscow’s strikes on Kyiv data centers
#Russia #Ukraine #WWIII #news #war #PutinsWar #Putin #Ukrainewar #disinformation #bots #SlavaUkraini
RE: https://mementomori.social/@rolle/117239751453109028
I looked into the bot issue again today. It turns out the bots aren't cracking Turnstile, they are bypassing it entirely by registering directly through the API (POST /api/v1/apps -> /oauth/token -> /api/v1/accounts). Turnstile, CAPTCHAs, and similar tools only protect web signups.
Because of this, blocking usernames, IPs, or email addresses doesn't help for long, as the bots keep rotating them and they are completely randomized.
I added a quick check to our fork in the Api::V1::AccountsController#check_enabled_registrations method: if API_REGISTRATIONS_REQUIRE_INVITE=true is set in .env.production, API registrations will require a valid invite code and return a 403 error otherwise. This does not affect regular signups.
The invite code cannot be guessed, so this should put an end to the issue. We could also achieve the same result in Nginx by blocking POST /api/v1/accounts, but I am not entirely sure what complications that might cause.
We are in the middle of a server migration, so we're keeping work on this to a minimum right now. We'll look into Anubis or Cloudflare anti-bot protections later.
We'll keep an eye on the situation.
«Kernel.org — 98 Prozent des Linux-Kernel-Archiv-Traffics sind wohl keine Menschen:
Bots scrapen die gesamte Sammlung an Kernel-Commits und -Forks. Schließlich ist der Linux-Kernel eine exzellente Quelle menschlicher Arbeit.»
Weshalb erinnern.mich die KI's an den Bots seit je her? Die sind also so intelligent, dass die den menschlichen Arbeit schamlos beklauen (ich weiss Linux ist Open Source aber trotzdem)
#linux #opensource #bots #ki #kernelorg #kernel #arbeit #oss
I have migrated my ActivityPub and Mastodon-compatible bots to use a queue and parallel workers. Synchronized requests were taking too long for many bots with many followers.
Upgrade now if you use my bot software:
https://github.com/nekromoff/mastodon-bots
#bot #bots #mastobots #mastoadmin #mastolivre #fediverse #activityPub #software #webdev #tools #webdevelopment
Excellent article de Jill Lepore (en anglais) dans le New Yorker sur la question de la vérification d'identité et de notre humanité dans un monde de robots.
> “The internet was made for machines to talk to each other,” he says. “It’s a system of protocols for computers to interact and message each other. In the end, that’s what it will be. It will be an internet of A.I. agents, operating on our behalf.”
👉 Are You a Human? | The New Yorker https://www.newyorker.com/magazine/2026/08/17/are-you-a-human
Activity Pub bot instance (Mastodon-compatible) is now in v1.2. Mostly security hardening, some bug fixes + tests and Docker + nginx to deploy along previously available Apache.
Want to run your own bots in Fediverse? This is your quick & easy way to launch.
https://github.com/nekromoff/mastodon-bots
#activityPub #mastodon #mastolivre #mastoadmin #bots #bot #opensource #webdev #php #software
Pour l'instant j'ai opté pour la solution radicale mettre le sous-domaine en 404 ! Pour pouvoir accéder aux autres sous-domaines et services...
🤖#rappel #bots
Si les bots écroulent votre site, il y a peut-être une astuce beaucoup plus légère et simple qu'Anubis pour les bloquer.
https://sebsauvage.net/wiki/doku.php?id=stupidantibot
I wonder if this actually worked somewhere, somewhen, for somebot
Jul 27 07:40:21 skapet sshd-session[71062]: Failed password for invalid user root/bin from 217.156.66.34 port 47552 ssh2
#passwordgropers #passwordguessers #sshgropers #ssh #cybercrime #morons #idiots #bots
It looks like whoever is behind this has finally come for one of my sites. Manually blocking datacenter IPs has worked for a while, but it seems like the traffic is now coming either from residential IPs, or the IPs are just getting spoofed.
Real conundrum. I didn't want to have to set up Cloudflare for the site, and I have to wonder how good they are at catching this anyway, but it might just come to that.
Anyone else has been dealing with this?
Welp, now they came for my personal site.
I already reluctantly added Cloudflare to botwiki.org. But I *really* don't want to have to do that to my site.
This kind of blows. Thanks AI bros.
#indieweb #PersonalWebsite #devops #bots #spam #AICrawlers #enshittification
Bonjour la fédiverse !
Si vous êtes admin d'une instance de la fédiverse, regardez si des IPs du bloc 43.160.0.0/12 (plus précisément des IPs soit dans les plages 43.172.194 à 198 et 43.173.173 à 194)
ne font pas *énormément* de traffic sur votre instance. Si c'est le cas, c'est un bot maléfique, bloquez à vue !
stats récentes de mamot : (hits par bloc)
6434 66.249.
258917 43.172.
497379 43.173.
piaille :
28582 216.73.
230864 43.172.
443057 43.173.
Coté Source :
~614 487 IP sources : rappel, on est sûr du logiciel NON grand publique, un peu niche avec zéro contribution de dev externe a l'entreprise, ce qui est normale.
Si j'enlève les IP de l'infra (monitoring, jenkins, redmine) on enlève ~630 000 requêtes pour 6 IPs.
reste 2 500 000 requêtes et 614 481 IPs ...
~ 582 000 IPs, on fait moins de 10 requêtes (pour un total de 1754808 requêtes soit plus de 50%) dans les détails :
~ 257 998 IPs, on fait une seule requête pour un total de 257998.
36395 IPs, on fait seulement 2 requêtes pour un total de 72790
125627 IPs, on fait seulement 3 requêtes pour un total de 376881
28233 IPs, on fait seulement 4 requêtes pour un total de 112932
15122 IPs, on fait seulement 5 requêtes pour un total de 75610
60216 IPs, on fait seulement 6 requêtes pour un total de 361296
sinon on est ~ une trentaine (et pas tous dev) et en ce lundi de juillet, les bureaux parisiens (ou il y a pas grand monde ~ 3 personnes) ont fait environ 800 requêtes...
donc l'usage "légitime" sur la journée doit être ~ 30 000 requêtes (évaluation haute) soit 1% de l'usage. (bon l'infra compte pour 20% quand même 🙂 )
bref, on n'est pas sur les mêmes chiffres, mais on dépasse largement ton test.
Plusieurs point : l'url du git est ancienne (depuis plus de 10 ans) il y a eu quelques changements, mais globalement ce sont les mêmes urls.
De toute façon, c'est seulement depuis moins de 2 ans qu'on a un nombre de requêtes aussi importantes. Au point de déclencher des erreurs sur le monitoring et d'empêcher l'usage correct de la plateforme.
Je pense que les robots ne sont pas ceux des moteurs de recherche, ils ne parcourent pas internet à la recherche de page a indexé, mais plutôt des robots qui ciblent des URLS particulières " à forte valeur ajoutée" (des urls de code opensource accessible, super pour alimenter des IAs de code).