Amikke @Amikke@qoto.org

@Moon @shibao @union yeah, but you can at least establish sieves that catch at least a portion of them before they're too far gone. Deb00nkers are doing god's work in that context, even if they're a little trigger-happy at times.

@Moon @shibao @union honestly, that is better than people unfamiliar with the meme believing in it and building a siege mentality around it until it's an entire conspiracy theory with a dedicated community.

@newt one of my favourite 4chan moments was when it turned out that the vast majority of shitposts (per old meaning, posts that literally only waste time and thread count) come from Australians, and the flood of memes that followed.

#meme

why does this shit still make me laugh

#meme

Funny how we went from worrying that the world is gonna run out of oil to wishing it ran out already.

Searching for capitalist conspiracies in things that organically ended up how they are is the exact same thing as searching for jewish tricks in the same circumstances, only approached from a different angle.

It's ridiculous how indistinguishable far-left is from far-right if you equate "teh jooz" with "teh capitalist overlords", and the way the two often overlap makes it even funnier.

#politics

@newt @Paradox and the worst part is that the two most sensible arguments for using spaces over tabs have silly simple solutions:

1. "But tabs can be rendered with different widths 😭" yeah, that's an upside not a downside. If you don't like how wide or thin tab-indentation looks in your editor, just tell it to render it with different width, problem solved. You can't do that for code where some dumbfuck used 2 spaces for indent and you'd like to see the indent levels more clearly. This also applies to the people using text-based environments with the Unix default rendering of 8-width tabs - yes, vim, emacs or whatever 80s software you prefer is smart enough to be able to do `s/\t/    /`* before writing to the tty or has a plugin available for this exact purpose.

2. "B-but tabs can be rendered differently by different browsers so a tab-indented code pasted into a random text element can display weirdly for people viewing it on IE6" - rendering code to a universal text representation is as much of a thing as rendering it on a screen, and again in this case amounts to running `s/\t/    /`* on it. Code hosting websites already do this. Oh, and did you know that the official standard way to render multiple spaces outside of `<pre>` elements is to concat them into a single one, making them even worse in that regard? And that CSS has a `tab-width` property? Wild stuff.

*yes, these are non-breaking spaces, or at least that's what I typed before clicking "post"