skysight-inc/HackerNews huggingface dataset:
Does the author not know what a "leaky abstraction" is? The first time they referred to memory leaks I thought is a clever joke nested in a jab a hypothetical coder who didn't know, but then in the end they double down in a clearly non-joking way. Then even make a chart showing that calling a normal function from an async function is trivial, that is the opposite of a leaky abstraction.

An abstraction is a "leaky abstraction" when it forces some external condition or behavior onto code (ex: calling code that uses the network doesn't work when the network is disconnected). In this case the hurdles of calling async code from normal code, and this author tries to hand waive that with talk of dependencies.

There are real benefit and drawbacks to async code and styles. Even if I don't think it is a good abstraction I want to discuss it on the real engineering terms of its actual merits and drawbacks. This article is talking past the engineering decisions and seems like it didn't mean to.

maybe I am just being a pedantic jerk.
And last I heard still has show-stopping performance bugs affecting eg Unity web target.
What ISP is that? Name and shame. I'm Australian and want to know to avoid them.
You can do the same with Bitwarden by having the vault in your local computer.
I stick to adding entries on my desktop and distributing copies to my clients. Its better for me to limit syncing between devices.
This is fair, though in my answer, I wasn't answering the question from the perspective of applicability for a general audience.

For a general audience, even Bitwarden doesn't pass the "grandma check". If you've used Bitwarden for a while you have probably been met with a stern warning about "KDF Iterations too low".

So I pitched the answer assuming "able to use Bitwarden" as a base level of tech savvy.

Also, seeing as I am on HN, I assumed the following:

1. Security matters, even if it comes at a slight cost in convenience

2. User can figure out their own syncing mechanism
one word, exceptional. Kudos for just thinking that. Doom is a classic and deserves this.
I hope no one calls him "pedo-guy" and puts his life at more risk.

As usual he has a grossly inflated opinion about how much people actually care about him or what he says.
Ongoing thread that points to gasp the actual GitHub issue and not some rando site's take https://news.ycombinator.com/item?id=41893994
EDU DIY Labor
No LLM suggested to first build a table of primes for faster factorization.
108 is too small a number for the test.
How long will each program hang to give results for, say, the prime number 1599999983:
[1,1599999983,1]
I blame this lack of meaning on the overpaid Memetics Engineers who have added the word to just about every possible discipline in a vain attempt to make those disciplines seem important and dignified.
> I really wish JDBC would create something like "executeAsync" that returns a CompletableFuture or something similar.

Relevant: https://github.com/jasync-sql/jasync-sql#getting-started
The concept you are describing at Google is the "terminal level" for Software Engineers.

At Google, the vast majority of new college hires would begin as Software Engineers at Tech Level 3 (L3), where Tech Level 5 is "Senior Software Engineer." Level 6 is "Staff."

The terminal Level concept was one where all Software Engineers are expected to perform in an upward trajectory toward the standards of the next Tech Level, until reaching Tech Level 5. I.e. Software Engineers are expected to be promotable up to Level 5, and after reaching L5, there is no longer an "up or out" expectation. L5 SWEs are not expected to become Staff Engineers.

Today, the Terminal Level for Google SWEs is now Level 4.

The median Google SWE historically was around L4, and your average Google SWE would be a seasoned L4, potentially ready for a promotion to L5 in the next few promotion cycles.

The idea of a "principal" Software engineer is Level equivalent to a Director (Level 8) of which despite there being many at Google/Alphabet, as a percentage of the total population it is quite small.
> message history functionality is too restrictive for me.

At least a way you can get around this is to do the backing up by desktop. I'm assuming you're on an iPhone because Android supports backup.

If you are Android, see Molly: https://github.com/mollyim/mollyim-android

> Telegram strikes a good balance, and wins at the UI/UX game.

Telegram gets the "lol" because it's not default E2EE. They advertise themselves as E2EE but most people are not using this feature because it's opt in. If you're going to seriously position yourself as a security app, the defaults have to be secure. It's the bare minimum.

And E2EE isn't even available for group chats... WhatsApp is more secure (telegram also gathers metadata)...

I do think signal has stagnated while there are many things that could really be improved, including low hanging fruit like just being able to search for stickers (people do in fact care). But for the most part, I'm not sure there's anything major missing. It seems like we're willing to pay high costs to avoid small thorns. But I guess it's better to have a rock on your shoulders than a needle in your finger.
I've used this long-running fork and been pleased, and it's on F-Droid. https://github.com/Catfriend1/syncthing-android
Yeah I've heard that exact phrase. I was told I was already at the top of the band for my title (Senior Engineer haha) and not eligible for the annual salary increase. Then six months later laid off.
Why do dynamic address allocations matter? Most IPv4 consumer WAN addresses are also dynamic.

I’m asking, because I’m an advocate of having your gateway advertise a separate, stable ULA /64 in conjunction with the globally-routable dynamic /64.

This gives you a stable set of addressable LAN IPs, and you can usually ignore the dynamic globally routable IPs.

Granted this won’t work for everyone, but if dynamic global addresses are an issue, you should be requesting a plan that supports a static delegation from your ISP anyway.
Six top Alzheimer's researchers accused of fraud
These demonstrative particles themselves don't have gender since they are not nouns, but they have a gender-based variety, and must pair correctly with the nouns by gender.

It's similar to la and le in French. You cannot say "Vive le France"; it has t obe "la France".

They are used as helpers in communicating the gender of a noun. If we say "ten stôl", it reaffirms that the noun is masculine. "tá stôl" is ungrammatical.

Other words are like this. E.g. interrogative wh- words: "ktorý muž?" (which man?) "ktorá žena?" (which woman?)
Shameless plug: A few months ago I wrote a blog post [1] about integrating PasswordStore + GnuPG + TouchID on MacBook, and used that to automate my work VPN (Cisco AnyConnect) auto-connection [2], hence avoiding the need to interact with a very bad UI that is AnyConnect.

Hopefully others find it useful.

[1]: https://gurjeet.singh.im/blog/passwordstore+gnupg+touchid

[2]: https://gurjeet.singh.im/blog/cisco-anyconnect-vpn-automatio...
Indonesia was a democracy in name only. It had no tradition of peaceful transition of power. Sukarno became an increasingly authoritarian strongman, who tried to balance power between various anti-democratic factions.
Furries claim to be going to Bluesky every month, then they come back to Twitter because that’s where everyone else is.

It took forever for Bluesky to add video support as well which held it back for ages.
It's really just an Android tablet with some hardware and software that's there to facilitate reading and reduced eye strain. It's nothing entirely revolutionary but I find the price point to be the feature I like the most. Having spent $1000s on Galaxy Tabs over the years it's amazing the value for money the 11 model is.
> catching the low-hanging fruit would at least probably handle any potential legal liability?

Actually No.
It take 5 minutes to create a script to randomize a password, encrypt and upload.

Abusers have been doing the same for 20+ years and it is very effective.
Robo..jari toco123
It’s a little different though in that rather than an IP having a bad reputation, it’s usually a /64. That’s how I have seen IPv6 reputation managed since it’s a common network slice & NAT is not really used anymore.
I fully agree but can't help but think about the SWEs writing code for Tesla et al
One of my friends decided to change his job title from "technical project manager" to "solutions architect" for the sole purpose of sales. He and the boss agreed that it sounded more impressive to the clients we were going after.

Exact same day-to-day work. Exact same responsibilities and pay. Everyone within the company agreed that it was a complete joke. And yet, we still did it.
> differentiate between someone who picked up Python for a weekend project, and someone with 30 years experience with real-world systems

Why do you need credentials to differentiate these two?
I made a similar thing: https://waste.st/waste.1

If you run curl waste.st you also get the “manpage”

The goal was to make it do uploads without a ton of frameworks. The front page is around one request under 20K. It also has a special emoji url: https://[waste bin emoji].st that HN doesn’t support.
"How much do you earn right now?"

With all due respect, that is none of your damn business

"Interesting. I have no more questions"
One way to get out of this is to have a title wildly out of range relative to your compensation.

If you're title is "engineer" and you're overseeing a technical team and participate in the architectural decision for your company, anyone dealing with your salary (including when moving jobs) will need to actually look at your job instead of just the title.

In the same vein I had a coworker request "staff” as title and we were small enough that it didn't matter.
Worth mentioning that staying in line with other companies is critical for company sponsored immigration in the US. If an individual is paid too differently from their title at other companies, their visa might be denied for being unfair to citizens looking for similar positions. It could be similarly unfair if they're paid differently from citizens with the same title within your company. Hence everyone at your company needs salaries that align with industry titles, or you risk not being able to get visas for international employees.
STUN also isn’t guaranteed if the router is strict. IPv6 removes a lot of these unknown and strange ways that IPv4 infrastructure can break things.
Unruh's first page and a half alone are worth the click and motivate settling in for a long read.

(It's also a relief to see that eminent names in the field make a lot of typos.)
They have massively nerfed Copilot. I'm keeping my subscription for a couple more months but at this point, it has the same intelligence as the llma3.2 which I can run on my laptop.
"¿Esos son Reebok, o son Nike?" [0]

[0] https://youtube.com/watch?v=jd4TsegK9fQ
There are certainly research questions and cost questions and practicality and subsetting and whatnot. Addressed by some ideas and not by others.

What there isn't is a currently maintained and advertised client and plan. That I can find. Clunky or not, incomplete or not.

There are other systems that have a rough plan for duplication and local copy and backup. You can easily contribute to them, run them, or make local copies. But not IA. (I mean you can try and cook up your own duplication method. And you can use a personal solution to mirror locally everything you visit and such.) No duplication or backup client or plan. No sister mirrored institution that you might fund. Nothing.
One of the best things about postgresql is the documentation. They document not only the features, but the constraints and considerations for using it and why they exist.

So from reading https://www.postgresql.org/docs/17/transaction-iso.html#XACT... we can tell that using serializable transactions only locks data actually used.
Most industrialized countries do offer single payer healthcare to taxpaying foreigners, perhaps after a reasonable period of time.
That's totally fair and I actually do agree.

I'm willing to give up convenience for security. But I do like to stress that we should try to have both as much as possible. It's a thing that is often forgotten and many times matters.

I'd definitely agree that it's not a big issue here, as password managers are more personal, though my general frustration is with things like communication where I need the other person to also be willing to make the same compromises. Though back with password managers, I do need things that at least pass the parent test (retiree but not old folks home) because their information leakage leads to my leakage regardless of my actions. So I still do think it's worth turning up the heat to push things this way.

As a different point (which I'm not trying to argue but point out) is that we also need to recognize momentum and the challenges it brings, especially to the less tech savvy. We can jump ship easily when tides change because we know how to sail on our own, but what about those that don't? I am sympathetic to those who think we just jump ship to ship because even when they follow when they look back it looks like everyone is fine. I think it's a really unfortunate issue and I think a much more difficult challenge to solve. I'm not sure if anyone has any ideas. OSS only makes it easy to jump ship, but it doesn't reduce the need to jump in the first place
Collecto: An open-source, self-hosted, lightweight, email collection service
I second this request. Any publicly indexable channel would be fine.

I think Matrix is not publicly indexable unless the channel is unencrypted and set to public.
The argument wouldn't be "better at" but simply "more".

Sensor platforms deployed at scale, that you have the right to take data from, are difficult to replicate.
Because unlike in most actual engineering disciplines software developers generally aren't held particularly liable for the failures that their bad engineering causes, whereas people who build faulty bridges or airplanes don't have that luxury.

Software has built a lot of modern toys but it still plays a relatively limited role in the world of atoms rather than bits, but I suspect the value of credentials is going to appreciate as that changes over the next few decades.
Renesas is rocking after it's many many acquisitions & mergers. Very nice Cortex-M85 here!

I wish they'd throw some of the Siligo GreenPAKs on this thing. Rp2040 and rp2350 Pico and pico2 cores have those great Programmable Input Output units, which is so great for offloading the CPU. Silego's GreenPAK was a very capable/interesting mixed signal fpga that would be awesome to see as a competitor, could let the CPU sleep more or be less congested.
And, again, issue threads are only helpful if the people corresponding in them are good communicators who put in the work to leave a legible record of what happened.

Many Github issue threads that I read are incomprehensible. The thread is not where the story is (it's in the memories of the people involved). Explaining is work. This is why they make kids write reports as assignments in school.
Even if it were, still no one seems accountable to fix it.
Maybe we should be concerned about more than just direct loss of life? What about data leaks, for example? It might be nice if there were some risk that software engineers could lose their license over eg. plaintext passwords, or be protected by a governing body if they need to take a professional ethics stand against their employer.
For me it ia around 60per and it is really bad. I would go to depression if i was not able to scroll and get that dopamine. Went to therapy and now i think it is in control but sometimes i feel like i need that scrolling because i am not able to interact with my friends on a social platform. Trying my best to get rid of it permanently by deleting the accounts. And working on personal growth.
In the past two days, the official Syncthing Android client has been discontinued, making the use of KeePass harder. Bitwarden has been trying to move away from a fully FOSS system. And now this?
GM went bankrupt. Ford would have without government intervention. Each have had periods of profitability but they weren't ever anything like microsoft/google etc. Ford has underperformed the stock market average since it went public like 70 odd years ago. GM got so big in the first place via acquisitions, not because the business of cars lent itself to a dominant player.

Huge by itself isn't the same as huge winner.
This seems to happen more and more often, or at least it feels that way to me. FLOSS projects that aren't highly critical but very useful are maintained by only one person which loses interest, burns out or simply has other priorities. Sometimes they don't even make an announcement like here and just ghost the project. Very sad, even though understandable.
> The main problem right now is that we don’t really understand how LLMs work internally.

Right, and this is why claims that models are “reasoning” can’t be taken at face value. This space is filled with overloaded terms and anthropomorphic language that describes some behavior of the LLM but this doesn’t justify a leap to the belief that these terms actually represent the underlying functionality of the model, e.g. when terms like “hallucinate”, “understand”, etc. are used, they do not represent the biological processes these ideas stem from or carry the implications of a system that mimics those processes.

> Everyone who claims they know LLMs can’t reason are just making huge leaps of irrational conclusions because not only does their conclusion contradict actual evidence but they don’t even know how LLMs work because nobody knows.

If you believe this to be true, you must then also accept that it’s equally irrational to claim these models are actually “reasoning”. The point of citing the Apple paper was that there’s currently a lack of consensus and in some cases major disagreement about what is actually occurring behind the scenes.

Everything you’ve written to justify the idea that reasoning is occurring can be used against the idea that reasoning is occurring. This will continue to be true until we gain a better understanding of how these models work.

The reason the Apple paper is interesting is because it’s some of the latest writing on this subject, and points at inconvenient truths about the operation of these models that at the very least would indicate that if reasoning is occurring, it’s extremely inconsistent and unreliable.

No need to be combative here - aside from being against HN guidelines, there just isn’t enough understanding yet for anyone to be making absolute claims, and the point of my comment was to add counterpoints to a conversation, not make some claim about the absolute nature of things.
You don’t think you’re being a bit harsh here?
> In Germany there’s not so much parking to observe any visible effects.

That doesn't make sense. German streets are full of cars, partly because there's insufficient dedicated parking space. Lower car ownership would have a very visible effect on the streets.
> Telegram gets the "lol" because it's not default E2EE.

I use Telegram mostly for group chats, pretty much as an IRC replacement. I think that's where it really shines. :)

Agreed that even WhatsApp is more secure, but if I remember correctly, they do not promise that metadata is E2EE (if that's even possible), and Meta harvests that.
> Congrats, now these hosts can't talk to each other due to the ULA addresses being less preferred.

What do you mean by this? Are you taking about mDNS still referencing the withdrawn prefix?
The point of making mind maps by hand is that they help you memorize and study by synthesizing a topic.

If this is done by AI it's pretty much pointless.
I don't think the author's understanding of what a "leaky abstraction" is jives with how I've ever used it or heard it used. To me, a leaky abstraction is when there's hidden behavior underneath that makes the observed behavior when using the abstraction to change in ways that aren't intuitive based on the API contract.

For example, "everything is a file" on UNIX is a leaky abstraction: read() and write() can behave in wildly different ways, and have significantly different constraints, depending on what the file descriptor refers to (regular file, character device, socket, memfd, etc.).

Hell, C stdio/unistd functions themselves are leaky abstractions even when we're only considering regular files on disk. For example, even if your open()+write()+close() succeeds, the data may have not yet hit the disk, and might be lost if the machine crashes right after close() returns. And in some cases an fsync() might not even be enough, if the disk lies to the OS about the state of its own buffers and cache.

Put another way, abstractions are about hiding (hopefully) unnecessary implementation details from the person using your abstraction. An abstraction is leaky when those hidden details turn out to actually be important, and the person using your abstraction needs to understand them anyway.

The "Dependency Dog" sidebar block that has a mini-rant about AppKit on macOS is further evidence that the author doesn't know what a leaky abstraction is. You might not like AppKit, but every windowing system has canonical APIs to make windows/surfaces and draw things and define behavior and handle input. You just... have to use them, or some abstraction built on top of them. That doesn't make them leaky. (Also, pretty much every UI toolkit out there has restrictions on multi-threading; seems like a weird thing to complain about.)

The author's use of "blocking" was also a little confusing. To me, "blocking" means making a call that's going to sit and spin while waiting on I/O (or some other slow/contended resource), but the author uses it to mean "a function that is not declared async". The opposite of async is sync, not blocking.
Yeah, it's pretty common for teachers in some schools in the US to be assaulted by students. Many schools have metal detectors and other security measures.
At Apple, back in the 80s anyway, you could put anything you wanted on your business card except President or CEO.

One of my cow-orkers had "Dread Pirate Roberts (retired)"
It was one of the STEP interns that took down Google prod by modifying some config file by putting something erroneous into an automated tool. Everyone at the company was locked out, and someone had to physically access some machines in a datacenter to recover.
I was "Senior Technician" at my salaried job. At 16.

I was the first employee, and so, even though they hired a second, I argued I was "Senior".
IIRC the USSR coins weighted their value in grams, so that the cashier can know their value just by weighting them on the scales.
The DEA is the threat
I'm not sure how similar these are but this reminds me of the Soft White Underbelly series of interviews: https://www.youtube.com/c/SoftWhiteUnderbelly/videos
> From what I've seen in Amazon it's pretty consistent that they do not blame the messenger which is what they consider the person who messed up

Interesting that my experience has been the exact opposite.

Whenever I’ve participated in COE discussions (incident analysis), questions have been focused on highlighting who made the mistake or who didn’t take the right precautions.
I'm using passkeys in BitWarden, and they so far work everywhere, except for the Apple Developer website. That doesn't _have_ a passkey enrollment option, and instead automagically creates it in the keychain somehow.

I checked the way they are implemented in BitWarden, and it's straightforward.

BTW, the blog is disingenuous. The removal of device attestation from PassKeys was a great boon for compatibility. And the experience with resetting key storages or not having enough slots are simply bugs and/or limitations of hardware. Which was to be expected from a new technology.
The mother of all "mondegreens": https://www.youtube.com/shorts/bImP2zdxpng