Plant proteins are all allergens. Very few plants have MCTs or saturated fats. Sugars release tons of oxidative radicals.

Meat is orders of magnitude more concentrated in critical essential nutrients. Vitamin B12 another rarity in plants.

These people think our hybrid teeth, with a mix of meat and plant eating characteristics prove we are lol vegetarian animals.

No, we just can eat plants, so we can run away from places that are too dangerous.

VMs are more secure. But LXC is pretty secure in respect of isolation. If money is involved, go with the VM.

It's called "weak synchrony".

The Time Warp Attack, which was hypothetical, was implemented effectively against the Verge cryptocurrency, which succeeded in pausing the chain and allowing the attacker to issue as many blocks as they wanted to until the node runners shut them down.

The vulnerability that enabled this was an attempt to tighten the synchrony of the network, by, specifically, nodes adjusting their time offset to a tight margin of the average of the swarm.

All that was required was for one node to continuously poke at the network's measure of time until all nodes agreed there was no progress of time, and the attack basically then shut down the network.

The lesson of this story is that you can't make a consensus out of the time, without breaking the difficulty adjustment.

One of the strategies that the fascist pigs in the political lobbies have historically used for a long time is excessively verbose and complex laws that create a tangle of "red tape" that obstruct entry into a field of business.

Right now as we watch the AI business on yet another of its many resurgences with the LLM field producing intelligible text and images, we now have a situation developing that is going to be very amusing to watch.

Big Tech versus 19th Century Law and Medicine Trade Associations.

It's one very entrenched rentseeker group, against another, less recently established rentseeker group.

If AI can make differential diagnosis as effectively as an expert human, or find loopholes in tens of thousands of pages of current law books, it is going to come at a much lower cost than hiring the monopoly-protected law and medicine fields, there is going to be a lot of propaganda war going on between these two groups.

The doctors and lawyers will be screeching about the dangers of wrong assessments of data and due process and safety and all this, and meanwhile, the tech companies are gonna obviously be attacking this monopoly power in some way, it's going to get very entertaining.

I already shun doctors and lawyers because they overcharge. I see them as greedy pigs, every last one of them, even the more decent ones are still living higher on the hog than they deserve to be.

I mean, this lobby power isn't as bad everywhere, like, both medical and legal cartels are the worst in english speaking countries and varying degrees of lesser in other places. Like Bulgaria, for example, has a big supply of doctors of various kinds, but they tend to end up leaving the country because they don't get that privileged boost to their income.

AI for medicine and Law is gonna be super cool. I can't wait to see the hackers and anons building LLMs to attack these rentiers. Can't come soon enough for me.

https://www.theregister.com/2023/08/08/google_senator_ai_health

Just thought I should drop this link here as this is relevant to the subject.

If there ever was an exemplary case of software that MUST be open source, it's AIs used in this kind of business, and Law would be another subject area relevant to this.

It's a funny thing, to see Google doing something that is going to put them at odds with the AMA and I'm betting this same thing is being done in Law businesses too, either by Google and/or others.

Which rentier will win? AMA or Google?

Note that this story relates to Joseph, who is generally lionized by christians, but when you analyse the story, he applies every trick in the central banker playbook, and the result was the 7 plagues.

Ok, that may have been partly coincidence, but quite a bit of it was simply that it exposed the egyptians to conditions along similar lines as what was seen in Russia when communism was first inflicted on people. Before a jubilee period would have passed, the nation was starving.

This led to Lenin easing up on the program to industrialise agriculture, and is significant in the history of eastern europe that it enabled traditional, small farm holdings to continue to function with little oversight, and is an interesting common feature everywhere socialism took over in the period 20s-40s (including Italy and to some extent spain).

Also, somewhat related, but pre-monarchy Judaism, as described in 1 Samuel 8 as being against God, also, according to archeological records, probably refers largely to the city of Jericho, which stood for 9000 years and its destruction was presaged by the introduction of this monarchy.

It's an interesting subject and one I'd love to see an indepth, cross-referenced, as an object lesson in political economy, jurisprudence and how this relates to the modern liberal democratic state, which is by all biblical definitions satanic government.

Almost as importantly, and a lot less complicated and expensive, should be the development of community militias, and the abolition of military, replacing it with a council of generals and other administrative types to coordinate broad, multi-region action/responses.

Would be very cool to see that, I don't know how many places still have this kind of militia, I think Switzerland is still a little this way. If there was an option open for a global south country having this kind of setup it would be my first choice for where to relocate.

It's a very difficult bootstrap to achieve, but sooner or later it has to happen.

History shows over and over, nations that do this, survive, and don't get conquered, if they have resources worth fighting over.

This reminds me that my mother has a bible I was given, and a photograph, when I got baptised at age 14. Seems like an object I should be carrying with me, now I think about it.

Do you remember the photos of molten aluminium alloy car wheels melted down while plastics nearby were completely intact, and the way that certain kinds of things appeared to have basically exploded, during california "wildfires".

I know that part of the california thing had to do with the sheer amount of australian Eucalypt trees that had been planted, and these trees are adapted to and depend on a periodic fire regime to reproduce properly, and the vapors off the leaves can form a fully combustible gas mix that can explode like gasoline. While this is part of it, it just doesn't explain the molten metal with nearby plastics unaffected. That can only be caused my microwaves, which pass through plastics but agitate metals.

I hope this is also done for lawyers and all of the other professions that have a cosy relationship with the government to exclude people from getting certification not because of lack of skill but in order to keep the price of their labor high.

I want all those smarmy pricks to discover that they can be dispensed with. Can't come soon enough.

I for one want to see as many as possible pwned and set to fling themselves into the sun.

https://www.theregister.com/2023/08/11/satellite_hacking_black_hat

Got the time time tickin in my head TICKIN IN MY HEAD!!!!

https://youtu.be/GZknKOM0RTo?list=PL55dlik195K2ty8Y5Wqh6LSgc0nQ2YD1W

It also ties in with the work I am doing this very minute.

I have a segmented, multi-layer message protocol that is processed in various ways, and the basic principle is sentinal magic bytes marking sections, that are consumed from the top and padded out to appear the same length when they are forwarded.

Currently it is using defined, static, structs, and chained methods to encode reading or writing.

Previously I had written encoders that work on the principle of slice of interfaces, in this case, slice of codec.Codec, which is a defined interface type for some unit of data and how to read and write it from disk/wire format to in-memory variables that are addressable.

The dilemma is one I am still not satisfied at all with the construction, I kinda feel like maybe I need to try a third way, that uses method pointers , that an interface type of variable follows it. This way the coding is self-describing.

I just am not sure which way to go with it. My intuition is that the Go implementation of UTF-8 variable length encoding is a model that will make it easier, I want it to be as simple as ReaderWriter types... aargh... well, anyhow, gonna start with reading some of the current Go codebase anyhow. There is several good prototypes for similar stream/object processing code in there.

I only just learned today what "shenandoah" means, and I'm going to grow that again. Never liked moustaches anyway, especially my nasty one, so it will work out well. The random part of that is I bumped into the usage of "Shenandoah" to mean the style of beard, via reading about Garbage Collection: https://en.wikipedia.org/wiki/Garbage_collection_(computer_science)#Java

haha! Shenandoah!

Indeed, this would be a cool thing. And while we are at it, we need grouping for serials, chapters, etc, hell, the entire Gutenberg Project should be available via Project Gutenberg nostr relay which holds all the post hashes for indexes, lists, and the actual book text (in markdown, of course). Just make a nostr enabled ebook reader and we have something to rival Wattpad.

Random thought after reading program language garbage collection:

FUSE filesystem, on memory mapped file, allocation is creating a file, freeing is deleting. Memory mapped means the data is opportunistically persisted and enables fast recovery of state to a prior condition.

The logical choice for it is a filesystem that is designed for low latency, memory-like storage, `f2fs` or other similar. Ext-3 and ext-4 are also pretty good choices.

It leads me to the thought, which I have had before, which is essentially eliminating the notion of "working memory" in favour of a fast, SSD based memory cache system, so allocating memory ALWAYS means making one of these new files, freeing always means deleting, and accessing the memory is reading, changing it is writing, there is a notion of a cursor for seeking, and hell, somewhere in the mix, we would have TRIM as well.

I just checked my followers list on snort.social lol, omg I didn't realise I had so many already. sweet.

Despite being a feature on JPEG for maybe at least a decade now, not all JPEG decoders render the image according to the rotation tag.

Most likely whatever your favourite customary way to hold your camera is, is infact recording the images 180' from what you expect.

So, yet another secret leaking vulnerability found in a CPU (of the type I usually buy):

https://www.theregister.com/2023/07/24/amd_zenbleed_bug

The bug essentially is a flag that "marks" a register in an indeterminate state as "zero" - ie, just write over it. But if you read, it can have anything there, even such things as the passwords and encryption secrets of, for example, your SSL connection to a website.

In the idiom of the Go language, it is almost the greatest, most verboten sin of all, to allocate memory and not zero it. Every allocation in Go starts with zeroing before the program could possibly be reading it.

It would not be possible to directly exploit this vulnerability with a standard Go program. It would require bypassing it using `unsafe` or assembler code.

For other languages, memory allocation often will be allowing whatever state the memory is in when freed to be readable by a program. This is also why Go idiom recommends making use of the zero, because, it's going to run anyway, the runtime enforces it.

It does rather seem to me though, that a proactive variant would have programs deliberately zero their memory. Like, to just assume the worst in all cases, zero memory out, zero memory in.

Du Hassst Michhhhhh!