How to explain modern American politics in one chart
Uncategorized
8
Posts
7
Posters
1
Views
-
How to explain modern American politics in one chart
-
How to explain modern American politics in one chart
@jalefkowit
Yah. Noxious law -
How to explain modern American politics in one chart
@jalefkowit I suspect this charts says more about the number of billionaires than about how much rich folk are donating.
-
@jalefkowit I suspect this charts says more about the number of billionaires than about how much rich folk are donating.
@KeithWM The percentage is of the total volume of dollars contributed, not the number of contributors.
https://americansfortaxfairness.org/billionaires-buying-elections-theyve-come-to-collect/
-
How to explain modern American politics in one chart
The worst law of all the worst laws. And we knew what would happen. And it did.
-
How to explain modern American politics in one chart
@jalefkowit Ah, see. The world really did end in 2012.
-
How to explain modern American politics in one chart
-
How to explain modern American politics in one chart
@jalefkowit The Epstein ruling class wanted this.
-
undefined swelljoe@mas.to shared this topic
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@TOrynski @getajobmike not learning new things is different from forgetting them tho, and LLM usage can vary a lot in the range from looking at a map to sleeping while the robot drives.
I am convinced coding skills can atrophize but I'm not sure it's a fast process. I haven't driven a bike in a year, but I still know how.
-
@cwebber it's really good
-
@paco@infosec.exchange why Discourse?
Use NodeBB. We keep our shit in one folder.
You can put that folder anywhere 🫠
-
@paco this is also important to me. 👊
-
But no. The discourse "easy installer" sprays shit all over /var. I'm gonna get some database down in /var/lib/docker/something and I'm going to get assets living in /var/discourse, and umpteen gajillion container images in /var/lib/docker.
But I also have fucking /var/log for OS logs, and /var/run for runtime information like PIDs, and /var/lock and /var/tmp. I think /var/most-important-app-on-the-system is NOT where you put application software. So my volume/filesystem to encapsulate discourse? Is that a big ass /var?
I love #FreeBSD because it is so well organized. They even go to trouble to make packages like postfix or apache fit the idiom, rather than let it install in /var/lib/opt/sbin/etc or some shit.
This public service announcement sponsored by Old Man Yells at Cloud, Inc.
-
More moaning about #linux. I'm trying to get a discourse server off the ground. Why the fuck do they insist on installing non-OS stuff in the middle of all the OS stuff.
/var/discourse is not a good default. And then fucking docker wants to be /var/lib/docker. Never mind how /var/lib doesn't make any goddamn sense.
Related to my earlier discussion of hard drive partitioning. What I would like to do is have a volume that is not the operating system, but is instead all the application data. The discourse data, database, assets people upload, etc. That way I can have this nice virtual disk that encapsulates it. I could theoretically build a new node, attach this drive to the new node, and migrate the site. I can snapshot that drive more frequently than, say, the OS drive. Lots of benefits to encapsulating it.
-
@getajobmike It's interesting to see it grep in parallel for a dozen likely things in a codebase, like when an error string is constructed from variables and static strings or passed through a couple layers, and you have no stacktrace. But it will also get inverted about what's a diff vs code and point out some non-issue that wastes your time. If you work in a language with a lot of boilerplate like java, I can see it being too handy of a shovel.
-
Operazioni aritmetiche e scorciatoie
@matematica - Pare che i maschi siano più portati a usarle rispetto alle femmine.
