fao_
Joined 11 years ago
Joined 11 years ago
Just to expand on this for the audience. Even a perfectly reasonable synthesis of MPPP, a synthetic opioid, can produce MPTP[1], which will destroy all of your dopaminergic neurons and give you permanent brain damage. This was discovered entirely by accident. Or, Karen Wetterhahn, who got a single drop of organic mercury on her gloved hand and spent the next year suffering from her brain rotting from the inside out.
This only barely scratches the surface from what I can remember, but there's absolutely, unambiguously a lot of good reasons why these barriers are there. These are rules that have been put down through blood and tears.
I'd honestly just prefer it if you'd written a 2 paragraph history yourself. It comes off as very insincere otherwise.
As a whole, the archive and webpage are very difficult to navigate, too. I've seen a lot of these sorts of live-archival projects over the years, and as best as I can tell, a lot of the context clues that normal archivist projects (or even, you know, humans that design web pages) give you to help prompt you for what to expect are missing. It's also very distracting how the entire thing is written and formatted like a VC sales pitch.
edit: I just attempted another go at the "museum edition" version to see if I had missed something, but pressing "skip" to get past the intro caused the entire thing to seemingly halt completely. Any further input prompted the "if you make a mistake, press pound" sample to play, and then it prompted me for a password. I tried yet again, and it happened again even after a cache-clearing refresh. I tried again, and just waited it out, but pressing the star key caused it to enter the "connection closed" state.
This... As someone who has broadly avoided LLM software, this entire site is one of the buggiest things I've ever used. It needs a third pass just to make it bug-free and intelligible to someone who isn't involved in the project, I think. And maybe throw $20 at a programmer you know to hand code stuff instead.
It deeply, deeply sucks to have to give such a harsh review to the archival effort of what is one of the most unique and interesting BBSes I've ever heard about.
> The ancien règime in France is reported to have guaranteed fifty-two Sundays, ninety rest days, and thirty-eight holidays. In Spain, travelers noted that holidays totaled five months per year.
One of the reasons why children, teens, and young adults have become so infantalised is because they are socialised mostly around each other, and spend a lot of time being told "no you can't, you are a child". This is not a call for children to enter the mines, and I do not wish to see child labour laws repealed (as they are apparently being in some parts of the USA). But for children to be socialised correctly, they must maintain connections with people of all ages, both older and younger — all benefit from such an arrangement. For them to grow up, they must be treated as people, and given age-appropriate responsibility and inclusion in the tasks that adults do. It is harder to teach a teenager to wash the dishes and their clothes, than it is to ask for a child's help washing the dishes and your/their clothes. The children are happy to help and to be included, you get to teach them rudimentary tasks, and it counts as family bonding time. The alienation of children from adults, and the alienation of children from their parents' work, is a great loss to society as a whole.
[1]: https://groups.csail.mit.edu/mac/users/rauch/worktime/hours_...
It is not enough to simply say you have done something interesting (which is all that this blog post amounts to), we as humans want to know the story of it, it's that that makes it interesting. You can't get that story if you're just vibecoding it, much like how the one person involved in Wolfram Alpha spent a lot of tokens on an LLM that constructed alternative forms of logic, and came away from it thinking that it was worthless, the entire time wasted, because there was absolutely no way for a human to interact with it, those logics had no story or analogies or anything for a human to latch on to.
- Multithreading (using all hyper-threads / CPU cores)
- Video mode up to Full HD (1920x1080 / 16 bpp)
- 64-iterative ray-casting
- Pure DOS with Protected Mode (no drivers, no DPMI)
https://www.pouet.net/prod.php?which=96532It is a seriously technically impressive demo, if not being the most visually impressive.
> not sure if this is just me, but after updating rsync, my cpu usage got so bad during my daily backups that i had to stop timeshift from running forever
Or, phrased differently - People are frustrated and annoyed that the tool they trusted with their backups and data are seeing a huge number of regressions and new bugs that break their entire backup infrastructure, all because the main dev is vibecoding that software. Vibecoding experts like Simon Wilson explicitly state that vibecoding is 'viable' in the sense of "only if you hold the tool in a specific way", and this person is either not doing that, or that statement is untruthful. If you actually read the thread in question and just skim over the argument two people are having, there are multiple reports from users in industrial and government settings that now have to go through whole processes to update this software, simply because the software has become immediately untrustworthy in a way that directly harms users and defeats the entire point of the software in question.
I think I would also be mad if I relied on this software for my 500gb+ backups, and I wonder how many more issues have been introduced that we simply won't learn about until a company has a $10 million dollar data loss because they were not testing their backups consistently.
https://www.youtube.com/watch?v=Rh50Cht9tUc
https://www.reddit.com/r/glutenfree/comments/81pvql/the_best...
There's also this guy's recipe which is apparently pretty good: https://www.youtube.com/watch?v=DZH-GUFBrz0
Personally I do a 'lazy pizza' which is just a really basic primitive bread (like how people would have made bread before yeast):
The original recipe was:
- 8oz doves farm self raising flour (or any celiac self raising flour. but doves is the og and the best IMHO)
- 1 large or medium egg
- 1 tsp baking powder
- cold water to mix (alternatively: a cup and a bit of water with 1tsp chia seeds in it, you want them in the water for about 10 - 20 minutes with regular (regular!) stirring. stirring every time they kinda coalesce at the bottom. it should look like frogs spawn by the time you're through.)
Oil pan well, put soft dough in (you want it like. soft enough that it starts to spread just a little. but not so wet that it's spreading a lot. you do NOT want it as dry as a normal non-celiac bread because there is no gluten to hold on to the water). flatten with oily silicon brush, then top. cook at 180°C for 20 minutes or so. You might want to cook it a little before topping if your toppings are cooked already. And honestly, I just eyeball the cooking time based on how it behaves.
The chia seeds help make it a little chewy, which apparently is part of how pizza dough usually reacts, as well as pulling and stabilising any moisture so it doesn't get soggy.
All of these systems are designed around the core idea of "a human acting irrationally or improperly is not at fault" and, furthermore, that a human can have a bad day and still avoid a mistake. They all steer someone around a possible fault. Hell, the reason why we divide the road into lanes is itself a forcing function to avoid traffic collisions!
So, where is the forcing function in large language models? What part of a large language model prevents gross misuse by laymen?
I can think of examples here and there, maybe. OpenAI had to add guard rails to stop people from poisoning themselves with botulism and boron, etc. But the problem here is that the LLM is probabilistic, so there's really no guarantee that those guard rails will hold. I seem to remember there being a paper from a few months back, posted here, that show AI guardrails cannot be proven to work consistently. In that context, LLMs cannot be considered "safe" or "reliable" enough for use. Eddie Burback has a very, very good video showing an absolute worst case result of this[1], that was posted here last year. Even then, off the top of my head Angela Collier has a really, really good video demonstrating that there's an absolute plethora of people who have succumbed, in large ways or small, to the bullshit AI can spew[2].
I feel like if most developers were actually serious about being an engineering discipline, like we claim, then we wouldn't have all jumped on the LLM bandwagon until they'd been properly tested and had a certain level of reliability. Instead there are a sizable chunk of people saying they've stopped coding by hand entirely, and aren't even reviewing the code! i.e. They've thrown out a forcing function that existed to prevent errorenous PRs being committed! And for some bizzare reason, after about 2 decades of people talking about type safety and how we need formal verification to reduce error, everyone seems to be throwing "reduction of error" out the window!
[0]: https://en.wikipedia.org/wiki/Behavior-shaping_constraint (if you're curious about the term)
The art of essay-writing seems to not be something people here care about any more. If a human didn't bother to write it, why should I bother to read it?! Just post up the bullet points you would feed the LLM, and let the people who want to do so, post it into their own LLMs so they can make the Content and shovel it into their eyeballs by themselves, instead.
This is but one model developed within academia for an entirely anarchist organisation, there are dozens of others and they have been both studied for efficacy (they tend to work better than a more hierarchical structure), as well as put into practice in real life within certain organisations. To this date there are a number of non-profit organisations and coöperatives that use this governance system to improve the situation where they are locally and achieve their goals — whether that's "everyone working to improve the local community" or "make good products for a client".
The entire point of anarchism is that there isn't One Big Guy, it's that it's people, deciding on a system and working together on a small scale — this then translates to the big scale through cross-group meetings, information sharing, and resource sharing. There is a lot of evidence within the social sciences to back these methodologies up as being very efficacious compared to traditional methods of group organisation, as well as being more democratic than traditional alternatives.
This additionally tends to be how some kinds of open mic nights work, as well as some kinds of modern speakeasys.