By the way, I am now officially tied to a device which is too old to support Anubis.
-
@alexia@starlightnet.work @sneexy@booping.synth.download i figure the latter is slow because it's running a newer and thus more bloated android version
i have an android 7 phone with 2gb of ram and it runs fennec quite well, though admittedly i'm used to stuff stuttering a bit, my bar for those things is low
-
@alexia@starlightnet.work you have disabled GMS on it right? it makes a world of difference
@soop that device doesn't have it installed to begin with -
@pndc@social.treehouse.systems @alexia@starlightnet.work not really no iocaine is a complete alternative to anubis
-
@pndc @soop
eh, it depends.
iocaine can be configured to do a lot of the same things as Anubis whilst also serving LLM scrapers markov-chain garbage
That is, it can be configured to serve a javascript challenge like Anubis uses, and I think that the developer uses such a challenge on their own stuff too and has it in their nam-shub-of-enki configuration
but, yeah fair enough, moving is a bit of effort; Not because it's difficult but just because it'll obviously take some time to read the docs and move things around -
I think the biggest statement that I want to make here is this:
Software should be efficient, and fast. We've all forgotten what it means to be on a platform that is restricted ever since our computing resources started going up, and this is where it left us.
Those less fortunate are unable to view even the simplest pages because there is software in front that simply won't run on my device.
Our software isn't quick or snappy anymore, to the point where any software which IS quick or snappy markets itself as being so. It has become a marketing feature.
Sure, all our new fancy tech is quite nice, but let's not forget that not everyone is as fortunate.
I am very glad that there's tools which work even on the cheapest or oldest devices.@alexia I have a fairly new phone with 8 damn gigabytes of RAM and I'm still astounded at how bad Android runs. I seem to remember the home PC back in the day having 500MB of RAM, and it ran Windows XP with probably the same performance, maybe slightly better??
-
I think the biggest statement that I want to make here is this:
Software should be efficient, and fast. We've all forgotten what it means to be on a platform that is restricted ever since our computing resources started going up, and this is where it left us.
Those less fortunate are unable to view even the simplest pages because there is software in front that simply won't run on my device.
Our software isn't quick or snappy anymore, to the point where any software which IS quick or snappy markets itself as being so. It has become a marketing feature.
Sure, all our new fancy tech is quite nice, but let's not forget that not everyone is as fortunate.
I am very glad that there's tools which work even on the cheapest or oldest devices.@alexia@starlightnet.work this is why I don't run anubis, and why I dislike most webapps
-
@alexia@starlightnet.work this is why I don't run anubis, and why I dislike most webapps
-
In other words, I encourage you to look to other solutions.
Some that I know of in no particular order:
- go-away – alternative with No-JS challenges and more customizability
- Iocaine – actively poison AI scrapers, best paired with nam shub of enki configuration
I heard mumbles that Anubis is also getting No-Javascript methods eventually, but I don't know more than that.
Anubis has No-Javascript challenges, there's some more advanced ones in the paid offering
(feel free to add to that list, I had something bookmarked but I've lost it on my old phone) -
To put this into perspective, I cannot visit some static websites that have Anubis deployed, but I can:
- Chat over XMPP using Conversations or use delta.chat for Chatmail
- Hang out on Fedi using Tusky
- Listen to music using any player, or by visiting my local Copyparty instance (which works all the way back to Netscape 4.0)
- Navigate places using Comaps
But visiting websites with Anubis? Nope. Not happening.
Even if it could run, it would probably take me a minute to visit your website.@alexia@shrimp.starlightnet.work you can bypass Anubis by changing your useragent in most websites.
This is how many extensions work https://addons.mozilla.org/en-US/firefox/addon/anubis-bypass/ -
By the way, I am now officially tied to a device which is too old to support Anubis. Not just in the "it takes too long" sense, but also being unable to install any version of Chromium that supports the required APIs.
This is probably what a lot of people which are less fortunate than you feel like.@alexia@shrimp.starlightnet.work this is literally one of the planned slides of my DDoS Mitigation talk (i need to continue writing slides)
-
By the way, I am now officially tied to a device which is too old to support Anubis. Not just in the "it takes too long" sense, but also being unable to install any version of Chromium that supports the required APIs.
This is probably what a lot of people which are less fortunate than you feel like.@alexia I waited until Anubis dropped the no-JS impl before activating it on my static site for that reason tbh.
Ik you suggest iocaine, but insofar as I still have reservations about using that myself (for reasons), I feel like this is a reasonable middle ground:
- static sites get Anubis' metarefresh check (which might get swapped out for other noJS solutions in time; still trialling - ty for the other suggestions in any case!)
- stuff that's just for me or requires JS gets full JS checks, since it's not really gatekeeping anything more than it already was.
But idk, I'm still open to feedback on stuff if people encounter issues with one of my sites.
-
@alexia@shrimp.starlightnet.work you can bypass Anubis by changing your useragent in most websites.
This is how many extensions work https://addons.mozilla.org/en-US/firefox/addon/anubis-bypass/@ulveon I know, but it's not a foolproof solution. I know how Anubis works and there's many that challenge all user-agents. -
@alexia meanwhile iocaine gives me the gibberish no matter what
inb4 yes i know it's just the docs site's strict config
@xyhhx can you visit cyrneko.eu -
@xyhhx can you visit cyrneko.eu
-
@xyhhx mhm okay what browser do you use
I have the same configuration and I actually sort of understand it now
the most common blunder is faked User-Agent and Sec-Ch-Ua headers -
@xyhhx mhm okay what browser do you use
I have the same configuration and I actually sort of understand it now
the most common blunder is faked User-Agent and Sec-Ch-Ua headers -
By the way, I am now officially tied to a device which is too old to support Anubis. Not just in the "it takes too long" sense, but also being unable to install any version of Chromium that supports the required APIs.
This is probably what a lot of people which are less fortunate than you feel like. -
I think the biggest statement that I want to make here is this:
Software should be efficient, and fast. We've all forgotten what it means to be on a platform that is restricted ever since our computing resources started going up, and this is where it left us.
Those less fortunate are unable to view even the simplest pages because there is software in front that simply won't run on my device.
Our software isn't quick or snappy anymore, to the point where any software which IS quick or snappy markets itself as being so. It has become a marketing feature.
Sure, all our new fancy tech is quite nice, but let's not forget that not everyone is as fortunate.
I am very glad that there's tools which work even on the cheapest or oldest devices.@alexia can i ask a quick favour of you? (no worries if not, just ignore me or tell me to buzz off lol). if you visit my profile https://k.iim.gay/@kim in your browser, how long does the scraper deterrence there take to complete on your device? it's something we're testing embedding a very simplified form of in gotosocial as an optional defense for users (defaults to off). but depending on accessibility issues it's not something we're set in stone on keeping. we're ultimately just experimenting with making it easy for users to protect themselves, but only if it doesn't compromise on our core principles of accessibility, ease of deployment and low resource usage (at least on the server side, though you'll see from our extremely minimal web client we do care about that client side too)
-
@alexia can i ask a quick favour of you? (no worries if not, just ignore me or tell me to buzz off lol). if you visit my profile https://k.iim.gay/@kim in your browser, how long does the scraper deterrence there take to complete on your device? it's something we're testing embedding a very simplified form of in gotosocial as an optional defense for users (defaults to off). but depending on accessibility issues it's not something we're set in stone on keeping. we're ultimately just experimenting with making it easy for users to protect themselves, but only if it doesn't compromise on our core principles of accessibility, ease of deployment and low resource usage (at least on the server side, though you'll see from our extremely minimal web client we do care about that client side too)
@kim 13450ms on my ZTE Blade A34 (so, quad-core 1.6GHz)
on the Moto C Plus, it doesn't work at all. Just never loads, as I can't get a browser with the required APIs on this thing
(well except Firefox but it gets OOM'd too frequently)
