When I answer questions in a public forum, helping the person who asked the question is only about half of the value I expect to get from my contribution.
I had the exact same thought when I saw the headline. For their purported use, both forums have bafflingly low signal-to-noise.
The Apple and Microsoft community support forums may have had more value years ago when the only people who knew how to find and use a forum were already technical. It’s hard to imagine now, but there was a time when making an account on a site to talk to other people was unusual for average people.
Today, the only useful community support forums I visit are for highly technical products. Anyone participating has a baseline level of competency to even get into the software or hardware, so conversation quality is higher.
The Apple (and Microsoft) community forums almost always have a 12–page thread of people having my same issue and no solution. There is also the strange phenomenon of the community members who want to be very helpful but are only copying and pasting “have you tried turning it off and back on again” or “wipe your device and reinstall” non-solutions.
I’m surprised the Apple community forums lasted this long. I can remember a couple solutions I found there, but most of my visits were frustrating experiences of clicking through pages of threads of people complaining about the same thing. Even when someone did post a solution, it could get lost in infinite posts from users who didn’t know how to use a forum but kept adding complaints to the thread.
According to my own browser history last time I landed on this forum was to figure out why the Apple Maps app was taking so much storage despite being a rarely used app. The post https://discussions.apple.com/thread/256084682?sortBy=rank, which was the first thing from a search engine query, completely solved the mystery. It was the stupid significant locations feature that I don’t need.
Then the second item in my browser history was https://discussions.apple.com/thread/253015477?sortBy=rank which explains how to change the location where screenshots are stored. Isn’t it a superbly intuitive UX design that locations of screenshots produced by Command-Shift-4 should be changed by pressing Command-Shift-5?
just kidding, the Genius Bar is still open
If anything, this is likely flooding LLMs with incomplete/invalid/useless information and it's just time they deprecated it in favor of something more modern and useful.
When I answer questions in a public forum, helping the person who asked the question is only about half of the value I expect to get from my contribution.
I had the exact same thought when I saw the headline. For their purported use, both forums have bafflingly low signal-to-noise.
The Apple and Microsoft community support forums may have had more value years ago when the only people who knew how to find and use a forum were already technical. It’s hard to imagine now, but there was a time when making an account on a site to talk to other people was unusual for average people.
Today, the only useful community support forums I visit are for highly technical products. Anyone participating has a baseline level of competency to even get into the software or hardware, so conversation quality is higher.
The Apple (and Microsoft) community forums almost always have a 12–page thread of people having my same issue and no solution. There is also the strange phenomenon of the community members who want to be very helpful but are only copying and pasting “have you tried turning it off and back on again” or “wipe your device and reinstall” non-solutions.
I’m surprised the Apple community forums lasted this long. I can remember a couple solutions I found there, but most of my visits were frustrating experiences of clicking through pages of threads of people complaining about the same thing. Even when someone did post a solution, it could get lost in infinite posts from users who didn’t know how to use a forum but kept adding complaints to the thread.
According to my own browser history last time I landed on this forum was to figure out why the Apple Maps app was taking so much storage despite being a rarely used app. The post https://discussions.apple.com/thread/256084682?sortBy=rank, which was the first thing from a search engine query, completely solved the mystery. It was the stupid significant locations feature that I don’t need.
Then the second item in my browser history was https://discussions.apple.com/thread/253015477?sortBy=rank which explains how to change the location where screenshots are stored. Isn’t it a superbly intuitive UX design that locations of screenshots produced by Command-Shift-4 should be changed by pressing Command-Shift-5?
just kidding, the Genius Bar is still open
If anything, this is likely flooding LLMs with incomplete/invalid/useless information and it's just time they deprecated it in favor of something more modern and useful.
> ACR in LG TVs does not collect or store screenshots, screen images, screen recordings, or video recordings from the TV. Instead, it uses audio fingerprints generated from content audio using the TV’s internal soundboard (not a speaker) to identify the content being viewed.
So based on the fingerprint they know what content is being displayed, but they can say they're not recording your screen.
Maybe he just said that to make a sale, but yeah the fact they offer that targeting alone is quite telling.
LG: No. ACR in LG TVs does not collect or store screenshots, screen images, screen recordings...
Hold on, we already know this is not true. There is even an option in the settings to disable this (which is usually automatically reverted by LG within a week).The setting has the obvious name of "Live Plus".
There are reasons why folks know the names of notes in some positions better than others.
When I was playing a lot of bass for folks in low rent with bands that were playing standard music and never rehearsing, I generally only paid attention to the low string and worked my parts out (often on the fly) around the relative pitches.
If you're trying to keep up with the bass part on a song you've never heard before while performing it on stage, it's much more relevant (and far easier/faster) to know the position of the minor 3 note of the scale than it is to know what note is the minor 3.
Over the decades I play a lot more piano, and that changes. I play a lot of blues and jazz but am quite poor at reading typical rep for the instrument. While I started out mostly playing using chord fingerings (and inversions), the more I play the more specific I can get on my understanding of actual notes. Because I've been playing a lot of clarinet (which forces me to transpose a whole lot, including reading a part and transposing on the fly), the names of specific notes has gotten a whole lot more important, but also easier with practice.
On the pedal steel (which I have only been playing for a decade on and am still coming to terms with), while I can pull all that knowledge I am still usually playing based on a notes position- I know what string/lever combo is going to get the 6 note in a given scale rather than thinking "I need to play an A to get this C chord to be a C6, and that's this position on the neck with the BC pedals down or that position with the LKR lever pushed.
All that is to say, it's okay to not know the names of notes if you understand their function related to the melody.
I thought Bluesky was supposed to be better than X/Twitter, not worse. Bummer.
Although it does feel the finds are getting increasingly hard to spot, every now and then you get a how did everyone miss that moment. Perhaps not surprisingly, most of the remaining impressive finds tend to be in woodland, using the Digital Terrain Model data which can peer beneath the forest canopy, like this Mexican one today, or are within newly released coverage which is promptly pounced on by armchair archeologists.
Not sure what my point is here except... to me this story still feels like a function of the amazing recent progress in lidar coverage and data availability (not to mention the incredible technology behind it), rather than an AI one, although I don't doubt that pointing a capable model and a healthy token budget in this direction might well be able to sweep up a few of the remaining discoveries.
"Prior art has reduced the novelty of the discovery" is a great one
We are reading this article because it continues and amplifies the AI hype machine, and no other reason. If a motivated amateur had made the discovery through any other means, and motivated amateurs do things like this all the time, then it would never have gotten an article, never shown up on the HN feed.
The Walt Disneys of the world screwed themselves on this one. If copyright was still the 20+20 it started as, and if the bulk of people being "stolen" from (don't get me started on using theft to refer to IP), then I think most people would be much more up in arms over the AI industry.
But, in a world with sane copyright laws, perhaps AI companies would have different approaches. Today, if they want anything after 1930, they're either breaking laws or in uncharted territory.
And siloing our knowledge is a silly response even if you are a copyright maximalist.
The lineage of every LLM of relevance today was the largest theft of intellectual property in human history. Every digitised creative work, whether in the public domain or not was taken, often outright pirated, with the explicit intention of being able to trivially produce compelling forgeries. Physical works are being enthusiastically destroyed to digitise them to further feed the hunger. And outside of a few court cases, the original creators across the world have been paid nothing for their work having been stolen and repurposed to put them out of a job.
Meanwhile, those same digitisation efforts have resulted in badly behaved scrapers from all comers absolutely thrashing the entire web, in many cases exponentially increasing the cost of hosting for smaller entities. Larger entities care less about that but are still enthusiastically walling their gardens so they can monetise the output of their communities rather than continuing to allow it to be stolen freely.
We are siloing our knowledge out of desperation. I'm sympathetic to the idea that knowledge should be free but that isn't possible when bad actors like Google and OpenAI are preying on the commons.
Perhaps google SWE should have requested a literature search before publishing his results as novel
But Dr. Estrada-Belli found something that was undiscovered. Finding this structure wasn't his number one goal - it was the side effect of a larger anthropological assessment that allowed him to improve estimates about population density of the north versus south, how Mayan homes and farms are distributed, what this means about social relationships between the elite and common people, how different regions were interconnected, etc.
Interestingly, one of Dr. Estrada-Belli's primary conclusions is not that these structures were only used by "the local elite," but that the closeness of residences and farms to these community sites suggests that the elite and the common people actually had a much closer and nuanced relationship than we previously thought. That's the opposite conclusion you'd get from the Google SWE's assessment.
Knowing that a Mayan site exists is one thing. Understanding what it means is another.
My own attempts to use agents to develop new historical knowledge [1] point to this as being both a very promising and interesting domain, but also one where the agents reliably and repeatedly make claims of novelty that are based on having read ~80% of existing research. Obviously to make an actual well-grounded claim of novelty you basically need to approach 100%.
This is partly why math is so tractable for this sort of thing - mathematics papers tend to be publicly available and searchable, whereas for history, it might be the case that you have an agent swarm duplicating a find that some French person in the 1870s previously reported in an obscure undigitized book.
[1] Detailed more here: https://resobscura.substack.com/p/using-opus-55-to-discover-...
> Agent: One major village doesn't seem to have been registered.
The idea of just brute forcing discovery with agents on lidar is really cool, but doesn't the story ultimately rest on the agent making a mistake in its literature search?
> This story is going wild on X and elsewhere. The site was already published by Dr. Francisco Estrada-Belli of Tulane University ages ago. This is why we have peer review. Mexican gov didn't have it in their database, but that doesn't mean it is unknown/unmapped. https://pietromiotti.com/latest/maya-site/
Basically: already known, not in the Mexican Gov database, but in published literature... and open-access.
Link to the previous publication: https://doi.org/10.1016/j.jasrep.2025.105288 (Journal of Archaeological Science: Reports 66 (2025) 105288)
The Mexican govt may not have had the right records, but you can see what the site looked like at the time it was first found here: https://bsky.app/profile/indyfromspace.bsky.social/post/3n22...
I appreciate the enthusiasm. I'm not sure I agree. Especially since this was a SWE and not an archeologist / anthropologist announcing this (especially if the goal is to understand and preserve history -- not get headlines for AI).
The best way to protect a site is to leave it alone. If we start finding dozens or hundreds of sites it will be more than what archaeologists can excavate and protest. Treasure hunters and looters don’t care about stratigraphy and the processes involved for doing research. Maybe the cat is out of the bag on this one, but good for thought.
Edit: I’m not saying we shouldn’t have people use AI to do this or that no bad actor will. This comment is in response to the sentiment I am seeing in the comments that we should lidar the whole world and have AI find any anomalous structures it can. There is no way for archeologists to excavate and protect all those places in that scenario
The final barrier for super intelligence, or perhaps even just "human intelligence": can it materialize "new fields/ideas" without large datasets of human made and curated existing attempts?
Anyway, I can hear myself beginning to sound like a hater now, so I will stop here. I hope it turns out to be right, and in that case, congrats on your wonderful discovery.
These interventions target very complex systems. It's not unexpected that we need to try a bunch of things that don't work before we find something that does, to the extent that most of the things we try are ineffective, right?
Edit: I wrote the above before reaching the end of the article. By the end, the article reaches a similar conclusion, albiet with less science and more mysticism.
Maybe that means it's a good article, leading me to reach its conclusion before taking the stance itself. On the other hand, the article's leading sections gave such a strong impression that the author thought something needs to be drastically changed about the current system — the opposite stance from its conclusion — on seemingly shakey grounds, that I almost didn't finish reading it. I'm not sure what to think, aside from please leave innocent goats alone.
Unintended consequences are inevitable. The danger isn't that they'll exist - it's that they'll be ignored entirely or ignored until they cannot be, that the desire for panacea produces a willful blindness to their existence or myopic fixation on their effects to the point where the value of the intended consequences are ignored.
Another relevant example here is vaping: an amazing win for harm reduction in existing smokers, but an attractive on-ramp to the addiction for some who would have avoided it otherwise. No panacea.
> That would be a beautiful study, but it wasn’t the study that was actually conducted. The “lottery tickets” in question were in fact football cards, each one with a picture of a player, their team, etc. Some participants were given the opportunity to choose their football card and some had a card handed to them. Later, just before the drawing, all of the participants were asked how much it would take to buy their card back. On average, the pickers asked for $8.67, while the not-pickers said $1.86.4
> I’m sure you can see the obvious and less exciting explanation for these results: when people were given the chance, they picked their favorite players. The people who didn’t get to pick ended up with a card they liked less. This “illusion of control” effect is merely a “reality of people having preferences and acting on them” effect.5
Alternatively, people who are knowledgeable of a subject will have selfishly biased opinions about it, which they value more than unknowledgeable people will value an arbitrary stance on the subject. From experience, this seems to affect things beyond situations of chance like lotteries, and infests collaborations like businesses in ways such as Not Invented Here Syndrome or generally poor management choices that fail to consider situational factors (e.g. overarching decrees that are ineffective in certain situations/locations/applications).
https://www.health.gov.au/sites/default/files/study-of-the-i... (page 12)
They also tried quitting more often (p=0.013)
This example provides an easily understood illustration of why so many social programs fail. Simply put, the people proposing and creating the programs have zero understanding of the people whose lives they are trying to influence and control. Like generals ensconced in their offices located not even on the same continent as the front line they study maps and tables and hear the advice of experts with even less direct experience than themselves and then dispatch orders that arrive too late and attempt to command a reality that does not exist. The reports they receive back show nothing has changed or the situation has got worse and yet they never adapt or see their own fault. Why should they? They've suffered no consequence.
It is much more of "let's sell cards to crypto people, but nerf them, to not harm our enterprise margins", not "we've got a ton of subpar hardware, let's to something with it".
Anyways, that's what I tell myself as I taste my bowl of sour grapes.
I do, however, see a massive difference between "AI as tools" and "AI as creative director". I agree with the mindset of "I want to hear stories from humans" and "I want to experience creative expression from humans". But some of the current discussion feels like the arguments we had back in the day of whether Photoshop/digital media/video games were "real art" or not. If a human has creative vision and uses a robot stir-er to mix their paints, I don't think that should invalidate their painting. We can still judge it, though.
It sounds like this author’s argument is “AI in games sucks for lots of reason but mostly because it robs people of jobs.” I don’t disagree with that in theory but the real question is whether House House would have actually hired another human.
My guess is that they would’ve either delayed it more, or not known about the bugs and released it. They are purposefully small and bringing on even a freelancer introduces a lot of complexity and room for error. So too does AI but ultimately you control the output. You don’t have to worry about it being late, or it having a bad day.
If the end result of using AI is an artful, beautiful game like Big Wall, I’m all for it.
In my opinion the metric shouldn’t be whether AI was used, it should be whether the end result is *good*. I realize that’s subjective but I think we can objectively say Big Walk is a wonderful, artful game. When AI is used and the output is bad - as was the case, say, with those Coca Cola or McDonalds ads - that’s when we should question it.
When it’s being used for artwork or writing - I also think that’s a valid argument against it because it is, as we all know, utilizing artwork and writing without consent.
Is that true for code? Maybe some code but we would all say, I think, it’s much looser around code than creative outputs like artwork and writing.
It sounds like House House used AI like a tool the same way they did whatever engines or coding tools they used.
The metric should be quality.
AI is here and it trivializes what used to be hard. Developing software used to require feats of skill and endurance, and we're used to judging software based on that. Now it doesn't.
We will have to get used to judging software based on the output not on the input. Whether what was made is unique, interesting, creative, not whether it took a lot of time or knowledge.
There is no going back, only forward.
Absolutely not. Constraining the set of possible actions instead of having you verbalise what you want every time is often a feature, not just a technical limitation. A camera with a shutter button is better design than having to tell the camera “please take a photo”.
At the supermarket, I personally also prefer the self-checkout machines over going to a human cashier.
Commodities like todo apps and calculators rarely compete on features, they compete on product design. This includes look and feel, relation between elements, design choices on what exact common features are available.
All products are, at their essence, just a set of design decisions stitched and shipped together.
Now, making these design decisions is hard. It requires knowledge, consistency, and insights into how real people operate real products. Even as a sole user of the app you build you rarely know what you actually need.
LLMs are 'design-less' in their essence. Building your own todo app takes literal seconds and it all looks simple because LLMs will default most of these design decisions for you - until you try to use your new app daily and notice it somehow sucks. Building a good todo app or good calculator requires tweaking, publishing, polishing, and solving bugs, testing, rinse and repeat.
Another tricky side of this is that you might know logically what features you want, but you are not selecting one product over another logically. You need to try and see if that works for you, all the vibes and good parts and bad parts and design choices and colors, till you find something that "clicks" for you. Using pure Claude as a todo app only works as long as you want to have more Claude in your daily life.
In the meantime app store provides dozens of well-reviewed alternative solutions which look good and require zero maintenance.
And that's just a calculator or todo app. Non-commodity apps are even harder than that.
For instance; I don't think LLMs will be replacing Spotify, Facebook, Insta, or Youtube for my parents. They absolutely do not want to purely interact with a blackbox. They want to scroll through songs/shows/etc. they want to tap on it, and have the app do the thing.
Even as a SWE, I have absolutely zero desire to interact with an LLM for everything, but I'm not the litmus. I have found use with these tools for taking on some nested set of tasks, but at no point do I want to give up the app entirely.
I think folks who live in spec-driven worlds just don’t appreciate how poorly understood the capabilities and processes of computing and networks are, to the point where even if you gave people hallucination free LLMs you’d probably find people just frustrating themselves because they can’t figure out what they want, what it should do, and how it should be used.
Quite apart from the huge chunk of the app ecosystem that relies on common protocols, centralised services and so on.
Essentially every single non-builtin app on my phone fundamentally requires the internet to work, and is backed by some sort of SaaS with a proprietary API. And even if/when the APIs are open, I doubt any normal person is going to decide that from now on they want to somehow use YouTube or Tiktok or Feeld or Spotify by talking to ChatGPT.
Apple, to me, is the winner in the end of this AI chapter.
I might be one of only few people who think Apple is a loser in the AI chapter.I don't think it shows yet but I think the dominance of the App Store will end. I think a ton of iOS apps will be replaced by ChatGPT/Claude. I think there is a big opening for a company to redesign the phone from the ground up purely around an AI assistant instead of apps.
I think AI will severely weaken iOS, App Store, and the iPhone in the next few years. It was nearly impossible to start a 3rd competitor to iOS and Android until recently because no one is going to redesign their apps for your new phone. Today, that's different. Many productivity apps are just being replaced by GenAI/ChatGPT/etc and services are making it easy for AI agents to access directly without an app.
Not to mention higher chip prices will eat into hardware margins.
I do not think local LLM inference will make up for lesser iPhone dominance.
Could be the winner, in your opinion. They are extremely well positioned with hardware, devices, ecosystem, privacy, brand value & trust, and a significant active base. So far, they have not yet delivered on any useful AI application. There are so many opportunities in both MacOS and iOS, I guess they just need a new software VP.
There's a name I haven't heard in a long time! Claris (always an Apple subsidiary, since being founded in 1987) renamed themselves to FileMaker in 1998, but apparently they rebranded back to Claris in 2019.
Looks like they've mostly just released annual upgrades to FileMaker for the past decade, but they did add MCP to it last year: https://www.claris.com/blog/2025/why-mcp-matters-for-claris-...
Right now 128GB MacBook is the top of the line and you could do Qwen 3.8 Flash or similar.
There is a rumor that the M7 chip can use 1.5TB of memory which would imply Apple is aiming for more memory on devices.[1]
Would that imply the entry-level MacBook will have 128GB and top of the line models could run larger reasoning models? Then the question is price and if any of this will translate to iPhone for on-phone models.
With how expensive memory is, IDK if they can pull this off but I hope they do
[1] https://www.tomshardware.com/tech-industry/semiconductors/ap...
Distillation works: we can get models leaner, have better performance with lesser and lesser parameters, more efficient, running locally. Apple gets this and we'll see the result with M7 Max/ultra chips and I reckon this will be one of the titular apps when M7 line of chips are introduced.
I guess it explains the haste Anthropic and OpenAI are in to IPO, cash out and leave the the retail investor holding the bag.
Dealbreaker. Too bad they couldn't get it legal on 45mph or less. It would literally open up 99% of non-highway routes.
I know a kid who drove his tractor to school once in a while, it topped out at ~20. If dad had the truck and mom had the car, what else was he gonna do? Using a low-speed vehicle in a pinch is not a new idea to these trucks' target customers. Having such a vehicle but with A/C and airbags is probably a huge selling point, actually.
[1]: https://www.deere.com/en-us/products-and-solutions/gator-uti...
The Toyota eCVT is an engineering marvel[1].
The hybrid power train is simpler than a regular transmission and made of more durable parts.
The clutch itself might not have to disappear for more fine grained power delivery, the new Ferrari clutch-by-wire[2] is a similar bit of a few hall sensors talking to the ECU.
You can build a simulacrum of a manual low-mode transmission without needing to use it constantly in stop-go traffic or while sliding backwards on loose dirt.
[1] - https://www.youtube.com/watch?v=r2L5VOtf47Y
[2] - https://www.ferrari.com/en-EN/corporate/articles/ferrari-12c...
It's a shame they don't really make them anymore. If I could buy a modern vehicle in the States that had the following properties:
- 2 seater
- Pickup truck
- Manual transmission
- Minimum 6 foot bed
I'd probably do it in a heartbeat. But even these somewhat weak constraints fail every vehicle in the USA market.
They aren't comfortable to drive at all (although just having A/C at all on a hot summer day in the field is a godsend), and I wouldn't want to do longer trips in one - although you certainly could in a pinch.
It seems like Toyota/Scion is just testing the waters here, and I'm not sure how successful they'll be. But I hope there is a future for kei trucks in the US.
As for the imports, I saw one of these 90s-era right-hand drive kei trucks at a parking lot a few months ago and talked with the owner. He was a young guy who lived in Boston, said it was super easy to park. Speed maxed out at 70 mph, which is fine for local trips but maybe not for long highway trips.
For people in jurisdictions that allow 30 year old truck imports, and are interested in getting one, there are other countries that use such trucks and have left-hand drive. Taiwan has models from CMC and Suzuki, and I believe South Korea also makes them.
After that, when vehicle sizes start trending down towards reasonable, we can look at getting speeds up without reducing overall safety.
On intercity highways in Japan you are driving next to as large trucks as anywhere I've driven.
There's sizeable demand for people who want to be able to do runs to the bigbox stores for garden and DIY renovation supplies and store it the rest of the time.
The interpretation here is not so much that an LP can do Astra's work -- after all the Astra prompt was "improve Qwen's math by changing weights" or similar. Instead, it's that with some guidance (eliminate this behavior, preserve that behavior, as expressed through linear constraints) the solver is much more efficient than Astra's trial and error. So essentially the solver would be a way of cutting through all the time consuming stuff and expressing Astra's intent more immediately. And then presumably Astra could iterate on that to a better solution.
The use of an LP solver here is a really cool insight.
Elixir is well handled by LLMs at this point, and we keep the “easy to scale and maintain” aspect (operational characteristics of the runtime are very good).
I can safely say that total cost of ownership is excellent.
""" This is a site designed to serve as a center for information - and by "center," we mean center. ByteCode.News is a site fed from discord, slack, IRC, and here on the web, meaning to present a common information graph and a common set of services. """
From my quick skimming of the site it just looks like hundreds of AI articles. More than likely it's just an AI bot that generates articles after some threshold of engagement is reached on "discord, slack, IRC".
There are lots of Ads that are posted as if they are articles for example: https://bytecode.news/posts/2026/10/cheerpj-5-launches-java-...
The article itself is just an extremely odd hit piece against Zig, I'd even be guess this is a form of "rage/engagement bait".
Not true! It just means (realizing a) vision is more important to them than becoming popular. It's their choice to make.
The important question is when/whether it will hit 1.0 and what its commitment to stability looks like _afterwards_.
What I wrote with Claude is basically everything else: custom LLVM passes, a hand-written runtime that replaces the Windows calls, a Direct3D 11 to Metal layer and the shader translation! Plus fixing the crashes one by one by iterating and playing. All details are in the Pipeline section of the README if you're interested: https://github.com/adrbn/bo2-mac#pipeline
1. The Secure Enclave being inaccessible when you're not present is a feature, not a bug. If you need to run headless then its not the correct solution to your problem and you'll have to find another.
2. You don't need an SSH agent proxy, you can use a `match` block in your `ssh_config` with something like `host * exec "test -z $SSH_TTY` to check whether you're operating over an SSH connection and select Secretive's SSH agent if you're using the machine locally.
A lot of the Security Framework came from Classic, hell, the idea of a keychain came from Classic! Just a mess.
It's funny you mentioned that. The GitHub repository is a mirror of https://git.zx2c4.com/wireguard-apple. You cannot create issues there. You're supposed to send a bug report to the mailing list, which is enough friction that none of us did so far.
When I installed WireGuard on macOS, I was happy to discover that it stores private keys in the system keychain. Accessing the private key requires Touch ID.
Then one day after a system upgrade, the WireGuard app crashed on startup with:
[APP] Unable to open config from keychain: -25300
Then the app deleted all profiles because they are all "orphaned", apparently for "keychain consistency" [0].From then on, I just use a text editor to edit my WireGuard configuration files, and import them to the app. The bug still exists to this day [1].
[0] https://github.com/WireGuard/wireguard-apple/commit/dfb685f2...
[1] https://www.reddit.com/r/WireGuard/comments/wyt828/osx_wireg...
I recently had a gig collecting soil samples in rural Alberta, and we relied on Starlink to upload the data as we worked.[0]
It was surreal trundling through a remote farmer’s field in a skid-steer with a funny-looking square dish on top, surrounded by a herd of bison or cattle.
Stepping outside of the machine to take a piss on a tree and hearing the motors in the dish whir as it repositions itself to get a better connection was startling and neat. It’s one thing to read about the dishes having that functionality but another to experience it while you’re doing something as mundane as a basic bodily function.
Pulling the dish and the mount off the skid-steer and tossing it in the back of the truck, and seeing the off-the-shelf Ryobi battery and inverter that powered it, all scuffed up and covered in dirt, makes you realize that as magical as it is right now, it’s just a machine. People thought that transistor radios were pretty magical when they came out but eventually they just became an everyday thing.
Soon enough these things won’t be so big and expensive, and there will be a market of providers offering even better service. What comes then will be scary from a privacy perspective, but it may also enable so many positive things that we can’t yet imagine.
“The most profound technologies are those that disappear.”
Then, recently, SpaceX changed the terms such that the 100GB and 300GB subscriptions are no longer usable internationally (technically outside of North America). You have to pay for the unlimited service tier and even then can only use it for 30 days before returning to the home region.
A huge decrease in utility and a tripling in cost. A new device with a built-in battery is definitely not going to make up for that.
(Still a great service when it works, am posting this from remote western Mongolia.)
I've got deep concerns about the politics side of the company, and the future implications of them being able to decide where and who gets coverage. But from a technology perspective it's doing things I didn't really think were possible a decade ago. Having signal in the bottom of the pit, or way out the back of the Pilbara is just crazy.
I just checked a few weeks ago and “Roam” does no longer include international coverage at all. Only “Roam unlimited” does, and only for 30 days at a time which entirely defeats the purpose for me. Also no way to replenish this quota or buy additional, you have to go back to your country for it to reset.
My SIM card already gives me 14 days of roaming included, so Starlink is just marginally better for my use case.
I’m sure it’s regulations related but still a bummer :(
Those are the three options for your mandate.
the non-government intervention option is just for Starlink to prove the market, and others can move in. SpaceX is willing to sell them the ride for a decent price, in relative terms.
That means I can now head out on Wednesday after work, drive 3-5 hours to the middle of no-where, and work Thursday and Friday. But each of those days, I am able to be done working and then at a camping site with my family. Go on hikes, fish, swim, etc.
So now my whole family can enjoy being in the wild, and I don't have to burn up vacation days. And we don't have to try to jam it all into a weekend were you feel like your just travelling the whole time.
Side note.. Having no signal on the west coast can actually be extremely dangerous, with how fast some wild-fires have spread. You can have one 10 miles away and not know it with the wind blowing the other way, and if it shifts direction, you can have a very limited time and path to get away.
Being able to check tools like WatchDuty and weather reports from the middle of nowhere is a safety feature.
I expect the problem isn’t necessarily the AI generation itself, but the difficulty to distinguish between someone that’s really understood the problem domain versus someone with LLM-induced “Dutch courage”.
That in combination with a large uptick in volume of community interactions (issues, PRs, …) risks burning out OSS maintainers.
Perhaps giving it a few months/years for the flurry to die down, and for people to establish better best-practices for using these tools is the motive.
It's not a mantra, it's the reality of the business: if I must bear responsibility of the code facing a customer, then I have to understand the code. The AI can be a wonderful tool, but people are still calling me to fight fires.
It absolutely does. You lose understanding of the code, but what kind of understanding do you actually gain in turn? AFAICT it is purely a tradeoff between velocity and understanding.
FWIIW Quality was always cheaper and quicker for anything but a prototype. This is just as true now. The problem was that many people were too lazy and unfocused to make quality work and those people are only too happy to agree with these comments
Do you have examples of where this actually worked for you? How large was the codebase, how long did you have agents generate the mess in it?
I ask because my experience is pretty different, even with Opus 5.5 and Astra - unleashing agents on a messy, vibe coded repo only seems to increase the mess. The agents just slow down more and more as they keep generating further mess, they make more and more incorrect assumptions based on bad code previous agents left behind, and I grow more disappointed in their capabilities every day.
Actually reviewing all agent output thoroughly is the only effective way I've personally found of working with agents. In order to ensure that every line of code they add is actually there for a good reason, and not organized in a way that future agents will miss it, or misinterpret it. It's the only way I can prevent them from producing worse results as the repo grows.
I can imagine things like this happening very easily mid/long term: https://www.reddit.com/r/ClaudeCode/comments/1xq2n3t/a_year_....
As of 2026, I think LLMs still lack vision, and long term, tend to build a very scattered codebase, if maintainers don't pay a lot of attention.
LLMs do have cognitive limits as well!
No doubt code quality increased substantially, but I've been wrestling overengineering for a long time, with both GPT/Claude - they will take any small chance to write excess code/documentation/specifications, anything - they seem to love reinventing the wheel. Heck, even prompts sent to subagents are walls of text.
Explicitly requiring simple solutions works for simple problems, but for more complex ones, complexity quickly creeps in. I even ask the alternative model to challenge the complexity of solution, but doesn't work really well.
There is a perverse incentive for AI companies to train models to be verbose, as it increases the tokens consumption.
"AI writes shallow tests" - used to be true, not true anymore since Astra and Fable 5.1 / Opus 5.5.
"AI writes overly complex ccode" - only if you let it. A "do not overengineer it" or "Pareto, 80% result with 20% of effort" go a long long way.
"Reliance on AI decreases human understanding" - human understanding does not decrease, it just moves up a level or two. The same way you do not really understand how the Linux kernel works, nor do you know how assembly really works (with probably a bunch of exceptions here given this is the HN crowd!). And then there is hardware and physics too.
Understanding code, algorithms and data structures becomes a rarer need than it used to be.
"AI moves too quickly to maintain a high quality bar" - if you are stuck with the mantra that humans must review the code today, then obviously that statement becomes true. The problem is the assumption, not the observation. The good news about AI progressing fast is that coding AND reviewing get better and better with each release.
I know it is tough to let go. But as a software engineer, the sooner you do it, the quicker you will learn to yield a much, much more powerful weapon.
Programming is about engaging with high level mathematical abstractions.
To the extent AI can do this high level thinking, it is going to be able to do absolutely everything else humans can. Programming (when not underestimated) is as hard as the hardest cognitive task humans can do.
I've always thought that good engineering should go smoothly by definition. You shouldn't be juggling a ton of bugs and broken develompent pipelines. The problem is justifying this in a work culture that doesn't care about quality and is stuck looking at numbers that can be immediately justified.
AI can generate "confidence" only in very limited amounts. It can help with testing, but that becomes very expensive and hard once we leave the realm of tests that can be simply written with code, like unit tests. At some point, the only way to increase the confidence in a codebase is actual testing with actual, real user interaction. And once that's maxed out, the only way to further generate more confidence is to get it into production and let real users (not test users, production users) find the remaining bugs no tester and no AI ever managed to hit.
This is the sole reason why AI doesn't make code "disposable" - yes, it can rewrite any codebase far more quickly than any human, but that new code will start at low confidence values - AI cannot transfer the confidence that the old codebase achieved simply due to being smashed against reality in production use to the new code it writes.
This is also the reason why it still makes sense to maintain libraries, even though AI could not just theoretically, but also practically write a lot of functionality from scratch that we usually import into projects via open-source libraries: the newly written stuff doesn't come with the same confidence as the already-battle-tested library does.
"Maintenance" does not mean "development after the first week".
My immediate question would be what kind of adversarial reviews and deterministic gates did the author write to capture the dimensions of maintainability (lack of DRY, cyclomatic complexity, unclear naming, poorly architected flows, etc) that they cared about.
Don't get me wrong. When I was speeding along at 200 PRs a day (personal projects - I would not have inflicted them on others) I pretty quickly slopped together a big ball of mud, but as I'm re-generating my estate (a) the models are a little better but (b) I'm adding a lot more rigor around verification (correctness, performance, security, operational costs and maintainability). It's not an easy problem to solve, but it feels to me like an engineering endeavor, not speculative rocket science.
I fully understand that many AI generated code bases do indeed suffer from more incidents and less maintainability, but I think it's important to distinguish between what is common and what is possible as the fix for one is improving the rigor of your verification whereas the fix for the other would be either accepting crappy code or giving up on LLMs.
That said, my experience tells me that enterprise and business coding has rarely ever been about stable or robust codebases. We engineers and a fraction of competent engineering managers and a vanishing small number of directors fought against business interests to ensure quality was priority when it came to code, but it was always an uphill battle and we were oftentimes disciplined for spending too much time on quality and design.
A timed cadence of release is anathema to quality code because you can't timebox it.
So, AI is just the extension of that. Do I try to ensure my agents design code I would consider to be good? Yes, absolutely! But I've fully outsourced it and I find it's also fully capable of fixing it's own mistakes. I've gone far beyond anything I individually or even with a team was ever capable of with AI assistance, so I believe I just have to apply my experience and skills into management and architecture rather than actual lines of code.
Time only will tell how this plays out.
Wallaahu aʿlam.
At 30 users you have no idea what maintenance looks like. That's literally what maintenance is - responding to real world usage.
Come back with your experience when you have lots of users that stick with your app, you're putting out fires and implementing new features. Your experience will be meaningful after 6 months to a year.
I'll wager that right now you have a PoC that needs a lot of work to be something that retains users. That's not a criticism, that's just how it works for every startup.
I have had experiences out of my technical depth where I’ve instructed an agent to do something technically nonsensical. The agent tried to do it, creating a mess. Nothing works, I get frustrated, only to realize I have a fundamental misunderstanding of something technical.
A similar thing happens when you ask for something, but the complexity for the perfect solution is 10 x the complexity of a simpler, 90% solution. And sometimes you only realize that looking at code (or feeling lots of brittleness)
Doesn't seem like a good strategy to me.
Sorry, but at this point you have no idea what the maintenance looks like.
Right now, they're not great at following good software engineering principles. They do the job, with verbose code, lots of duplication, abstraction leaks, useless unit tests and so on.
Is it an issue? you could think that in the long term it'll be, that AI won't be able to handle the complexity it introduced, but I'm not really worried about it. Most software isn't that big, and agents are getting better by the day. And if you really care about design, it's not too hard to instruct your agent to follow your standards.
I wish it wasn't the case and that I could justify my experience and expertise for a few more years, but the facts are there.
Here's the famous commentary about Oracle RDBMS codebase of 25 million lines: https://news.ycombinator.com/item?id=18442941
Every big company codebase with millions of lines devolves into a similar state. The small codebase starts with clean conceptual integrity. It then inevitably decays into incomprehensible spaghetti code as more people are added to it. Various reasons for it including the later devs caring less about the code than the initial team of devs, deadlines, avoiding refactoring because of fear about breaking things, etc.
If you don't want AI to create fragile code, you have to apply the same quality gates that would have been applied to pre-AI hand-written code to keep everything clean. Most companies don't do that.
My code has never been stronger.
That's fine though. Progressive enhancement, adding features to a site when they're available but still offering a working site when they're not, is how we should build web sites. That way they work for the user's device rather than the developer's opinion of what the web should do.
Working that way completely removes the decision about whether or not to use a feature because it doesn't work for some people, and moves it to a decision about whether or not it's worth adding for the users on browsers that can use it. In the past that was a real development effort cost, but today where AI writes the code the effort is much, much lower.
If you're using AI to make something but still using heuristics designed to save coding time then you really need to rethink your mental model of how to decide what gets built.
Websites created today should all use server-loaded content for the first render, small page sizes, a sub-1s loading time, progress enhancement for features, and WCAG 3.1 AAA accessibility (maybe.. at least AA though) because doing that isn't any more effort than not doing it.
This would be deeply surprising to me, and I am the target audience for this repo. I'd expect the default here to be Widely Available only with some opt-in for the courageous. I don't know that I'd even enable it.
[0] https://github.com/GoogleChrome/modern-web-guidance/blob/4dd...
To be clear, the skills document how to use these features to solve common use cases, and then they give your agent a full browser support table for any APIs mentioned that are not Baseline Widely available -- and then your agent can decide whether to use them or not, based on your site's browser support requirements.
In most of these cases a cross-browser fallback is also documented.
CSS @function
CSS calc-size()
CSS interpolate-size
CSS corner-shape
CSS border-shape
CSS flex-wrap: balance
CSS text-fit
CSS text-decoration-skip-spaces
CSS scroll-axis-lock
CSS scroll-target-group
CSS :target-current
CSS scroll-initial-target
CSS container scroll-state queries
scrollsnapchange event
scrollsnapchanging event
HTML focusgroup
Element.startViewTransition()
CSS view-transition-scope
Interest Invokers (interestfor)
LanguageModel (Prompt API)
LanguageDetector
Translator
Summarizer API
Window.fetchLater()
Speculation Rules API
Long Animation Frames API
VisibilityStateEntry
PerformanceSoftNavigation
InteractionContentfulPaint
Connection-Allowlist
CSS url() integrity() modifier
HTML meta name="text-scale"
HTML template for
HTML processing instructions
PasswordCredential
Promise-returning scroll methods
Web App Origin Migration
Local Network Access permissions
Request.targetAddressSpace
beforeinstallprompt event
To be fair, the skills also recommend ~11 features not supported by Chrome itself. And the project does seem concerned with compatibility: "Guiding models to use sensible, lightweight fallbacks."That index page should link to plain markdown versions of all of the documents, and should be designed for search with grep to find the right answers.
That way I don't have to install anything at all - provided my agent has the ability to make HTTP requests I can tell it "Look for tips on https://googlechrome.github.io/modern-web-guidance-src/skill..." and it will fetch the index, then navigate to the most relevant documents - no MCP or npm or installation required at all.
So I'll take a 1-line CSS solution over 60 lines of ResizeObserver/setTimeout business. But.. best practices for frontend isn't just the code.. it's ensuring quality UX, that keyboard navigability works, that layout doesn't shift on users.
They tried really hard to help me recover my work even without a license but weren’t able to. They then apologized and proceeded to give me a full Suite license for free. I couldn’t believe it, I mean this is serious professional software and I had never even been a customer. That showed me that they really stand behind their product. I was able to start making a living off of it and eventually when I could afford it I bought another license even though I didn’t really need it that badly, mostly as a thank you.
The team over there is great and so is the software.
IMO that's a better model for consumers since you do get something at the end of it. And if you are a professional, you were probably already getting the latest and greatest every time anyways.
S4M is an open source extension to Max that allows you to run the s7 Scheme interpreter in a Max object, similar to the JS object in Max. Advantages over JS are that in can run in the high priority scheduler thread, enabling accurate timing, it has direct access to the file system from Scheme code, and allows you to make Scheme s-expressions directly in Max messages. It is also a very nice way to control the Live API, as the live API works on lists of symbols.
https://github.com/iainctduncan/scheme-for-max https://www.youtube.com/c/musicwithlisp
I'm planning another major release in the next few months as part of my PhD work.
Any Ableton Live users here that can chime in on how they solve that?
It is cheaper, supports Linux and I start to think it is also the better DAW.
It's on flathub so you can try it on any distro and see if you like it.
https://learningmusic.ableton.com/ https://learningsynths.ableton.com/
My first pass at it was a naïve search using the built in string matching. Because of the size of the file, and the speed of PCs, it would sometimes take more than 30 seconds to do a search. Ward wanted it faster, much faster.
I eventually came up with an algorithm that took the text you wanted to search for, and changed it into a special kind of bit mask, table. It was a table 256 bytes long, initialized to zeros. If the first character of the string you wanted to search for was a D, then the first bit of the $44 and $64 mask would be set, to handle case sensitivity. A wildcard * was only 1 character long, but would set all bits for that character. I then used the 8088 XLAT instruction and a very small loop ingest a character of the text being searched, use that as an index into the mask table, and AND that with the existing flag in a different register, then shifted it, checking for CARRY (a match!) and looping if not zero.
It took search down to less than 3 seconds if the whole file was loaded in RAM. The thing we used as a benchmark was searching for "DOS TECH REF", the IBM DOS Technical Reference Manual.
I can't find the code, lost it over the years, but it was one of my coolest hacks.
> Years ago, I was working at Video Seven, a now-vanished video adapter manufacturer, helping to develop a VGA clone. The fellow who was designing Video Seven’s VGA chip, Tom Wilson, had worked around the clock for months to make his VGA run as fast as possible, and was confident he had pretty much maxed out its performance. As Tom was putting the finishing touches on his chip design, however, news came fourth-hand that a competitor, Paradise, had juiced up the performance of the clone they were developing by putting in a FIFO.
> That was all he knew; there was no information about what sort of FIFO, or how much it helped, or anything else. Nonetheless, Tom, normally an affable, laid-back sort, took on the wide-awake, haunted look of a man with too much caffeine in him and no answers to show for it, as he tried to figure out, from hopelessly thin information, what Paradise had done. Finally, he concluded that Paradise must have put a write FIFO between the system bus and the VGA, so that when the CPU wrote to video memory, the write immediately went into the FIFO, allowing the CPU to keep on processing instead of stalling each time it wrote to display memory.
> Tom couldn’t spare the gates or the time to do a full FIFO, but he could implement a one-deep FIFO, allowing the CPU to get one write ahead of the VGA. He wasn’t sure how well it would work, but it was all he could do, so he put it in and taped out the chip.
> The one-deep FIFO turned out to work astonishingly well; for a time, Video Seven’s VGAs were the fastest around, a testament to Tom’s ingenuity and creativity under pressure. However, the truly remarkable part of this story is that Paradise’s FIFO design turned out to bear not the slightest resemblance to Tom’s, and didn’t work as well. Paradise had stuck a read FIFO between display memory and the video output stage of the VGA, allowing the video output to read ahead, so that when the CPU wanted to access display memory, pixels could come from the FIFO while the CPU was serviced immediately. That did indeed help performance—but not as much as Tom’s write FIFO.
[1] https://www.jagregory.com/abrash-black-book/#the-challenge-o...
> The slop is gone
> A sizeable portion of users seem to still believe we still suffer from a lot of made up and hallucinated reports by these AIs. We really don’t.
> Almost all the stupidity and lies we saw in the vulnerability reports made by AIs in the past have ceased. Since spring 2026 the slop reports are practically gone. Our current challenge is much harder: high volume, high quality.
Agreed. My fairly obscure company got hit by something like this last weekend. What stood out was the speed: attackers found something small, used it to uncover something else, and pivoted to clever exploits for the new thing within minutes. It hit a dozen of our apps in parallel within the span of a day, from a rotating pool of residential proxies, Tor, GCP and Cloudflare IPs.
I'm fairly confident it was LLM-driven. The payloads and throwaway accounts had names like "PT59553 TEST IGNORE" and "PocCorp1659r2", and it adapted to error messages the way a person reading them would, just never sleeping. A non-tech company with 100x the surface area and much more valuable data could be in big trouble.
Of course I used LLMs for the defense too, and they were amazing at log forensics and fixes. The annoying part was when I asked Opus 5.5 for clear repro cases of exactly what the attackers did, I hit the cyber safeguards. Opus was trying to keep the exploits for my own bespoke applications away from me. It was happy to fix things of course, but I worry if it really can't 'think' about actual exploits, its fixes will be less informed.
https://www.controleng.com/throwback-attack-hackers-attempt-...
https://esemag.com/water/russian-hackers-breached-quebec-wat...
https://www.cbsnews.com/news/us-water-systems-cyberattacks-i...
https://www.bbc.com/news/world-us-canada-55989843
edit: formatting urls
All of them were real bugs. None of them were false positives.
The quality of the reports was exceptional. (My baseline is doing security defense on a browser engine, so my baseline has a large sample count and is probably representative of what experts are capable of.)
The quality of the proposed fixes was alright. I took some of the fixes verbatim. I used most of the fixes as significant inspiration for doing it my way.
The quality of the test cases was exceptional.
Maybe I’m special somehow! But I just want to call out the enormous chasm between what I saw of anthropic’s capability and what TFA says
> almost none are being exploited
Isn't the whole point of glasswing to patch stuff way before it can be exploited? If the patched code is distributed quickly- there's no opportunity (or incentive) for bad actors to craft and distribute an exploit. This reads like an attempt to spin them as not being "real" vulnerabilities.
Public datasets of CVEs being underwhelming doesn't mean much if all of the issues are in private company codebases that will never get a CVE number assigned and will never get a fancy blog post. You're never going to hear about them, and the people working on them probably can't tell you about them, but that doesn't mean they don't exist.
We're all worried about OSS having security issues because of how widely used things like PHP or curl are... but the same can be said about email providers, document collaboration SaaSes, payment processors, etc that millions of companies depend. Those companies will never be in datasets like this, and they'll never publicly disclose how many issues they found.
A good amount of the patches is straight garbage. It's not helped by the fact that a good amount (20~30%, maybe more) of the issues is also junk themselves.
I'll hopefully be able to share numbers (or data) after we're done with the batch.
That's consistent with my experience using them for coding, where even the best models mostly work by being persistently midwit (with infinite knowledge) more than individually brilliant.
One corollary of this is probably that any project that has had an army of actual monkeys pounding on it for years is likely more resistant to LLM attack than one that has not. Everyone is worrying about individual robot geniuses finding obscure vulnerabilities in Linux, PHP, Python, etc., but they should probably be more worried about the permutations of less-known software floating around their systems.
They turned frontier models loose on PHP, and the big one they found was based on a previously known logic flaw that was extremely difficult to exploit. Which makes sense: hence the need for frontier models.
And in the wild, while there have been many attempts and a few simple demo successes, the practical impact has seemed to be small, seemingly constrained by the length of the chain and the diversity of PHP configs.
In short, it was indeed a major vulnerability, but not magic (in the Arthur C Clarke sense).
I think ultimately the fear comes down to: do you believe that code can be secured. I recognize that there is probably no objective way to deductively prove it because of the Halting Problem etc. But if one believes code can be constructed to operate to spec, then there must be a limit to the damage an LLM can do, even a very smart one.
I think we are going through a phase where a lot of known triaged code shortcomings will get exposed and hopefully fixed. Sucks while it is happening. But not actually the first round of this type of evolution. And ultimately I think as before, we will come out the other side with more secure and durable technology.
Anthropic needs to teach their systems to propose a fix too. Detecting a coding problem and proposing a patch is what we should expect from a company with supposedly the best coding LLM.
The worst part is being thorough takes so much more work - they often do raise valid problems but you just can't set them in a loop because of this tendancy so you end up with way more work and hard questions
> The CVEs are a sliver of this year's total, almost none are being exploited, fixes have stalled while duplicates and withdrawals pile up, and the triage burden is shifting onto the open source maintainers Glasswing promised to help. The receipts keep coming in. They still don't reconcile.
> VulnCheck is helping organizations not just to solve the vulnerability prioritization challenge - we’re working to help equip any product manager, CSIRT/PSIRT or SecOps team and Threat Hunting team to get faster and more accurate with infinite efficiency using VulnCheck solutions.
The history of general-purpose massively parallel machines isn't good. From the Illiac IV to the Playstation 3, there's been dud after dud in this space. You can build them, but the users don't come. This sort of architecture is great if you have some specific problem that parallelizes, such as finite-element analysis or neural networks.
(I've used an NCube, and I kind of liked the Transputer concept. But both were dead ends.)
Pitchbook shows it as "Out of Business" since 2019.
In all seriousness congratulations on finding $30 million to launder and lose immediately. Hope your Porsche runs good.
Of course, the “don’t update after this firmware version” bit would always be the case (since any widely-distributed such vuln will be patched eventually), but deliberately moving the timeline to the left is sad.
(I say this as I am currently charging a cheap doorbell camera I bought, so that I can start dumping data from it and reverse engineer its protocol, solely so that I can lock it down to my local network...We needed something at the time, or I would have bought something more expensive that had an open protocol...)
> "single-handedly eviscerating DisplayLink's competitive advantage in this crowded market by educating our competitors and other third parties as to how we implement our proprietary technology"
Isn't that the purpose of a patent?
This is a clown show.
See Dan Gelbart's recent video on that very subject: https://youtu.be/v5d8nwgiSYI?si=iM9AFZiRTjxu4OuZ
DisplayLink on the driver side just compresses frames to send them over USB.
It would be interesting to analyse if Synaptics haven't stolen code from open source ffmpeg or VLC to do the compression.
“You are stealing our ideas! But we won’t tell you which ones unless you pay us”
In any other domain this would be called a protection racket.
if I patent a microwave and specify exactly how it works, that part can't be trade secret
BUT if my trade secret is on using ruby diamond for deluxe premium microwave lazor THAT isn't specified on the patent, well that be a trade secret
but trade secret CAN ONLY BE PUNISHED IF someone insider leaks the info -- not much can be done if some junk collector finds out about the ruby stuff
the tradeoff is that it becomes free eventually, unlike trade secrets
Good riddance if this is how OSS is treated by synaptics.
Most recent thunderbolt docks and usb4 docks have good display support, and fallback to DisplayPort alt mode if the host does not support tbt4. Which is much better supported over type-c. Intel and AMD upstream host support.
Obviously this is intended as a scare tactic, but, surely that could never hold up in court? Surely the burden of proof is on the owner of the patents to prove that someone's work is infringing, and you can't then say "We are charging the defendant to prove that we have a valid case against them." ?
There is no universe in which this is a reasonable response.
If one guy can reverse-engineer everything with an LLM and some free time, I'm pretty sure their competitors can as well, and they won't be doing it out in the open like this guy was...
https://lkml.rescloud.iu.edu/hypermail/linux/kernel/2610.1/1...
According to patent prosecution records, the independent claims for GB2484736 originally lacked any network transport limitations and were deemed entirely unpatentable against the prior art listed above.
To get the patent granted, DisplayLink’s attorneys amended the claims to specifically add delivery of the display data over a "general-purpose data network." The validity challenge relies on proving that adding a general-purpose transport layer (like USB or Ethernet) to existing image-compression methodologies was an obvious step and completely unoriginal in 2010, given the widespread existence of USB monitors and network-attached graphics at the time.