1. no es un bot
2. ¿donde sacaste esa tontería de que negaba que fuera una agresión? no toda agresión es "sexual assault". esa agresión que recién cometiste, bloqueándolo por una imaginación tuya, ¿acaso te parece bien llamar de violación sexual?, y por lo tanto un crímen? supongo que no. de eso se trata la discusión: de la tendencia de atribuir al término sentidos que no alcanza, que no debe alcanzar, y que tiene buenas razones para no alcanzar, puesto que hay otros términos que no tratan de confundir deferentes tipos de agresión como si fueran lo mismo.
@administrator
as reported by email, I'm facing a problem with frequent authentication token resets when accessing gnusocial.net
it occurred to me that it could be related with a plugin that maintains separate profiles in separate containers.
the login that was getting reset was in one such container. this is posted from the primary container, that still had a valid login.
I don't think this started after the latest browser update, and the plugin doesn't seem to have been updated recently. very odd.
blobs are nonfree by definition, no source code is available for them. (there could be source code under nonfree licenses, but IIRC the only blobs for which there is source code are some signed SOF, where the lack of freedom comes from the tivoization through the signature checking on the hardware, not the binary program proper; indeed, the unsigned binary runs in freedom on existing devices that do not require the signature)
decompiling the binary-only ones is tricky, we don't always know the ISA they're built for, some are encrypted, and then, some are digitally signed to prevent modification, so decompiling wouldn't be enough to recover freedom
hola! hace tiempo que no pasa, pero mis mensajes otra vez se represaron. no llegan ej a @freedo desde hace unos días. ¡ayuda! :-) ¿podrías por favor hacer la mágica que haces para arreglarlo? gracias en adelantado,
ok, the image and css downloader is working, and visiting future archival download pages should be lighterweight on the server than visiting any of its regular pages. I have opened my latest downloaded set, that would have hit the server with over 1k image downloads, and it should have barely registered in the radar
(unlike my sequential download of images for the earlier set, that's probably not going to be much use as the avatars seem to have all expired by now. oh well... I guess I should have downloaded them back then...)
nice, but then I wonder what it is that's blocking based on User-Agent... it's pretty clear that this is what's happening, it's entirely reproducible, and the error message is different from the one I get when an IP address is blocked, because the TLS session is actually established, then abruptly aborted, whereas IP blocking prevents it from being established
now, I haven't even been able to make even *regular* accesses for weeks, because of this setting, and the accesses you're seeing in your logs are either normal browser-based access while I tried to figure out what was going on, or *sequential* page preloads from my scripts for offline reading and archiving, neither of which has ever got IPs blocked. but access with a modified user-agent... that amounts to an instant block on the very first connection, and only when accessing gnusocial.net.
now, maybe it's not about GNU in User-Agent, maybe it's libresoc? or something else?
Here's what I was using before, that stopped working a few weeks ago: "Mozilla/5.0 (X11; GNU libresoc64; rv:94.0) Gecko/20100101 Firefox/94.0"
while what works now has 'Linux x86_64" instead of "GNU libresoc64", and the actual, current version numbers.
@administrator, did you by any chance start blocking https requests based on User-Agent a few weeks ago, or tightened preexisting rules?
I had been unable to access with abrowser for all this time, and could only access over text-based browsers over tor after my home IP got blocked. at first I didn't realize I was getting an unusual error; then I thought it was some abrowser upgrade that broke something; then I upgraded another machine that still worked and it kept on working; then I verified all TLS- and abrowser-related files on this machine and found nothing unusual; finally, I realized both browser profiles in which it failed had a modified User-Agent (to have GNU in the operating system name, rather than the misnomer Linux), but the one in which it worked didn't. once I disabled User-Agent overriding, it started working again. so now I configured the browser to lie about the operating system name when contacting gnusocial.net, and I'm back!
if my diagnosis is correct, could your User-Agent blocking rules please tolerate GNU as the operating system name? TIA,
Alexandre Oliva (lxo@gnusocial.net)'s status on Friday, 13-Jan-2023 05:12:22 UTC
Alexandre Oliva.oO mark zuckerberg downloaded thousands of pictures of college students to bootstrap facebook, got no more than a slap in the wrist and went on to become a serial privacy violator
aaron swarz downloaded thousands of academic papers to bootstrap a public library, got criminal charges, and went on to become a martyr.
they are not the same!
and this is how society shapes the future.
does this look like the future you wanted?
aren't these all Unix systems, even though no Unix code made to them?
why do some people seem so determined to find excuses to write GNU out of history and deny its role and fundamental influence in the systems they use? :-(
you appear to reject the fundamental premise of the free software movement, that the *user* is entitled to control their *own* computing. you want it with a twist: that the *operator* be entitled to control everyone else's computing. those are not the same. you're entitled to your opinions and agendas, of course, but that's not what the free software movement is about.