I want to be much more publicly unhinged and in general do a lot more art without worrying too much about why or what I'm trying to say. I've found a lot of beauty in shitposts this year and I want to develop my skills to really meaningfully contribute to the corpus.
I think this kind of critique often leans too hard on “security through obscurity” as a cheap punchline, without acknowledging that real systems are layered, pragmatic, and operated by humans with varying skill levels. An open firmware repository, by itself, is not a failure. In many cases it is the opposite: transparency that allows scrutiny, reproducibility, and faster remediation. The real risk is not that attackers can see firmware, but that defenders assume secrecy is doing work that proper controls should be doing anyway.
What worries me more is security through herd mentality, where everyone copies the same patterns, tooling, and assumptions. When one breaks, they all break. Some obscurity, used deliberately, can raise the bar against casual incompetence and lazy attacks, which, frankly, account for far more incidents than sophisticated adversaries. We should absolutely design systems that are easy to operate safely, but there is a difference between “simple to use” and “safe to run critical infrastructure.” Not every button should be green, and not every role should be interchangeable. If an approach only works when no one understands it, that is bad security. But if it fails because operators cannot grasp basic layered defenses, that is a staffing and governance problem, not a philosophy one.
Earlier this year I downloaded TikTok once, I needed to access some very niche videos and couldn't watch them without getting an account. I never added anybody, and I never associated with any other socials, but somehow I started getting emails from TikTok that one of my NEIGHBORS were viewing my profile! Even used their full name. I deleted the account and uninstalled the app.
Yeah, synesthesia combined with being attuned to body language and emotions could account for lot. I even remember there was some anecdote of a famous physicist (Feynman?) who investigated this soviet mind reader and found that he was picking up on subtle bodily clues.
I think it ultimately comes down to whether you care more about the what, or more about the how. A lot of coders love the craft: making code that is elegant, terse, extensible, maintainable, efficient and/or provably correct, and so on. These are the kind of people who write programming languages, database engines, web frameworks, operating systems, or small but nifty utilities. They don't want to simply solve a problem, they want to solve a problem in the "best" possible way (sometimes at the expense of the problem itself).
It's typically been productive to care about the how, because it leads to better maintainability and a better ability to adapt or pivot to new problems. I suppose that's getting less true by the minute, though.
In the 2000s, my bank was acquired by some bigger bank from another country. Their long standing, well working and fast banking application was replaced with a very dysfunctional Java applet thing. I was using Linux at the time and IIRC it either worked barely, or then not at all. I phoned the bank, and they told about a secret alternate 'mobile' url, that had a proper working service. I used that for a while before ultimately switching to another bank. The bank sent apology letters to customers and waived some fees also as they saw many of them leave. It made me really wake up that to the fact if the company can do these visible level blunders, what else is going on there, and also, how the customer is in such a vulnerable position.
On the other hand, NASA in the past had some really great Java applets to play with some technical concept and get updated diagrams, animations and graphs etc.
And most people problems are communication problems. Engineers aren't engaged with the product vision or the customer base, and are allowed to silo themselves. Product doesn't see the point of engineers being engaged and feed the engineering team like an in-house outsourcing shop. Sales and CS fail to understand the cost of their promises to individual customers to the timelines of features they're hungry for from the product plan. Goals and metrics for success fail to align. And thus everyone rows in their own direction.
The solution usually isn't "better people." It's engaging people on the same goals and making sure each of them knows how their part fits with the others. It's also recognizing when hard stuff is worth doing. Yeah you've got a module with 15 years of tech debt that you didn't create, and no-one on the team is confident in touching anymore. Unlike acne, it won't get better if you don't pick at it. Build out what that tech debt is costing the company and the risk it creates. Balance that against other goals, and find a plan that pays it down at the right time and the right speed.
>I really, truly don't understand. This isn't just about manners, mores, or self-reflection. The inability or unwillingness to think about your behavior or its likely reception are stupefying.
Shower thought: what does a typical conversation with an LLM look like? You ask it a question, or you give a command. The model spends some time writing a large wall of text, or performing some large amount of work, probably asks some follow up questions. Most of the output is repetitive slop so the user scans for the direct answer to the question, or checks if the tests work, promptly ignores the follow-ups and proceeds to the next task.
Then the user goes to an online forum and carries on behaving the same way: all posts are instrumental, all of the replies are just directing, shepherding, shaping and cajoling the other users to his desired end (giving him recognition and a job).
I'm probably reading too much into this one dude but perhaps daily interaction with LLMs also changes how one interacts with other text based entities in their lives.
Having consulted on government projects - especially huge projects spanning dozens of government departments, what I have learnt is that the project is doomed right from the start. The specifications are written in such a way that it is impossible to get a working software which can address all of the millions (yes, literally) of specifications.
For instance, I had the opportunity to review an RFP put out by a state government for software to run a single state government. The specifications stated that a SINGLE software should be used for running the full administration of all of the departments of the government - including completely disparate things such as HR, CCTV management, AI enabled monitoring of rodents and other animals near/at warehouses, all healthcare facilities, recruitment, emergency response services etc...
ONE SOFTWARE for ALL of these!
There isn't a single company in the world who can write software to monitor rodents, hospital appointment booking, general payroll, etc. And since the integration required was so deep, it would be impossible to use existing best-of-breed software.. and everything has to be written from scratch.
How is such a software project ever going to suceeed?
A number of years ago I worked on a POWER9 GPU cluster. This was quite painful - Python had started moving to use wheels and so most projects had started to build these automatically in CI pipelines but pretty much none of these even supported ARM let alone POWER9 architecture. So you were on your own for pretty much anything that wasn’t Numpy. The reason for this of course is just that there was little demand and as a result even fewer people willing to support it.
The comment at the bottom of the article I believe is correct. I believe this because our neighborhood had the same problem. One day my neighbor, frustrated beyond his capacity, and seemingly very high on something, went outside and started ripping infrastructure out by hand and damaging everything else he could find with a hammer.
They came out and replaced a lot of the damaged equipment and did a few upgrades. After that the intermittent 2 minute drop problems disappeared.
Like other commenters point out, automatic OCR on Apple platforms is a godsend, and it's such a great use of our modern AI capabilities that it should be a standard feature in every document viewer on every platform.
Another thing I wish was more common is metadata in screenshots, especially on phones. Eg if I take a screenshot of a picture in Instagram, I wish a URL of the picture was embedded (eg instagram.com/p/ABCD1234/). If I take a screenshot in the browser, include the URL that's being viewed (+ path to the DOM element in the viewport). If I take a screenshot in a maps app, include the bounding coordinates. If I take a screenshot in a PDF viewer, include a SHA1 hash of the document being viewed + offset in the document so that if I send the screenshot to someone else with the same document, it can seamlessly link to it. Etc etc.
There are probably privacy concerns to solve here, but no idea is new in computer science and I'm pretty sure some grad student somewhere has already explored the topic in depth (it just never made it to mainstream computing platforms).
It feels like screenshots have become the de facto common denominator in our mobile computing era, since platforms have abstracted files away from us. Lots of people who have only ever used phones as their main computing devices are confused when it comes to files, but everyone seems to understand screenshots.
I feel like there are competent, competing visions talking past each other on the subject. There's kind of a spectrum:
1. Everything is a monolith. Frontend, backend, dataplane, processing, whatever: it's all one giant, tightly coupled vertically-scaled ball of mud. (This is insane.)
2. Everything is a monolith, but parts are horizontally scaled. Imagine a big Flask app where there are M frontend servers, and N backend async task queue processors, all running the same codebase but with different configurations for each kind of deployment. (This is perfectly reasonable.)
3. There are a small number of separate services. That frontend Flask server talks to a Go or Rust or Node or whatever backend, each appropriate to the task at hand. (This is perfectly reasonable.)
4. Everything is a separate service. There are N engineers and N+50% servers written in N languages, and a web page load hits 8 different internal servers that do 12 different things. The site currently handles 23 requests per day, but it's meant to vertically scale to Google size once it becomes popular. Also, everything is behind a single load balancer, but the principle engineer (who interned at Netflix) handwaves it away a "basically infinitely scalable". (This is insane.)
These conversations seem to devolve into fans of 1 and 4 arguing that the other is wrong. People in 2 and 3 make eye contact with each other, shrug, and get back to making money.
The keywords seems to bring an anomalous amount of trolls in the comments. But maybe I am in the wrong, and there's a positive side into leaking plastic pellets in the ocean. Like turtles can now build their own platic industry and we'll make business with them soon or something.
PSA that melatonin use was way out of control before this study was even published.
Sleep aid melatonin is shipped in pills containing ridiculous amounts of the stuff—I’ve seen 10, 12, and 20mg myself, Amazon has a 40mg fast dissolve and 60mg gummies.
This spikes your blood amount with 100x-1000x of your natural cycle of melatonin. Why? Because melatonin is not, repeat not, the signaling molecule that makes you sleepy. It responds to light levels and triggers the cascade of other molecules that make you sleepy, several hours after it peaks. So that's why the 100x overdose—you are trying to kick those secondary mechanisms into overdrive, “hey everyone it is black as the abyss of hell I guess we gotta sleep!!”, because Americans taking melatonin want to pop one just before bed and have it knock them out.
And it does that for like 2 or 3 days before your body starts down-regulating all of its sensitivities to those melatonin byproducts. Nerve cells like to be tickled, not zapped, when you shock them like this they react angrily.
You want to use melatonin to reinforce circadian rhythm and fight jet lag, you do it with amounts in the ~100 micrograms range, slow release if you can find it, and you take that at sunset and let it reinforce your normal cycle. If you're looking for an acute sleep aid, take a walk, get fresh air, drink water, and if those don't help pop a Benadryl/Unisom (it's the same drug either way). If you have doctor’s orders of course follow those, but if you're just trying to self-medicate that’s how you do it.
Absolutely unsurprising that punching your sleep apparatus in the gut once every day for five years increases some sort of stress on your heart.
As I heard someone say, happiness is your reality minus your expectations.
Smart people see more variables that could be changed, more components that could be modified, and are less likely to accept things as they are. This creates a false sense of ease by which reality could be modified, and thus higher expectations for the world around them.
I suspect this misplaces happiness and contentment, but the two are also very strongly correlated for many people.
> I wonder from a modding perspective would it be better if all public methods are just the API users can call and they themselves create a way for mods to exist?
It's the way vintage story implemented modding. They developed the whole game as engine + modapi + hooking engine for stuff outside of hookapi.
Then most of gameplay is implemented as mods on top of engine using api and hooking. And those tools are open source, with central distribution point for mods, so servers can dispatch and send update of required mods to clients as they join.
Marvellous and elegant design. Makes running a server with client side mods a breeze, because mods are automatically pushed to the clients.
Though in the end, you can't really open all the interfaces and expect it to be stable without making some huge trade offs. When it works, it's extremely pleasing. Some mods for vintage story that are made purely using mod api can work between major game versions. Even server/client version check is intentionally loose as mismatched versions can still for the most part interact across most of mechanics.
In practice, to preserve balance of api evolution and stability, not everything in the game is in the api, and thus you have to use their hooking api, and stuff that is not exposed tends to break much more often, so mods require manual updates, just like in minecraft(though not as bad, tbh. In minecraft nowadays modders tend to support both fabric and neoforge/forge apis, targeting each for at least a few major versions. In vintage story, you only gotta support one modding api heh).
Not in any civilised country. Criminals do have guns in my country but firearm use is incredibly rare and use is restricted to crim V cop and crim v crim because police response and enforcement are so harsh for gun crime it isnt worth it unless it quite literally becomes life or death.
So then non criminals, while not armed with guns, face no real gun violence because even getting access to guns requires critical thinking and intelligence at least sufficient to understand risk vs reward well enough to understand civilian pop isn't a reasonable use case for firearms. Any firearm related incident here is a multi week news item. Stuff thats everyday in the USA and doesnt even make local news.
So, our cops and our criminals are armed, and i can trust my kids wont get shot up in school, i wont get shot in a store robbery, or by a disgruntled coworker etc.
You dont quite understand how bad it is I think, USA americans who move here have an adjustment period and usually need mental health support coping with leaving a country where getting shot in a road rage incident, for example, is a real risk. I had a colleague driving break down after cutting someone off accidentally, the cut off swerved ahead of us aggressivly stopped traffic got out and started shouting. Eventually wore themsleves out, as they do, got vack in car and kept driving. Didnt stress me too bad but my coworker driving totally shut down. Why? A year earlier a coworker in the USA did something similar and the person with road rage got out and started shooting at their car.
If you like sharp cheddar, the best cheese in the world is "Cougar Gold" from WSU Creamery in eastern Washington, USA, a region not known to be a hotbed of find cheeses. It comes in a can, also not thought of as a delivery vector for a great cheese, but there you have it. Tastes great out of the can or you can age it for a few years in the refrigerator. Five or 6 years is fine. I absolutely love the crystals. No mold forms unless you open the can.
WSU's other cheeses are okay but do not stand out to me. Nothing from England or France has delivered the sharp cheddar experience like Cougar Gold.
After reading the paper I’m struck by the lack of any discussion of awareness. Cognition requires at its basis awareness, which due to its entirely non verbal and unconstructed basis, is profoundly difficult to describe, measure, quantify, or label. This makes it to my mind impossible to train a model to be aware, let alone for humans to concretely describe it or evaluate it. Philosophy, especially Buddhism, has tried for thousands of years and psychology has all but abandoned attempting so. Hence papers like this that define AGI on psychometric dimensions that have the advantage of being easily measured but the disadvantage of being incomplete. My father is an emeritus professor of psychometrics and he agrees this is the biggest hurdle to AGI - that our ability to measure the dimensions of intelligence is woefully insufficient to the task of replicating intelligence. We scratch the surface and his opinion is language is sufficient to capture the knowledge of man, but not the spark of awareness required to be intelligent.
This isn’t meant to be a mystical statement that it’s magic that makes humans intelligent or some exotic process impossible to compute. But that the nature of our mind is not observable in its entirety to us sufficient that the current learned reinforcement techniques can’t achieve it.
Try this exercise. Do not think and let your mind clear. Ideas will surface. By what process did they surface? Or clear your mind entirely then try to perform some complex task. You will be able to. How did you do this without thought? We’ve all had sudden insights without deliberation or thought. Where did these come from? By what process did you arrive at them? Most of the things we do or think are not deliberative and definitely not structured with language. This process is unobservable and not measurable, and the only way we have to do so is through imperfect verbalizations that hint out some vague outline of a subconscious mind. But without being able to train a model on that subconscious process, one that can’t be expressed in language with any meaningful sufficiency, how will language models demonstrate it? Their very nature of autoregressive inference prohibits such a process from emerging at any scale. We might very well be able to fake it to an extent that it fools us, but awareness isn’t there - and I’d assert that awareness is all you need.
In college, some times a kid would go pass out in his car rather than drive, and people would Saran Wrap the car so they couldn’t open the doors to get out.
I think it all hinges on recognizing what opportunities automation helps.
For instance, I had to rename a collection of files almost following a pattern. I know that there are apps that do this and normally I’d reach for the Perl-based rename script. But I do it so irregularly that I have to install it every time, figure out how I can do a dry run first, etc. Meanwhile, with the Raycast AI integration that also supports Finder, I did it in the 10-15 seconds that it took to type the prompt.
There are a lot of tasks that you do not do often enough to commit them fully to memory, but every time you do them it takes a lot of time. LLM-based automation really speeds up these tasks. Similar for refactors that an IDE or language server cannot do, some kinds of scripts etc.
On the other hand LLMs constantly mess up some algorithms and data structures, so I simply do not let LLMs touch certain code.
It’s all about getting a feeling for the right opportunities. As with any tool.
This reminds me of the time that Google’s Paris data center flooded and caught on fire a few years ago. We weren’t actually hosting compute there, but we were hosting compute in AWS EU datacenter nearby and it just so happened that the dns resolver for our Google services elsewhere happened to be hosted in Paris (or more accurately it routed to Paris first because it was the closest). The temp fix was pretty fun, that was the day I found out that /etc/hosts of deployments can be globally modified in Kubernetes easily AND it was compelling enough to want to do that. Normally you would never want to have an /etc/hosts entry controlling routing in kube like this but this temporary kludge shim was the perfect level of abstraction for the problem at hand.
This place needs more of this kind of documentation.
I failed to use IP tables for years. I bought books. I copied recipes from blog posts. Nothing made sense, everything I did was brittle. Until I finally found a schematic showing the flowchart of a packet through the kernel, which gives the exact order that each rule chain is applied, and where some of the sysctl values are enforced. All of a sudden, I could write rules that did exactly what I wanted, or intelligently choose between rules that have equivalent behaviors in isolation but which could have different performance implications.
After studying the schematic, every would just work on the first try. A good schematic makes a world of difference!
The text-based software that would eat work management is one that embraces the incumbents rather than avoid them.
I want a bidirectional SaaS <=> YAML/JSON adapter. So that I can push and pull our CRM (and other SaaS utilities like project management) into a common (schematized) YAML format.
The YAML then can be analyzed and modified using LLMs and/or stored in git.
And then use the bidirectional sync to reconcile conflicts and push.
So I can do work processes on the console, and still collaborate with people who want the native web UI.
That's what they do to the people that figure things out. They discredit them so other people will not listen to them. It's the ones that go full tilt with lining the walls of their houses to be Faraday cages that make it all fringy cringy the rationally paranoid folks get lumped in with.
I had the absolute pleasure during my engineering undergraduate (Oxford) to take a biomedical module. One of my 'labs' was on nonlinear acoustics, specifically ultrasound applied for therapeutic uses. It was very captivating seeing a very focused point within a block of gel become ablated. A part I found particularly exciting was realising that it was a phased array of ultrasonic emitters, so that the point where the ablation occurred could in fact be placed anywhere you desired in the gel.
They showed us results of HIFU applied to real patients to non-invasively ablate tumours and treat prostate issues. As far as I can tell the probe creating the ultrasonic waves needs to be relatively close.
A thought I had at the time was if you knew all of the material properties of all of the tissues inside someone and their locations (say with an MRI) you could in theory apply this even deeper in someone than is currently possible - with a larger stick-on patch of actuators as a phased array.
Finally, another memorable thing that was discussed was what another researcher was doing with ultrasonics.
Stride (who I am delighted to say was a fantastic lecturer) was very interested in bubbles. She would construct tiny bubbles where the surface (or interior?) was made of a chemotherapy drug. These bubbles could then be injected into someone's blood stream and would be ruptured using ultrasound to allow for extremely targeted application of chemotherapy (the jet formed from rupture would be so strong it would inject the drug into nearby tissue).
Fascinating, fascinating stuff but of course developed over many years of hard work.
