It certainly is not negligble compared to static site delivery which can breezily be cached compared to on-the-fly tarpits. Even traditional static sites are getting their asses kicked sometimes by these bots. And yoy want to make that worse by having the server generate text with markov chains for each request? The point for most is reducing the sheer bandwidth and cpu cycles being eating up by these bots hitting every endpoint.

Many of these bots are designed to stop hitting endpoints when they return codes that signal they've flattened it.

Tarpits only make sense from the perspective of someone trying to cause monetary harm to an otherwise uncaring VC funded mob with nigh endless amounts of cache to burn. Chances are your middling attempt at causing them friction isn't going to, alone, actually get them to leave you.

Meanwhile you burn significant amounts of resources and traffic is still stalled for normal users. This is not the kind of method a server operator actually wanting a dependable service is deploying to try to get up and running gain. You want the bots to hit nothing even slightly expensive (read: preferably something minimal you can cache or mostly cache) and to never come back.

A compromise between these two things is what Anubis is doing. It inflicts maximum pain (on those attempting to bypass it - otheriwse it just fails) for minimal cost by creating a small seed (more trivial than even a markov chain -- it's literally just an sha256) that a client then has to solve a challenge based on. It's nice, but certainly not my preference: I like go-away because it leverages browser apis these headless agents dont use (and subsequnetly let's js-less browsers work) in this kind of field of problems. Then, if you have a record of known misbehavers (their ip ranges, etc), or some other scheme to keeo track of failed challeneges, you hit them with fake server down errors.

Markov chains and slow loading sites are costing you material just to cost them more material.

If I had a nickel for every time someone ignored me just to say something I directly address...

You are pretty blatantly referencing X11 Forwarding / Network Transparency.

I can't reasonably assume you actually read anything I say, but to briefly reiterate:

Checkout Waypipe. Here's a direct quote from the README:

Waypipe is a proxy for Wayland clients. It forwards Wayland messages and serializes changes to shared memory buffers over a single socket. This makes application forwarding similar to ssh -X feasible.

Have you tried this? What is disatisfactory about it? And if all else fails, is there really ANY problem with simply using VNC/etc? What real-world problem do you have that is uniquely solved with this?

What? I've gotten RDP, VNC, and SPICE working fine on Wayland. And if you need app-level displays then waypipe worked fine the last time I used it. I've been running Proxmox containers with Wayland just fine, too.

Any particular use case that benefits from what Xorg was uniquely capable of networking-wise (network transparency, afaik?) of is quite niche and development effort twoards that end has always reflected that!

I've not been able to find the git or project repo/writeup of "Wayland on Wires". Though i do vaguely feel like I saw it somewhere.

But I suppose me and my ongoing computer science degree and shared family hobby of IT simply hasn't reached Real Linux User levels yet. I must sharpen my Bash Blade for another 1000 years...

Since that's the case, I suppose I must defer to your Infinitely Endless Wisdom as a True Linux User. I beg of thee, answer my Most Piteous Questions...:

1. What do you use Xorg's networking functionality for?
2. What is ""real"" Linux work?
3. Why can't you use Wayland for that?
4. Have you heard of Waypipe? Have you used it?

"Linux as a desktop is BAD!"

"Evidence?"

"I failed to make a slideshow in a buggy application. :'("

In all seriousness, though, wtf? You could have pulled from any of the well-know papercuts and instead you balk about a broken application? Lmao?

My vibeo gaem crashed on Windows once. I guess I should hold Microsoft personally accountable for it....

For the record, I've used Linux throughout Highschool, Community College, and College. No issues with basic software functionality, really.

The worst and only issue I've had in that regard is self-inflicted because I decided to run LibreOffice via Wayland, which has an ongoing bug that makes scrolling laggy. That's it.

The larger issues with Linux as a desktop is software compat (Wine) with Windows for nicher use cases (requires debugging and a bunch of setup), certain drivers (cough cough Nvidia cough cough), and general dumbass-proofing.

Can we just let this shit die already? If you're unsatisfied with Wayland make extensions to the protocol or make a new one.

Why in the fuck are so many people obssessed over a piece of software that contains an entire networking stack and has a security model so bad that it lets literally every application keylog you constantly?

Go is a simpler-to-read language that does not involve lifetimes (as you know, it is GC'd). For a lot of smaller projects like this, the boringness of Go is preferred. Less mental bandwidth required.

I'll admit my definition of "industrial" here was vague, but I think you can get my point. I'm not trying to say that Rust isn't good in a business setting - my job also has Rust in the code!

However, for these purposes, most of the benefits of Rust in this situation are already provided by Go.

At this point we all need fake social media accounts

Ykw you've convinced me. I'm adding anime girls to my software rn. I wasn't a huge fan but after seeing your comment, I just really saw the light.

Think of the amount of morons I can throw into a rage over a cartoon girl....

chawan

Not the OP but I find it really curious you trust Apple's custom silicon over Google's in such a way that you seem rather confident with your locked down, Apple-controlled OS... unless you root it but then GL getting security updates, which kinda defeats the whole point.

There are a lot of risk vectors and frankly if we're getting to the immutable silicon level the exploits are probably going to be filed under direct targeting level privacy concerns. GrapheneOS is really mature and has security experts so good at their jobs they occasionally apply security patches before Google, with all its funding, does.

Apple and Google were both caught providing push notification data (e.g. the service underpinning most of the notifications appearing on your device) to the authorities. Not to mention Apple argued in a court case that it's "unreasonable" for an Apple user to presume their activities are private from Apple. I believe that particular court case was about them constructing ad profiles on their users.

It's genuinely absurd to me that you just vaguely threw out some kind of blanket concern with Google's underlying hardware. I'd really love to hear if that's based on anything material. From information I know is real and privacy concerns that have been explicitly justified, GrapheneOS is the best choice on the market atm.