beprogrammed

Some really great and interesting open source games being posted on here lately.

I can't believe I've never heard about a sixel up to now!

I read the whole article in the emacs screenshot before I realized it was right above in text...and i preferred it.

And today I learned Donald Knuth was the youngest Turing award winner at the age of 36. I'm going to have to go learn SPARQL.

Out of curiosity I took a look at his links, there actually pretty good. Strips out all the crud from articles and gives you some stats on how much smaller it made them.

https://trimread.org/

I don't know how you would shrink this article in particular, but for your standard news site, seems to work quite well.

As an example I fed the mosquito article from earlier into it and got this back. https://trimread.org/articles/437/info

Size went from 3.49 MB to 124 kB, the requests went from 210 to 6 and the load time went from 4.67 sec to 0.26 sec. Pretty good.

Same, literally laughed out loud.

Agreed, I'm especially fond of uMatrix lately for firefox.

Love it, that basically sums it up.

I especially love that my browser asked if I really wanted to leave the page, got me with my own setup.

I have to disagree. And to each is own.

Having read the article I found that list painted a clear picture and summed up the patterns nicely.

If one reads that and wants more, read the article.

(Not authors)Pattern 13: Using excessive prose where less will do

New to me, thanks.

https://amiunique.org

pattern 1: making outdated assumptions about the audience’s knowledge

pattern 2: having inconsistent expectations of the reader’s knowledge

pattern 3: strained analogies

pattern 4: pretty pictures on confusing explanations

pattern 5: unrealistic examples

pattern 6: jargon that doesn’t mean anything

pattern 7: missing key information

pattern 8: introducing too many concepts at a time

pattern 9: starting out abstract

pattern 10: unsupported statements

pattern 11: no examples

pattern 12: explaining the “wrong” way to do something without saying it’s wrong

He demonstrates it's operations on his YouTube channel.

https://www.youtube.com/watch?v=9hrnI8u3Uc4

A contender appears for FAF(Forged alliance forever), looks very good.

Dying buy your own creation is just the final tier of fun in inventing.

Stand back, I built this sh*t myself!

RIP buddy.

Agreed, that's why I never use or recommend any else use any of the domains run by private operators, just asking for troubles like the above. The attempted sale of org was scary.

Which is all very unfortunate because some of those TLDs are quite nice, like .forum. What a mess we've gotten ourselves into.

Should have been kept as a public service, but no putting the genie back in the bottle now. Only way out of this mess is a distributed system, but I can't imagine what that would like without a massive proliferation of competing services.

And if it's an effective method of selection, then those companies will thrive, if instead it's a poor method those companies will fill up with busy workers and sink under there own weight.

I look forward to seeing which it is.

Well, to be fair, censorship and fascism are worse things than extortionate domain name prices. Though both are bad.

Interesting piece of this is CadQuery, a python library for doing parametric cad like openSCAD.

https://github.com/CadQuery/cadquery

It's a terrible process for the users. And as we can see what did it get them, a third party logging into there webmail.

The service is protected with a username and password, didn't matter if it was IMAP or webmail.

It's fine to trust them right up until they give you a magic number.

- Scan containers and Pods for vulnerabilities or misconfigurations.

- Run containers and Pods with the least privileges possible.

- Use network separation to control the amount of damage a compromise can cause.

- Use firewalls to limit unneeded network connectivity and encryption to protect confidentiality.

- Use strong authentication and authorization to limit user and administrator access as well as to limit the attack surface.

- Use log auditing so that administrators can monitor activity and be alerted to potential malicious activity.

- Periodically review all Kubernetes settings and use vulnerability scans to help ensure risks are appropriately accounted for and security patches are applied.

The problem is, we get less of you and more of them, it damages us all. As long as you keep writing good software though, that's what really matters.

We used to stand in a field where everywhere we looked we could see and hear another of us, now there's 10,000 fools between each of us, and it's rare for us to hear or see another over the crowd.

Well he's a BSD guy, so he refers to the entire bunch as UNIX.

"One of Brooks's many excellent points is that quality happens only if somebody has the responsibility for it"

Linux is a prime example of this with Linus. I fear the day he's not around as a guiding force.

"Economic system based on private ownership of the means of production and the creation of goods or services for profit" no not capitalism, governance.

60 hour cap! Ha. I mean who wouldn't want to spend every waking hour at the sweltering chip factory for basic rate.

AI: Artificial Ignorance

Harsher punishments. Nothing is stopping kids from going around and stabbing randoms but the fear of getting caught (and for some the distaste of hurting others). Kids believe they can swat someone and get away with it. Don't only go after the cases that result in deaths, crackdown on all such cases.

He was born, succeeded in living a meaningless life, and died.

"Every time I look at LV2, I am repulsed. LADSPA is KISS, one header file dependency and relatively straight-forward. LV2 is like the opposite of KISS. It's like FART: Forget About Representing Terseness. It reminds me of something from IBM. The dependency is like 6 different little libraries that no one will ever use for anything else. And all that this complexity really buys you is shitty in-process GUIs that crash your host program."

Lol. That's what made his software so great, he kept it non. But I can see the problem when others start wanting to add features via bloat. Two contrasting desires, does he stick with the thing that made his software great, or add any feature someone wants?

That's a dirty move.