In 3 days, the jabber.fr wiki, a niche specialized wiki with a lot of outdated info and only one or two occasional contributors at the moment, has served more than 200 000 pages to shitty LLM bots.
Our PHP and mariadb processes are constantly hammered by them, and most of them are masquerading as normal traffic with browser user agents.
Is there a better solution than blocking off entire countries and cloud provider subnets at the moment?
Le serveur jabber.fr a été brièvement indisponible pour une opération de maintenance il y a quelques minutes.
Plus de détails sur https://statut.jabberfr.org/
#Jabber #XMPP
The only one, that is maintained and developed is probably #Emacs-#Jabber:
https://codeberg.org/emacs-jabber/emacs-jabber
It's fun, but I don't use it, because it's missing most modern #XMPP features, such as MAM, #OMEMO, message replies, message reactions…
If I knew a little bit more of #Elisp — and had more time at hand…
Hi, #Debian #XMPP team member here, and very likely the person who uploaded #Dino and #Gajim indirectly to your Mint distro
I'm using both Dino and Gajim on a daily base and they are pretty stable for me. Dino always crashes after disabling an account (but how often do you do that ) and Gajim almost never crashes for me.
Note, that both #Jabber clients have debug options. Maybe you can find out, what's wrong?
I agree and I would not even say, that my preferred solutions (mainly #Jabber or other federated systems) would be more secure for the threat models Signal tries to counter.
But, of course I can't recommend Signal to my family or to my friends, because they would not be able to reach me then and would wonder why I don't eat my own cat food
However, esp. with #Quicksy (which has an Indian variant now, called #Prav), I'ld say it's equally easy to get even non-tech people on board.
>> 1. I don't want to use Google Android or Apple iOS. There is no first class client for Linux/#Debian/#Mobian.
Build one.
>> 2. I don't want to fuel the Amazon cloud of Jeff B., but prefer services in my home "country", the #EU.
Use #OpenStack or ask an EU provider to use it.
>> 3. I don't want to use a phone number for creating an account. E.g. it makes multi-account setups hard.
>> …grey beard, but I'll stay with #Jabber
How about #Mastodon?
Just reading through the #xmpp / #jabber core specification bc I initially wanted to write an own jabber <-> matrix bridge (the ones that exist either dont work anymore, aren't maintained or didn't work with my usecase), and I seriously consider just scraping that idea.
It's even more awefull of an protocol than HTTP; no length-prefix of messages, malformed xml, and genneraly try-and-error mentality for most of the protocol.
I'm sure, that Signal is secure (for its intended use cases) and can be trusted. But…
1. I don't want to use Google Android or Apple iOS. There is no first class client for Linux/#Debian/#Mobian.
2. I don't want to fuel the Amazon cloud of Jeff B., but prefer services in my home "country", the #EU.
3. I don't want to use a phone number for creating an account. E.g. it makes multi-account setups hard.
Call me an old-fashioned grey beard, but I'll stay with #Jabber
Does anybody know what happened to #xmpp #jabber instance jabber.de?
Status page https://www.jabber.de/?page_id=91
#Monocles Chat makes #XMPP experience better.
Help them by donating to their fundraiser for the awesome work they are doing https://www.startnext.com/en/monocles.
XMPP network needs you because we don't have VC funding or corporate donors.