No. What is actually happening in the comic is that a character is having a discussion with another person (not a racist conversation, because sea lions are not sentient beings despite what is about to happen). Treating it as anything more than that is reading something into the story not intended by the original comic. Not everything is so literal, particularly with Malki comics.

Not gonna cry over what the victims of racism do to racists.

Eh…I dunno. I’m not going to tone police anyone, and consequences for bad actions are definitely good, but do two very-wrongs make a kinda-right? I’m not sold.

[the rest]

Look…if you don’t vibe with the comic, that’s fine. It’s just obviously not about all the stuff that you seem to think it’s about.

Yes, I think you’re correct, but using browsers to coerce the web back into static documents will result in companies creating their own apps so that they can continue to deliver experiences. And the past 10+ years has shown that users will absolutely follow them.

Dang, that comic will be ten years old next week.

Racism justifies harassment and home invasion? I don’t think I can necessarily agree with that. Consequences, yes. But harassment? I’ll have to think about it.

The point Malki was making, I think (and the way I take it) is less about the purpose or content of the discourse and more about the harassment veiled in false civility as a means of silencing discussion.

There’s also an element of Person C inserting themselves into a private conversation between Person A and Person B, even if that conversation is being held in a public place.

Pretend he’s not a sea lion, but a conservative, and you’ll get the intended effect.

It’s not a whatabout, but since you have your mind made up, by all means don’t let me get in your way with facts.

Yeah, I get it, but like…the same could be said for emails in a world where phishing exists.

With stuff like Tesla and Twitter, it can keep away the weird nerds who search those terms in hopes of white-knight-sealioning a conversation into oblivion. I think it just became part of the lexicon.

I’ve been working in full stack for long enough to know that history manipulation is as much a part of the modern web as images and email. I’m not trying to be flippant, that’s just the state of the modern web. Single-page apps are here, and that’s a good thing. They’re being used badly, and that’s endemic to all features. So no, history manipulation is not “bad functionality,” though I admit it’s not fully baked in its current implementation.

Yeah, I get it. But I fear that ship has sailed long ago.

I’d prefer not to let the bad actors dictate browser design.

“Let’s get rid of images since companies can use images to spoof browserchrome elements.”

“Let’s get rid of text since scammers can pretend to be sending messages from the computer’s operating system.”

“Let’s get rid of email since phishing exists.”

Nah. We can do some stuff (like the aforementioned forked history) to ameliorate the problem, and if it’s well-known enough, companies won’t find it necessary anymore. Heck, browsers like Firefox would probably even let you select Canonical Back as the default Back Button behavior, and then you can have the web the way you want it (like people who disable Javascript).

That would absolutely make everything worse, no question; the web should be more integrated, not less. We shouldn’t incentivize even more companies to silo off their content into apps.

Looks to me like that’s what this screenshot is of.

I don’t know about “easily.” replaceState() is actually intended to make single-page apps easier to use, by allowing you to use your back button as expected even when you’re staying on the same URL the entire time.

Likewise, single-page apps are intended to be faster and more efficient than downloading a new static page that’s 99.9% identical to the old one every time you change something.

Fixing this bad experience would eliminate the legitimate uses of replaceState().

Now, what they could do is track your browser history “canonically” and fork it off whenever Javascript alters its state, and then allow you to use a keyboard shortcut (Alt + Back, perhaps?) to go to the “canonical” previous item in history instead of to the “forked” previous item.

Also to get the white right people to intimidate the brown wrong people into staying home, under the guise of “poll watchers.”

Pretty sure it’s black on transparent. Not the most visible, especially if your client makes the background black.

I’m not moving any goalposts at all. I’m expressing how inexperience and bad assumptions can make one’s searching unfruitful through no fault of their own. That’s all I’ve ever been saying.

Ah, you made an edit. Yeah, “kde login rotation” does, but “EndeavourOS login rotation” gives you no results mentioning SDDM. Giving people the benefit of the doubt costs you nothing over assuming that they’re lazy, and the added bonus is that you don’t sound like a jerk.

That’s totally the biggest problem with the internet. And definitely deploying self-important moderaptors is the way to fix it.

/s, of course. Get off your high horse.

Yes. I would assume that the problem is in X11 or Wayland before thinking it could be SDDM, frankly. But even then, googling “Linux login screen” doesn’t immediately reveal SDDM to be the point of concern.