MurphyA/hacker-news huggingface dataset:
by rickdeckard | 2025-06-11 09:57:56+00:00
Because this strategy is not sustainable in the Android ecosystem, not even for Samsung.

Google applies different levers here:

1. Google is making your feature a commodity: Samsung is aware that Google plans to implement a native version of the feature, with or without Samsung. Google will make the feature available to ALL competitors of Samsung. Samsung get's the chance to shape it WITH Google or will later be forced to ensure compatibility with it (because it's not sustainable for Samsung to coexist with AND compete against an ecosystem used by ALL other Android vendors)

2. Google offers to take over some tasks: Google creates media attention for OS-Upgrades, creating pressure for Device-Vendors to adopt the new OS-version as soon as possible. The more a vendor deviates from the generic implementation, the more time & resources (and money) will be needed to adopt a new OS-version. So it's in the interest of Samsung to contribute as much of their fundamentals back upstream, so Google themselves takes care of maintaining it.

3. Google may make it mandatory at some point: The Android Compatibility Definition Document (CDD) defines the mandatory requirements for a device to be granted into the Android Ecosystem. Google is in control of this document and may at some point add specific behavior or features as a condition for Android compliance. This "Desktop Mode" has the potential to become the default behavior for Tablets, so Samsung may be required to adopt it for devices classified as Tablet by the CDD [0]

4. Google returns the favor: Samsung can trade collaboration on this feature for business opportunities with Google in other areas (i.e. Mixed Reality, B2B, Chromebooks,...), which potentially allows Samsung to be first in an entirely new market...

[0] https://source.android.com/docs/compatibility/16/android-16-...
by makeitdouble | 2025-06-11 09:58:03+00:00
It's a tougher sell when the younger generation gets the short end of the stick.

In a way that would be a good barometer of how that society thinks it's doing and how promising the younger generation sees its future, as prepared by their elders.

It's all the more interesting in countries where the population pyramid if fully reversed, and elders have way more power than the younger working class.
by IshKebab | 2025-06-11 09:58:22+00:00
The "unix philosophy" is a useless philosophy - perhaps worse than useless even - because "one thing" is not well defined, so in practice it adds nothing and just leads to arguments.

You could say that Eclipse does "one thing" - being an IDE platform - but I don't think anyone thinks that's what the Unix devs meant. Similarly I don't think they meant for people to write libraries that contain one 11-line function.

The actual advice should be something like "programs/libraries shouldn't try to do too much or too little". How do you know how much is too much or too little? Like so many programming guidelines the answer is you need taste and experience.
by motorest | 2025-06-11 10:00:44+00:00
> (...) but most of what they pay you for is dealing with internal (arguably mostly social) stuff.

Not really. They pay you to deliver something, but you also need to coordinate and interact with people. That involves coordinating and syncing.

There is absolutely no position or role whatsoever, either in a big corporation or small freelancer gig, that you do not need to coordinate and interact with people.

Pray tell, how do you expect to be paid while neither delivering results nor coordinating with anyone else?
by pajamasam | 2025-06-11 10:01:51+00:00
SEO spam was still easy enough to spot and skip through in search results before the masses of LLM-generated content took over.

They seem to generate extremely specific websites and content for every conceivable search phrase. I'm not even sure what their end goal is since they aren't even always riddled with affiliate links.

Sometimes I wonder if the AI companies are generating these low-quality search results to drive us to use their LLMs instead.
by leandro-sardi | 2025-06-11 10:01:58+00:00
Hey HN,

I’m a solo founder and just launched MassProspecting — a tool that scrapes real-time LinkedIn posts, enriches leads with verified emails, and uses GPT to write personalized outreach messages.

It started from my own pain: building cool stuff but struggling to get replies from cold emails. I wanted to contact people when they're actually talking about something relevant — not just pull static lists.

Here’s how it works:

- You define your target (job position, country, industry, company headcount)

- We scrape new LinkedIn posts with that context (using our own accounts).

- We enrich the author’s profile with email/phone.

GPT generates a message based on what they just posted

You get a downloadable CSV or can launch outreach directly

I’d love to hear your thoughts — especially if you’ve tried to scale B2B outreach before or have ideas on how to improve the workflow.

Open to feedback, questions, or critiques.

Thanks!
by achamian | 2025-06-11 10:03:51+00:00
Follow-up observation: The XP interaction pattern is crucial here.

When onboarding a friend, I used this framing: "Treat Waver/Maker/Checker like three intelligent interns on your team." This immediately shifted his mental model from "prompt engineering" to team collaboration. His first reaction revealed everything: "I don't like Checker - keeps raising objections." I explained that's literally Checker's job - like a good QA engineer finding bugs.

The parallel to XP practices became clear:

Waver explores the solution space (like brainstorming) Maker implements concrete solutions (like coding) Checker prevents mistakes (like code review/QA)

What makes this powerful: You're not optimizing prompts, you're managing a collaborative process. When you debate with Checker about which objections matter, Checker learns and adapts. Same context, same "prompt", totally different outcomes based on interaction quality.

When you ask Maker and Weaver to observe your conversation with Checker they notice how feedback is given and received. It is important to create an environment where "Feedback is a judgement free zone"

The resistance points are where breakthroughs happen. If you find yourself annoyed with one perspective, that's usually the signal to engage more deeply with its purpose, not bypass it.

[Related observation on how collaborative tone enables evolution: https://github.com/achamian/think-center-why-maybe/blob/main...]
by kotaKat | 2025-06-11 10:04:28+00:00
> What's stopping the GrapheneOS team from negotiating similar access contracts as OEM's enjoy?

Google themselves.

> Is there some kind of sorted history between Google and the GrapheneOS team of which I'm unaware?

https://www.androidauthority.com/google-android-development-...

Google is starting to move AOSP private if not in preparation to kill off the "OS" part of it.
by n4r9 | 2025-06-11 10:04:29+00:00
That's nonsense. A shot of spirits is one unit of alcohol. A pint of strong-ish beer like Stella Artois is 3 units. 550 calories is easily a dinner's worth for a woman of 70kg, or a man that's heavier but trying to gradually lose weight. Either of whom would normally not be too affected by two pints of Stella.
by joshstrange | 2025-06-11 10:05:36+00:00
4.5 years later and all the links to the previous parts of the series are dead. These are all internal links to their own site.

Now obviously my tiny blog of <30 posts is much easier to maintain but I’ve kept my links working for 13+ years even while moving from Wordpress->SSG(Hugo)->Ghost->Wordpress (and soon back to SSG). Yes, I enjoy the tech behind my blog more than blogging sometimes.

Yak Shaving aside, it’s always been important to maintain permanent URLs [0]. I find it absurd that larger publications just don’t care. Link rot out to the internet is one thing, internal link rot is just embarrassing.

[0] https://www.w3.org/Provider/Style/URI
Show HN: Prototype for tamper-proof LLM logs – looking for early feedback
by paulmbw | 2025-06-11 10:06:00+00:00
Hi HN,

I’ve been exploring how to keep every LLM prompt and response in an audit-ready form. In regulated environments (health, fintech, EU AI Act) examiners now ask for content-level logs that are:

- Immutable – no user can “UPDATE … WHERE id = …” the night before audit - Confidential – the logging vendor can’t read your data - Verifiable – a third party can prove nothing was altered or deleted

Cloud audit logs are great for API calls, but they don’t capture the text that left the model. Teams I spoke to were DIY-ing S3 buckets, object-lock settings and spreadsheet trackers = nightmare.

Here is a high-level overview of how the prototype works:

- Client encrypts every prompt/response with your cloud KMS key (BYOK). - Each log entry is written to an append-only store and linked so that any change breaks verification. - A public fingerprint of each batch is published so an auditor (or you) can confirm integrity without trusting the vendor. - When you need the content, you can decrypt a single row on demand under your own KMS permissions.

There are several reasons why I think this matters: regulations like HIPAA, SOC 2 CC7/CC8, and the draft EU AI Act explicitly call for tamper-evident, long-term storage of AI interactions. Furthermore, insider edits or accidental (even intentional) purges can happen if you host logs in S3 or in your DB, and implementing crypto + anchoring + KMS plumbing in-house is non-trivial for most startups.

What feature (or missing piece) would turn this prototype into a useful tool for your team? And how are you handling “prove-nothing-was-changed” today, if at all?

I'd also love to demo the prototype we've built so far, just book some time with me here: https://cal.com/traceprompt/traceprompt-intro?overlayCalenda...

Thanks!

Paul
by nosebear | 2025-06-11 10:06:01+00:00
>It's technically incorrect, but it's used for emphasis and hence politeness, and that's probably where your feeling comes from.

That's wrong, it's not technically incorrect. In fact before 2006 the only correct way to address someone personally in written form was to capitalize the Du / Sie / Ihr. Since then you are allowed to write it either way. I still use the capitalized form because I'm old and that's what I learned back in school.
by terhechte | 2025-06-11 10:07:38+00:00
The "it would have been different under Steve Jobs" trope is coming up every so often when Apple introduces a radical new feature. Oftentimes I don't agree but in this case I absolutely do. A huge amount of engineering to get these shader effects right, but the outcome will be that the platforms will look more like a fruit salad and less coherent. Companies that invested in React Native, Flutter, Tauri, or alternatives in the past years will not necessarily be willing to redo their whole app just so that the controls get the glass look. At the same time replicating this in every cross platform toolkit might be difficult, and so I think this will lead to many apps looking out of place which worsens the overall experience.
by cekci | 2025-06-11 10:08:21+00:00
Funding Proposal: Build Grin MultiSig & Earn a Bounty!

Calling all Rust devs! Help us bring MultiSig to Grin by contributing to grin-wallet. We’re breaking this into milestones with bounties—perfect for short-term wins or long-term collaboration.

What we need:

Rust implementation in grin-wallet Robust testing & documentation

*Why jump in?*

Earn bounties for milestones.

Grow with Grin as a contributor.
by jocaal | 2025-06-11 10:08:35+00:00
I'm a EE masters student and I also want to reinforce how inaccessible EE is and that I don't really recommend it as a hobby. EE is a very mature field and it's very math heavy for a reason. The second you move past the hobby boards, stuff becomes really difficult and really expensive really fast. If your end goal is to create toys for kids, then it's fine as a hobby. But without the formal training and lab access you are going to struggle to get past that point so it's pretty much impossible to turn the hobby into something more. Unlike software, where tinkering genuinely has the possibility of turning your side projects into careers. Hell, if you don't live in EE hotspot locations, I wouldn't even recommend it as a career anymore. Software is where it's at, even in the age of AI.
by npteljes | 2025-06-11 10:09:26+00:00
I really enjoyed this article, thanks for sharing!

It's a shame that OP didn't add a tracker to the pirate plea button. I would wager that he made practically zero sales from it - looking at how well donations seem to work in software development in general. I think that this is why microtransactions work well. They give away a nerfed version of the game for free, and after the player formed an attachment to it, the game can be upgraded for a price. In a way, this is a much more human design, than forking up the entire cost in advance.
by Bender | 2025-06-11 10:09:35+00:00
I've seen spikes but not to the point of being unusable if I only have uBlock installed. If I have both uBlock and NoScript installed but I allow javascript from YT and block it from google.com I get massive spikes due to some intermittent dependency on Google at about 60 seconds. It's hard to compare notes with others as they seem to do A/B testing on different groups of CIDR blocks. I stopped logging into YT ages ago.

This is on a Debian fork, Firefox ESR and regular Firefox. I've also never browsed the web from a phone. I am not a developer much less a JavaScript developer so I really do not understand what they are doing in the background. Rumble works fine for me, no spikes at all.
by jstummbillig | 2025-06-11 10:09:40+00:00
It's just a highly unoptimized space. There is very little market consolidation at this point, everyone is trying things out that lead to wildly different outcomes and processes and costs, even though in the end it's always just a bunch of utf-8 characters. o3 was probably just super expensive to run, and now, apparently, it's not anymore and can beat sonnet/opus 4 on pricing. It's fairly wild.
by ofalkaed | 2025-06-11 10:09:46+00:00
Timber framing uses dry wood as well, slightly different techniques but in the softwoods and some of the hardwoods its is not all that harder to work dry than green and in some ways easier. It depends on the tradition and location as to the exact process and technique, some preferred dry timbers, some green, some something between.

In US farm country it was common to fell the trees in late fall/early winter after the harvest was all taken care of and then leave the trees where they dropped until the ground froze. After the ground froze you haul them to the build site, much easier to drag logs on hard frozen ground than on soft wet ground. Then you would forget about them until after the spring planting is taken care of and build in the summer. Those big timbers would be far from dry but they will have lost a fair amount of weight and will be more stable which makes everything easier.
by WhyNotHugo | 2025-06-11 10:10:05+00:00
I do feel bad for the situation in which these guys have landed, but it’s also something that seemed inevitable long ago.

They focused on delivering a secure user-controlled operating system for phones. They used as a base an OS stewarded by an advertising and spyware company which couldn’t have values more directly opposed to theirs. They focused primarily on hardware by that same company. Other hardware was not supported in what sounds like “perfect being the enemy of good”. Eg: other devices might have been less suitable if you were targeted by a nation-state, but would have been superb for the 99%, and also avoided funding their opposition.

They let their antithesis have all the cards. It’s been an uphill battle which they’ve managed to push hard. But it’s hard to see a future, just as it’s always been hard to see a long term future for GrapheneOS.
by valenterry | 2025-06-11 10:10:11+00:00
Fair enough.

> Since then you are allowed to write it either way

Okay, my interpretation is that it doesn't really make sense within the language rules, so they changed it but allowed to use the old style to make the transition easier. ;-)

> I still use the capitalized form because I'm old and that's what I learned back in school.

Impossible to keep up with all the Rechtschreibreformen anyways.
by pbiggar | 2025-06-11 10:10:25+00:00
Extending strings is not a linear-time operation. Behind the scenes, the JS runtime allocates new memory for it. In the naive case, you start by allocating 1 byte, then when you append to it, you need 2 bytes. So you allocate a new string of 2 bytes, and copy the data in. Each new byte is a new allocation, and a new copy of the entire string. That's how it's quadratic.

In practice, memory allocators tend to double the size of an allocation like this, which is still quadratic.

In practice, JS runtimes also tend to use data structures like Ropes for strings to handle this sort of issue. That brings it down to linear time in practice (I think?)
by dkersten | 2025-06-11 10:10:26+00:00
On top of that, he only ran the script that NPM themselves provided him. Yes, the micro-package situation was absurd, but Azer Koçulu did nothing wrong. NPM did by forcibly taking his package, and then by providing him with scripts that were clearly unsafe to run. That Azer Koçulu got any blame for this is ridiculous.

Jon Schlinkert is a typical marketing A-hole. He should be banned from NPM and Github IMHO.
by bartread | 2025-06-11 10:10:34+00:00
> Not driven by logic, anger...

I don't know that I fully buy this either, at least not the anger part.

I can look back on all this with wry amusement nowadays but I remember it being pretty frustrating at the time.

It sort of felt like, well, either you knew what the impact of unpublishing all your packages would be and you did it anyway, which makes you kind of antisocial, or you didn't know what the impact would be but did it anyway, which makes you kind of a hothead. And in this latest piece Azer has admitted that he didn't understand what the impact would be so... y'know... I do wonder if anger was at least a small factor.

Regardless, it's pretty clear that npm bear a lot of the responsibility for what happened. It's also something that happened a very long time ago and, as I've already implied, is just a funny story nowadays, not something I can manage any ire towards Azer over.
by rolandog | 2025-06-11 10:11:55+00:00
If future LLM patterns mimic the other business models, 80% of the prompt will be spent preventing ad recommendations and the agent would in turn reluctantly respond but suggest that it is malicious to ask for that.

I'm really looking forward to something like a GNU GPT that tries to be as factual, unbiased, libre and open-source as possible (possibly built/trained with Guix OS so we can ensure byte-for-byte reproducibility).
Show HN: Chrome extension that helps you master any tools you touch
by NicholasCrumb | 2025-06-11 10:12:12+00:00
I’m more of a marketing / not very tech savvy kind of guy and have always been curious about testing tools that could make more productive.

Here's why I decided to build this extension:

1. I kept getting stuck on dumb stuff in different tools

2. Was wasting time learning out new tools

So I decided to build AppHug, a sidebar that sees your screen and gives you live, step-by-step guidance based on what you're trying to do.

Kind of like having ChatGPT inside your tools.

Been a great help for me in no-code tools, design platforms, ai automations tools,...

Would gladly take any feedback on it!!

Thanks :)
by dspillett | 2025-06-11 10:15:01+00:00
Invented might be a bit strong, but he is certainly the first written record of the word. Dress existed as a verb already, as did the generic reversing “un”, but before Shakespeare there is no evidence that they were used this way. Prior to that other words/phrases, which probably still exist in use today, were used instead. Perhaps “disrobe” though the OED lists the first reference to that as only a decade before Taming Of The Shrew (the first written use of undress) was published, so there are presumably other options that were in common use before both.

It is definitely valid to say he popularised the use of the word, which may have been being used informally in small pockets for some time before.
by benterix | 2025-06-11 10:15:08+00:00
I know people hate this but it shows a huge problem: innovation in operating system design. It's really a tough one. You really want the basic functionality to be very stable and unchanging to save yourself and others incompatibility pain over the next decades. OTOH, you need to release a new OS every now and again to show the markets that you are doing something. So they did a cosmetic upgrade like changing the graphic theme. Which, depending on your PoV, might be a very good thing.
by qsort | 2025-06-11 10:15:40+00:00
I feel like "do one thing and do it well" is an oversimplification:

(i) Make each program do one thing well. To do a new job, build afresh rather than complicate old programs by adding new "features".

(ii) Expect the output of every program to become the input to another, as yet unknown, program. Don't clutter output with extraneous information. Avoid stringently columnar or binary input formats. Don't insist on interactive input.

(iii) Design and build software, even operating systems, to be tried early, ideally within weeks. Don't hesitate to throw away the clumsy parts and rebuild them.

(iv) Use tools in preference to unskilled help to lighten a programming task, even if you have to detour to build the tools and expect to throw some of them out after you've finished using them

---

[1] https://archive.org/details/bstj57-6-1899/page/n3/mode/2up
by IsaacGichuru | 2025-06-11 10:15:51+00:00
SEEKING WORK | EMEA, CET Timezones | Remote

Technologies: TypeScript, Angular, ReactJS, Next.js, Django, Flask, Node.js, Express.js, Python, MySQL, PostgreSQL, SQLite, MongoDB, CouchDB, Firebase, REST APIs, GraphQL, Docker, AWS (EC2, S3, Lambda), Azure Cloud Services, Git, GitHub, GitLab, CI/CD, Nginx, WebSockets, JWT, OAuth, PyTest, Jest, Cypress, Agile, Scrum, Figma, Adobe XD, Tailwind CSS, Bootstrap, Linux, Bash scripting, Trello, JIRA

Résumé/CV: https://drive.google.com/file/d/1EBQpTT0m9SCfGxg4BKc7ZBxF3nM...

Email: isaacgwamugi@gmail.com

I have over 5 years of professional experience building, deploying, and maintaining scalable fullstack applications. My recent focus has been on frontend engineering and UX design, where I bring a user-first mindset and strong technical execution.

One of my most impactful accomplishments was designing, building, and maintaining a full-scale healthcare platform from scratch that now serves tens of thousands of users across Kenya with 99.9% uptime. My work included: Building a powerful admin dashboard, Implementing features like advanced search, invoice generation, billing, live location matching, and secure health data management compliant with international standards.

I’m available to start immediately, and ready to collaborate with teams or solo on impactful digital solutions.
by neomantra | 2025-06-11 10:16:13+00:00
He said he has all his YouTube content backed up, but besides this livelihood, most of his Google digital existence will be wiped without backup, including two decades of photos of loved ones.

tldr; is that his Google account (all services) is scheduled for deletion by Google with no explanation or recourse.

He thinks it might be because he stored some Spanish-language chatroom transcripts on his Google Drive as research for a story, without realizing the content, which might be hate speech.

But he's in the dystopia of getting his life erased and no way to fix it...

So he's shouting out for somebody from Google/Youtube, so if you that person reading this on HN, that's why the video exists.