MurphyA/hacker-news huggingface dataset:
by nulld3v | 2025-05-28 06:14:30+00:00
HEVC/H.265 and VP9 can both also operate in lossless mode. In my testing they achieve compression ratios that ffv1 and huffyuv cannot come close to touching (not all that surprising given how old ffv1 and huffyuv are).

Ffv1 is much easier to work with compared to HEVC and VP9 though, probably thanks to it's deep integration with ffmpeg. By comparison, working with HEVC was hell on earth!

I spent like a week figuring out how to stuff JPEG sequences into HEVC files without losing colorspace and color profile information. Even JPEGs alone were horrible to work with, my understanding is they encode image data in the YUV444P colorspace, but every program works with them in the RGB colorspace. The conversion between YUV444P <-> RGB is lossy and every program does the conversion slightly differently. So if I ever accidentally triggered this conversion at any point, my archival was no longer bit-perfect.

And then to check your results, you obviously can't convert back to JPEGs, I think I ended up encoding to TIFF after having failed with JXL.

Code here if anybody else wants to try replicating it (good luck, you'll need it): https://gist.github.com/null-dev/ebd2f8b23c3e5066a48976c7308...

Converting lossy JPEGs to lossless HEVC might seem wasteful, but the space saved by intra-frame compression dwarfs the space saved by lossy encoding.
by thaumasiotes | 2025-05-28 06:14:31+00:00
It wouldn't really matter; the image includes a lot of structure that isn't present in the text that KaTeX provides. A text-only screen reader will never produce anything but gibberish if you feed it KaTeX output.

KaTeX will also style the text so that it visually resembles the image, stopping this problem from occurring for non-blind readers. You could have a screen reader that parsed all of the layout, but it seems like you might just as well OCR the image at that point.
by runeks | 2025-05-28 06:14:42+00:00
With proof-of-stake, an attacker compromising a majority of private keys results in the attacker taking control of the blockchain. The attacker could publish only empty blocks using this stake majority, and there'd be no way to distinguish these malicious valid blocks from actually useful blocks.

This makes proof-of-stake inherently less secure than proof-of-work because for PoW blockchains, consensus is not affected by compromising private keys.
by leoedin | 2025-05-28 06:15:34+00:00
A longer cable won't just catch fire, because the power dissipation per unit of length is the same regardless of overall length. Imagine the most extreme case - a cable so long the voltage difference is 0V at the end. It's basically just a very long resistor dissipating 60W. But each meter of cable will be dissipating the same power as every other PoE setup.

Looping the cable or putting it in a confined space could cause issues. The cable could then catch fire even though it appeared to be operating normally to the PoE controller.
by johnisgood | 2025-05-28 06:17:40+00:00
Oh, I think I came across that (I think it was PayPal? I actually don't know because I rarely see any on PayPal) before. It worked for me, but I do not have Vulkan, I believe. So I am not sure what happened in your case. You could call up their support (I did a few times before because I got locked out). This was a few months ago, I could get to a human pretty quickly (at least at that time). It was a sweet lady, and she spoke English (only). My problem was resolved within minutes. That said, in your case they would probably tell you to try a different browser, or even a different IP address (VPNs may have an issue).
by potholereseller | 2025-05-28 06:19:18+00:00
> doing this without pay

No, you got paid in vibes.

Never. Accept. Vibes.

Vibes are for losers. Refuse to be treated like a loser.

Reject vibes; demand money.

It is always a mistake to do un-paid work for an organization that wants turn a profit from your work. They will always suck you dry, as if you are a fire hydrant and they are a blackhole.

> Planning on letting him know I'm out near the end of this week.

Stand up for yourself. Stop working immediately and tell them that you won't work for free any more. If they want further work, they should start paying immediately. And consider demanding they pay for work already done.

Your time is valuable; you can't get any of it back. Only genuinely charitable organizations and in-need individuals should ever get free work; everyone else must pay for work.

> Co-founder didn't understand why I wasn't interested working without salary anymore.

This is methhead logic on his part. Again, reject vibes; demand money. Methheads live on vibes, especially the vibes from stimulants.

> most of my friends make way more money than me or have families

Again, reject vibes. You see their vibes, but are you so sure that they are actually doing well overall? They could be in debt up to their eye-balls; they could have terrible family situations; they could be totally burned-out from working 80-hour weeks. A lot of people put out good vibes to try to make themselves feel better about a bad situation; vibes can't fix a broken home, a terrible job, or a bad financial decisions.

A lot of people have started families/careers later in life. Now is the time to figure out why you want money/family/whatever. Working to feed your family is rewarding; working just to work is self-harm. Starting a family in order to shower them with love is rewarding; starting a family because it's a milestone is egotistical.

> Anyone else pivot away from tech and still make half-decent income?

Reject vibes; find a boring job. Research the sort of jobs that nobody wants to work, but which pay well. Those jobe have no vibes to offer, so they attract few candidates. A SWE can find good work doing boring jobs, because SWEs focus on details; and details are the antidote to vibes.
Show HN: Stop Babysitting Lovable
by nomangul | 2025-05-28 06:20:21+00:00
I got sick of staring at Lovable like it was gonna finish faster if I believed hard enough.

So I built a Chrome extension with a friend (@jason zook) to fix it.

It’s called Lovable Buddy, and it does one thing: lets you STOP babysitting AI.

It’s a lil floating widget that: - Tells you when Lovable is still working - Tells you when it’s done

Yes, it works in background tabs. Yes, it gives you desktop notifications too. Yes, you can move it wherever you want. Yes, it makes multitasking WAY less stupid.

And yes, we are charging $9 for it, because your time (and our time to create it) is worth wayyy more than that.

Learn: http://lovablebuddy.com Get it: http://bit.ly/lovablebuddy

And yes, we use it ourselves. Constantly. That’s why we built it.
Show HN: A simple, useful, powerful bookmark manager or simple note-taking app
by lilerjee | 2025-05-28 06:20:55+00:00
Metaessen is the practical, safe and concise resource manager, helping you focus on and manage the most important parts of resources, not be distracted by the unnecessary, grasp the big picture and essence, save time and improve productivity.

It can be used as a better bookmark manager or simple note-taking app.

The main purpose:

Focus on and manage the most important parts of resources in order to get, understand, organize, and use resources faster and better.

Use cases:

- Manage bookmarks

- Cleanse bookmarks

- Collect resources

- Write notes, articles, ideas, pieces of text, etc.

- Record What you see, hear and think - Manage tasks

- Record, Observe and Study the development and changes of things

- You can also develop other use cases or ways to use

Main features:

- Focus on and manage the most important parts of resources

Just focus on the most important parts, and remove all trivialities, superfluities, complexities, cumbersomeness, unnecessaryness and noise. Keep it practical, valuable, simple, clean and concise.

- Use Innovative Data Model to Simulate the Real World

The "Resource-Instance-System" data model is more consistent with the real world and actual situations, and can manage your various resources more practically, flexibly, efficiently and conveniently.

- Pay great attention to and protect user data security and privacy

Never sell, transfer, trade or share your data with third parties. No ads, No trackers (Google Analytics, etc.). No data censorship or filtering.

- Flexible, practical and efficient data organization and management method

Use systems (like folders), instances (like files or snapshots), and keywords (like tags) to organize resources. Various resources can be effectively combined into the desired useful information hierarchy or chain. Search and filter resources by keywords.

- Multiple use cases

- Simple, accurate, practical, efficient, responsive user interface and interaction

Cross-platform, responsive to almost all sizes of screens. Access and manage your various resources from multiple devices anytime, anywhere. Pay attention to every detail of user interface and interaction.

- Use the common but innovative bookmark backup file formats for data import and export

Using the common bookmark backup file formats (HTML or JSON), you can import your browser's bookmarks and also export all or part of your data to your browser (such as Firefox, Chrome) or other bookmark manager, note-taking software.

Please refer to the website: https://metaessen.com or the docs: https://metaessen.com/docs/

If you have any question, please ask here or contact me: liler@metaessen.com
by veqq | 2025-05-28 06:25:18+00:00
> grammatically incorrect

And he said to them, starting sentences with and is fine and normal. Haven't you read e.g. the bible where it occurs constantly? https://en.wiktionary.org/wiki/and#Usage_notes

Further, sentence (or clause) initial "and" can means if/as though, also existing in other Germanic languages:

> wir werden siegen, und wenn wir sterben müssen
by fredoralive | 2025-05-28 06:26:44+00:00
The 512x384 models are Macintosh LC adjacent, so the original LC monitor (the LC itself can do 640x480), or the Colour Classics. AFAIK it was partly in order to making the LC work better with the Apple IIe card (although the IIe software uses a 560x384 mode).

A Hercules card, whilst nice does suffer from the same non-square pixels issue as the Lisa, so not as nice for creating a GUI.
by echelon | 2025-05-28 06:26:45+00:00
You can set permissions on writes.

Optional, per-directory OWNERS files are common, and most VCS frontends (Github, Bitbucket, etc.) can be configured to prevent merges without approval from the owning team(s) or DRI(s).

PRs that intersect multiple teams' ownership would require handoff of everyone impacted. So a team updating the company-wide "requests library" (or an equivalent change), with a wide blast radius, would be notifying everyone impacted and getting their buy-in.
by makeitdouble | 2025-05-28 06:26:59+00:00
Is your underlying assumption that the organization doesn't want to go one way or the other in the first place and is nudged by the technical choice afterwards ?

I think most of the time the philosophical decision (more shared parts or better separation) is made before deciding how you'll deal with the repos.

Now, if an org changes direction mid-way, the handling of the code can still be adapted without fundamentally switching the repo structure. Many orgs are multi-repo but their engineers have access to almost all of the code, and monorepo teams can still have strong isolation of what they're doing, up to having different CI rules and deployment management.
by qaz14 | 2025-05-28 06:27:06+00:00
Dunno if this helps anyone but thought I'd share the thinking behind a new tactic we are using, in case it’s useful for others building who are working with creators to help amplify their marketing.

Our customers ARE creators—Podcasters, YouTubers, Musicians, Comedians, Authors etc—so it felt logical to treat them as true partners, not just marketing channels. We decided to set up a “Board of Creators” program where creators can earn equity in return for:

- Advising on product direction; - Being regular users (with zero platform fees forever) - Champion the product to other creators (for which we will also pay them a referral)

We’re hoping this approach leads to some early product advocates that will help accelerate our growth. I have no idea (yet) as to the quality or reach, but the response so far on LI has been pretty good (using the good ol' comment for more info approach to ensure we land in more feeds).

I would think this doesn't have to be just for creator businesses either, it could work more broadly for anyone using creators in their marketing.

This is early for us, so we’re keen to see how it plays out—and curious if others have tried similar models.
by Terr_ | 2025-05-28 06:28:00+00:00
What kinds of statistics can we watch that might illustrate the brain-drain from these policies, on various timelines?

Some of it is going to be people who don't even bother to apply anymore, because nobody wants to study in a place where you get arbitrarily black-bagged halfway through your degree by thugs filling an arbitrary quota.

I imagine there are also some students will be out there who really don't use public social media all that much, and the lack of activity will falsely be taken a sign of concealment...
by throwaway290 | 2025-05-28 06:28:30+00:00
LLM don't "know" anything. It's a program. But those programs get fed so many (mostly stolen) essays and songs that it outputs a convincing essay or song.

So the end result is this. you don't need to know how to write an essay but you get an essay written for you. It's very different from using calculator and knowing math or using ProTools and knowing how to make a song.
by Michelangelo11 | 2025-05-28 06:31:00+00:00
> Need to renew a passport? Your AI assistant can handle it. Want to resolve a billing dispute? Your bot speaks the call center’s language better than you ever could. These systems aren’t speculative—they’re already outperforming the humans they represent in key tasks.

This is all true, but I'm disappointed that TFA doesn't address the implication -- namely, the massive job destruction. Routine service jobs like those described employ probably tens of millions worldwide and are a stepping stone into the middle class, and I think AI razing them wholesale is a tragedy.

In general, the impact of AI at the societal level looks like a force to return us to what most societies everywhere have been like: a small layer of owners at the top, a vast block of interchangeable unskilled laborers at the bottom, and an (ever-shrinking) sliver of clerks and skilled laborers sandwiched between. Broad middle classes, created by the Industrial Revolution, then end up as a blip in the overall course of history. That outcome would be one of the most destructive things I can imagine.
by tsimionescu | 2025-05-28 06:31:03+00:00
The difference here is that STS-1 achieved orbit and flew 37 times around the earth, while Starship flight 1 didn't even explode correctly after failing to keep its designated path. Starship has yet to achieve orbit, in fact, in 2025 - passing the 13 year mark of STS-1.

And note that the actual shuttle that was launched in 1981, the Columbia, went on to conduct 27 more successful missions (until its tragic end many years later). So it was already successfully reusable from its first test flight (with the known caveats around cost of refurbishment).
by bawolff | 2025-05-28 06:31:11+00:00
Instead, it can be attacked simply by purchasing a lot of compute.

For a smaller chain, purchasing a lot of compute sounds easier than hacking everyone's keys. Not to mention if you can hack someone's private key, surely you can hack their server farm

(Fwiw, i think both have a similar level of risk, its just coming from different threats)
by johnisgood | 2025-05-28 06:31:24+00:00
But why can we not hold humans responsible in the case of LLM? You do have to go out of your way to do all of these things with an LLM. And it is the human that does it. It is the humans that give it the permission to act on their behalf. We can definitely hold humans responsible. The question is: are we going to?
by staunton | 2025-05-28 06:34:49+00:00
The gamma burst probability is something we can quantify (it's tiny). (And it's something we can do absolutely nothing about, so it's not worth worrying about).

Nobody can predict how soon a technology will plateau. People make predictions based on insane hot takes like "I pray to our new overloards who will make me immortal" and "there's nothing new under the sun, everything is just marketing"...

There might be the next AI winter starting starting next year, AI might wipe out humanity in our lifetime, even both of those might happen. Both very unlikely (qualitatively) ends of a huge spectrum.

That's not to say that we "don't know anything and thus give up talking about it". Otherwise I wouldn't participate in this discussion and I hope you wouldn't either if you didn't expect to sometimes learn something or be confronted with a new idea.

I just find both attitudes "it's making us immortal" as well as "I'm so experienced, I know that no new technology ever lives up to expectations and can mock people who admit they don't know that" unproductive. You don't know. Most technologies don't live up to expectations, a few work out even much better than expected. I'm sure before the Lee Sedol match, you thought to yourself "right, so it's going to win this and then plateau exactly a decade later"?
by Epa095 | 2025-05-28 06:34:57+00:00
So, how does that relate to this quote from the article?

>ty, on the other hand, follows a different mantra: the gradual guarantee. The principal idea is that in a well-typed program, removing a type annotation should not cause a type error. In other words: you shouldn’t need to add new types to working code to resolve type errors.

It seems like `ty`'s current behaviour is compatible with this, but changing it won't (unless it will just be impossible to type a list of different types).
by hardwaresofton | 2025-05-28 06:37:19+00:00
Hey sounds like youre having an incredibly difficult time, I hope things turn sooner rather than later.

> language, I know the linux shell very well, I use git, I consider myself a Python expert

It sounds like applying to every python job you can find is probably your best bet.

No job too low, no company too boring. Hope you find something
Show HN: Is Manual Social Posting Tanking Your Startup's Reach and Sanity?
by officialvikram | 2025-05-28 06:39:54+00:00
Hey HN,

Vikram here. We all know social media is a necessary beast for getting a startup off the ground. But let's be honest, manually managing and scheduling posts across multiple platforms can feel like a one-way ticket to burnout, especially when you're bootstrapped and every minute (and dollar) counts. I've been there, wrestling with inconsistent posting and the fear of becoming invisible.

That's why I built Postaler.co (https://postaler.co).

It's a straightforward, lean SaaS designed to help you manage and schedule your content efficiently across various social platforms without the hefty price tag or overwhelming features of bigger tools. My goal, as a fellow Micro SaaS builder, was to solve a very specific, high-friction problem: making consistent social media output achievable and affordable for busy founders and lean teams.

Why Postaler.co might be for your startup:

Actually Affordable: This isn't another tool with "startup-friendly" pricing that quickly balloons. It's priced with early-stage and bootstrapped realities in mind. My focus is on delivering value without breaking your (our!) tight budgets. Focus on Core Needs: We're not trying to be an all-in-one marketing behemoth. Postaler.co is about solid, reliable scheduling and multi-platform management to save you precious time and mental energy. Built by a Bootstrapper for Bootstrappers: I understand the grind. This tool was born from my own frustration with existing solutions that were either too complex, too expensive, or both for a lean operation. I'm launching Postaler.co and am specifically looking for early startup users to jump on board. Your feedback will be absolutely invaluable in shaping its direction and ensuring it truly solves the problems we face. If you're tired of the social media juggling act, worried about your inconsistent online presence, and looking for a simple, cost-effective solution, I'd be thrilled for you to try it out.

Happy to answer any questions and genuinely eager to hear your thoughts – the good, the bad, and the brutally honest HN feedback are all welcome!

Cheers, Vikram (Founder, Postaler.co)
by thaumasiotes | 2025-05-28 06:40:02+00:00
> Since others normally write his lines, do you grouse that you don't know who wrote Colbert's commencement speech?

> If you think he wrote it, do you wonder why he wrote his own speech instead of his writers?

No, I think Stephen Colbert is viewed as an interesting person whose life many people would like to emulate. Which would mean the answer to "who got invited" was the actor and not the character.

But none of that applies to Kermit the Frog; he's not even alive. I don't think Matt Vogel is seen that way.

Here, it appears that the character was invited, but without the ability to speak. How does that make sense?
by Pawka | 2025-05-28 06:41:26+00:00
It depends on the VCS you use. I don't know any ways to manage read permissions, such as allowing a person to checkout one directory but not another, though you can do that per branch on git.

But there are many ways to manage write permissions - limit the directories to which engineers are allowed to push code. E.g. if you use Git, this can be done with Gitolite, which is a popular hosting server.

Gitolite has very flexible hooks support, especially with so-called "Virtual Refs" (or VREFs)[1]. It is out of the box and has support to manage write permissions per write path [2]. You can go even further and use your own custom binary for VREF to "decide" if a user is allowed to push certain changes. One possible option - read incoming changed files, read metainformation from the repository itself (e.g., CODEOWNERS file at the root of the repo), and decide if push should be accepted. GitHub has CODEOWNERS [3], which behaves similarly.

[1]: https://gitolite.com/gitolite/cookbook.html#vrefs [2]: https://gitolite.com/gitolite/vref.html#quick-introexample [3]: https://docs.github.com/en/repositories/managing-your-reposi...
by timschmidt | 2025-05-28 06:41:36+00:00
> with the known caveats around cost of refurbishment

Only the orbiter was refurbishable (not fully and rapidly reusable like Starship - booster reuse was demonstrated today), which took 6 months, and cost $2 Billion per launch.

The whole Starship development program is slated to cost about as much as 5 Shuttle launches.
by nyanpasu64 | 2025-05-28 06:41:58+00:00
I looked up my brightness measurements of a Gateway VX720 VGA monitor (like Diamond Pro 710), and it seems the blue and green phosphors decay to 50% brightness in under 30 microseconds while red stays bright for 300 microseconds. I didn't measure how long it took for them to go to near-black levels. Sadly I never took measurements of my Trinitron TV when I still had it. All in all the results are inconclusive.
by timschmidt | 2025-05-28 06:42:21+00:00
Yeah, well, apparently neither was Shuttle. RIP Challenger and Columbia and crews.

No fatalities with Dragon yet, thankfully. It seems to me that Dragon and Shuttle are much more directly comparable. Falcon 9 throws away it's second stage, which is still less than Shuttle did. And Dragon requires a similar level of refurbishment to Shuttle. Shuttle could carry 27,000kg to LEO whereas Falcon 9 can carry 22,800kg to LEO.

Starship is slated for 200,000kg to LEO. It's in an entirely different class.

The aspect of Starship I find craziest - it's lack of launch abort system at this stage of development - was a problem Shuttle suffered it's whole life. And Shuttle didn't have the engine redundancy of Starship or Falcon 9.