MurphyA/hacker-news huggingface dataset:
by jcgl | 2025-11-28 23:29:52+00:00
That doesn't seem right to me, assuming you still want the paradigm of one-time principal-to-domain authentication with just-in-time principal-to-resource authentication. While I think you could probably use x509 certs to streamline and modernize the ticket-granting-and-session-key dance, you'd still be doing a lot of the same high-level things.

Depending on the use-case, Kerberos (/this imagined x509 Kerberos) or Oauth2 still seems suitable for single-authenticator/multiple-services paradigm.
by jcynix | 2025-11-28 23:30:25+00:00
> Are we just shittier engineers, is it more complex [...]

Both IMO: first, anybody could buy a computer during the last three decades, dabble in programming without learning basic concepts of software construction and/or user-interface design and get a job.

And copying bad libraries was (and is) easy. I still get angry when software tells me "this isn't a valid phone number" when I cut/copy/paste a number with a blank or a hyphen between digits. Or worse, libraries which expect the local part of an email address to only consist of alphanumeric characters and maybe a hyphen.

Second, writing software definitely is more complex than building physical objects. Because there are "no laws" of physics which limit what can be done. In the sense that physics tell you that you need to follow certain rules to get a stable building or a bridge capable of withstanding rain, wind, etc.
by aeturnum | 2025-11-28 23:30:37+00:00
Email has been updated many times in the last 20 years. All of the major sender authentication protocols (SPF, DKIM, DMARC) were created and deployed over the last 20 years. Email is also famously insecure and lacking a standard way of managing encryption - so the reason you never see updates is because the features signal is changing do not exist in email at all.
by stavros | 2025-11-28 23:30:37+00:00
I'm one of those people, but I have an absolutely bizarre response to the drug. I've tried to start it five times, and failed four.

I'll have one of two responses:

1. The drug works, and it completely eliminates food noise and the desire to eat unhealthy foods, but I'll get severe side effects (massive diarrhea, vomiting, burps that reek of rotten egg). I lose weight, but a lot of it because I can't keep anything down.

2. The drug doesn't work almost at all. I get minimal effects, and minimal side effects. This is where I am now, I've been consistently going up in dose (incrementally, so I don't trigger the side effects). I'm at 10mg now, and there's minimal effect.

Just mystifying.
by razingeden | 2025-11-28 23:30:54+00:00
great sales yeah (7bn+) but those dsp6 recalls on the fiesta cost ford about 2 billion.

id buy another one. (in manual.)

i dont know how many other gen5 fiesta owners would walk down the aisle with that car again tho

i think the dsp’s kind of cool. still have a 2011 in a barn somewhere. its on engine #2 and transmission #2 at 124,000 and thats not even counting all the bad grounds, bad caps, electrical squirrels ive been able to track down and fix. it wasnt that bad to deal with, but i totally empathize with anyone who doesnt remember theirs fondly or want to go out and get another one just like it
by SpecialistK | 2025-11-28 23:31:21+00:00
I'm confused by the first half of your first point - I understand frustration at Apple's constant "throw it out and move on" attitude, but if that did not exist I would still want software to be compiled for the CPU I'm using where possible. It's why I download amd64 instead of x86 binaries on Windows, and run CachyOS built for x86-64 v3 on my Zen 3 PC.

The second half I agree with. Apple has "their vision" of what computing should be, and you need to be ride or die with that vision. Including application deprecation, unrepairable hardware, and artificial locks to make sure you're not misbehaving. That doesn't work for a lot of people, and was something I had to accept when I bought a Macbook after a decade away from the ecosystem (it helps that I now have an army of ThinkPads, a homelab, and a gaming PC.) But if you don't want to pay lots of money to visit Apple Disneyland on their terms, no one can reasonably blame you.

Sadly, Microsoft has enshittified Windows to the point that I jumped off - that 30 year backwards compatibility isn't worth the spying and advertising (LTSC helps, but not enough) and the Linux/BSD world expect binaries to be recompiled to the point that people joke that Win32 via WINE is the Linux stable ABI.

Everything has trade offs or things that benefit the business much more than the users.
by arianvanp | 2025-11-28 23:31:29+00:00
And it should've been NixOS after!

It did slowly sneak in over time I guess. In my last year of my master's eventually the faculty was forced to stop hosting its own intranet and mailing lists and migrate everything to the "cloud" (Microsoft 365 and Blackboard).

I have a copy at home of all the old wiki content and the old cs.uu.nl website. The university themselves didn't even think they should archive it so I archived it myself.

I hope there's other people with copies too. My archive isn't complete
by pbmonster | 2025-11-28 23:32:46+00:00
> And yet it's still far cheaper than any other form of seasonal storage.

Only for countries with very suitable landscape, and the willingness to use it - damming high altitude valley is extremely unpopular and bad for the environment.

Also, pumped hydro is expensive. Initial capex is higher than today's lithium batteries, if you design comparable systems. The only reason anybody is still building new pumped storage is that you can use it for 100 years (instead of 20 for the batteries, although nobody really knows how much they'll actually degrade).

I think we'll find hundreds of TWh of seasonal storage elsewhere. Thermal storage is extremely attractive if (or once) you have district heating installed. Takes care of a massive junk of domestic heating, and could take over light (food processing, paper,... ) and medium (chemical, ...) industry. Just don't try to turn it back into electricity...

Once steel and concrete get electrified, we might get seasonal hydrogen storage in underground salt caverns. Concrete and steel need absurd amounts of high heat which probably means making lots of hydrogen, putting those in the right locations might make additional hydrogen for fuel cells/gas turbines available, relatively cheaply (still extremely expensive, seasonal storage always is). But who knows...
by grishka | 2025-11-28 23:33:06+00:00
It's just two broadcast receivers (one for receiving the push token, another for receiving actual notifications), and one broadcast sender to ask GSF to give you a token. This code is so trivial it's not even worth separating into a library.

Here's how you request a push token:

Intent intent = new Intent("com.google.iid.TOKEN_REQUEST"); intent.setPackage("com.google.android.gms"); intent.putExtra("app", PendingIntent.getBroadcast(context, 0, new Intent(), PendingIntent.FLAG_IMMUTABLE)); intent.putExtra("sender", FCM_SENDER_ID); intent.putExtra("subtype", FCM_SENDER_ID); intent.putExtra("scope", "*"); intent.putExtra("kid", "|ID|1|"); context.sendBroadcast(intent);

Here are the two receivers:

<receiver android:name=".PushNotificationReceiver" android:exported="true" android:permission="com.google.android.c2dm.permission.SEND"> <intent-filter> <action android:name="com.google.android.c2dm.intent.RECEIVE" /> </intent-filter> </receiver> <receiver android:name=".api.PushSubscriptionManager$RegistrationReceiver" android:exported="true" android:permission="com.google.android.c2dm.permission.SEND"> <intent-filter> <action android:name="com.google.android.c2dm.intent.REGISTRATION"/> </intent-filter> </receiver>

The first one is where you get notifications. The parameters you sent from the server will simply be your intent extras.

The second one is where you get push tokens. There will be a "registration_id" extra string which is your token. It may start with "|ID|1|" (the "kid" parameter from the request, not quite sure what it does), in which case you need to remove that part.

You want to refresh your push token every time your app gets updated and also just periodically if you haven't done it in a while. I do it every 30 days.
by tgsovlerkhgsel | 2025-11-28 23:33:23+00:00
Isn't the point that they intentionally glossed over ("We did not model what would happen if data center demand collapses and Meta cannot secure a new tenant. This scenario was excluded for methodological convenience.") a pretty important one?

If I understand the explanations on HN, the complaint is that Meta is taking on debt, which would normally affect its credit rating, so they're "hiding" the debt in a LLC without materially changing anything. Thus, alleging that Meta is "faking" a higher credit rating than it should have.

However, it looks like this construct might actually protect Meta against the main two risks that might make the datacenter be unprofitable (force majeure like a disaster destroying it, or a collapse of datacenter demand), i.e. keeping the good credit rating may be justified because the construct is actually very different, protecting Meta from risk, even though the article suggests that it's just a fig leaf?
by gruez | 2025-11-28 23:33:36+00:00
>Slicing paper thin and perfectly frying is an industrial process that most people can’t replicate at home.

It's baffling how for some people, the only way they can explain why chips are unhealthy is "industrial process", when the explanation is pretty obvious: thin slices means more surface area, which means more oil absorption and burnt bits. If you replicated the thiness at home somehow (which isn't hard if you have a mandolin), it'll be equally as unhealthy, maybe more if you factor in that your temperature control wouldn't be as precise.
by rzerowan | 2025-11-28 23:33:37+00:00
Not just the UI ,as you can see with Blender it goes toe-to-toe with the paying big suites like Maya and Autodesk, a legacy of its dvelopment being proprietary.Comparad to GIMP et al difference is stark.

Most of those UI/usability changes are market specific, like in my post Corel has speciaized to cater to lawyers so their workflow reflets that. LibrOffice and the others are highlygeneric , even MO as bloated as it is has specific workflows that hook their respective nicehe business verticals.
by adam_arthur | 2025-11-28 23:33:59+00:00
Yes, which is why the companies that develop the models aren't cost viable. (Google and others who can subsidize it at a loss obviously are excepted)

Where is the return on the model development costs if anybody can host a roughly equivalent model for the same price and completely bypass the model development cost?

Your point is inline with the entire bear thesis on these companies.

For any use cases which are analytical/backend oriented, and don't scale 1:1 with number of users (of which there are a lot), you can already run a close to cutting edge model on a few thousand dollars of hardware. I do this at home already
by 01100011 | 2025-11-28 23:34:00+00:00
and shorting something priced in a currency is effectively going long on the currency as well. If the USD takes a dive due to, idk, increasing populism from both major parties, stocks will do quite well in nominal terms. Your shorts will burn and you'll end up far worse than just staying in cash.

For most people, the best way to short is to just hold cash equivalents like short-term treasuries.
by cedws | 2025-11-28 23:35:43+00:00
1. I created a room but after refreshing lost it and then couldn't rejoin or recreate the room

2. Setup is a bit of a painful (had to install software and then still couldn't get audio to work from Rekordbox) so if that could be simplified it would be cool

3. I like the chat, makes me feel like I missed out on the IRC era
by rollcat | 2025-11-28 23:35:45+00:00
> Partnerships could mean more than just fab capacity -- maybe even incentives to build an instruction translation layer so software built for Intel chips could run natively on Apple Silicon. Something like Rosetta, but at the hardware level.

Rosetta is pretty damn fine as-is, and yet Apple is removing it, because they don't care for supporting anything older than 7 years.

Which is pretty hypocritical of them, touting gaming on Macs is good now, yet throwing 90% of the remaining game library (after killing off i386).

> Getting a lot of down-votes for this... why are people so down on the idea?

People mistake "downvote" for "disagree". You should only downvote a comment when it doesn't contribute anything to the discussion. If you disagree - you can argue, or just move on.
by fao_ | 2025-11-28 23:36:04+00:00
Conversations has an issue where the main tool for reading a backup on a computer (ceb2txt (so, say, I can properly and correctly archive a text dump archive of a person I loved who died)), will not work for me. I filed a support request and there's been no movement on it whatsoever and it genuinely seems like nobody gives a shit. Restoring a backup even with all the images and media files in the correct place with the correct filenames will then refuse to show any filenames.

This is par for the course with chat backups, though.

Messenger - Bad - No way to save chat responses of people you have talked to. This means you only ever have one side of a conversation, making it meaningless.

Twitter DMs - Bad - See Messenger.

Jami - Ehhhh - Saves a git local repository of messages. The only problem is message syncing is effing abysmal.

Dino (XMPP) - Bad - Does not allow backing anything up, this is "intentional". Depending on which protocol you use, as soon as you move to another device all the messages you _had_ are retroactively converted to Cannot Decrypt. They're my effing messages!

Discord - Good - Discord History Tracker (tedious to use but slurps everything up into a sqlite3 database that is itself, an official archival format)

WhatsApp - Good - Dumps a text record + files/images/etc. onto the phone's filesystem. This is reasonably easy to archive.

Signal - Mediocre - If you have an old Signal backup from 2018? That you could only transfer off your phone by deleting old messages? lmao you're effed. Load up a version from ten years ago, gradually update it and then maybe, MAYBE you can extract the sqlite3 archive? These days you have a .signalbackup or whatever which is an encrypted archive, and I assume that there's a tool to decrypt it, but uhhhhhh. Last I tried to use it it required way more RAM than I had accessible.
by yoyo250 | 2025-11-28 23:36:05+00:00
It seems that newly registered accounts are currently shadowbanned by default. At least that's what I did.

For example, when I send my first post, I find that I cannot see it on another device that is not logged in.

It might not have been shut down Manually by the admins; HN has its own antispam system.

In my opinion, these may automatically get you tagged and shadowbanned.

- using a VPN - posting instead of comment immediately after registration - posts containing unusual links (like personal blogs)
by tonyarkles | 2025-11-28 23:36:49+00:00
To give you a bit of insight, around the same timeframe (late October/early November) I directly observed two high-accuracy RTK GPS receivers reporting high accuracy (2cm), full 3D DGPS lock with carrier phase, and positions wandering within about a 5m circle horizontally. The altitude was staying pretty consistent (within about 1m, which was outside of the reported accuracy but not bad) until there was a sudden 60m altitude shift. This was all while they were sitting static on the ground, verified both by the crew and the accelerometer, gyro, and RADAR data.

There wasn’t a software fix per se, but we were able to quickly add a check to verify that the Kalman Filter’s position variance estimate was on the same order of magnitude as the accuracy level that the receivers were reporting and put a big red warning up. This wasn’t a flight-critical system, but it is the first time we’d ever seen that behaviour from those receivers and we’ve used them for 5 years.
by swatcoder | 2025-11-28 23:36:51+00:00
I don't think they really are.

There is, effectively, a "learning curve" required to make them useful right now, and a lot of churn on technique, because the tools remain profoundly immature and their results are delicate and inconsistent. To get anything out of them and trust what you get, you need to figure out how to hold them right for your task.

But presuming that there's something real here, and there does seem to be something, eventually all that will smooth out and late adopters who decide want to use the tools will be able onboard themselves plenty fast. The whole vision of them is to make the work easier, more accessible, and more productive, after all. Having a big learning curve doesn't align with that vision.

Unless they happen to make you more significantly productive today on the tasks you want to pursue, which only seems to be true for select people, there's no particular reason to be an early adopter.
by the__alchemist | 2025-11-28 23:37:08+00:00
This is great! The prev recommendation was usually a lib called celery that I wasn't able to get working. I don't remember the details, but it had high friction points or compatibility barriers I wasn't able to overcome. This integration fits Django's batteries included approach.

I've been handling this, so far, with separate standalone scripts that hook into Django's models and ORM. You have to use certain incantations in an explicit order at the top of the module to make this happen.
by tgsovlerkhgsel | 2025-11-28 23:37:17+00:00
To me it reads like the article intentionally pretends two major risks (force majeure and datacenter demand collapse) don't exist, by quipping that "rating agencies historically treat as theoretical inconveniences rather than recurring features of the physical world" for the former and explicitly saying they ignored it for "methodological convenience" for the latter.

If those have been offloaded to the LLC, wouldn't that be a pretty key difference?
by evanelias | 2025-11-28 23:37:20+00:00
That data center started operation over a decade ago. There's no reason to assume it should have any vacancies currently, nor is there any reason to assume its positions were largely filled by non-locals. And even if a few external folks relocated in some cases, isn't that economically beneficial to the area regardless?

Also given the 24/7/365 nature of data center operation, the number of employees will be larger than the number of parking spots.
by britch | 2025-11-28 23:37:25+00:00
I think about this a lot. My belief is professional programmers should not be artists.

I think about other professions. A cook cannot spend time making every dish perfect. A bricklayer isn't perfectly aligning every brick. Even in movie-making there's a shooting schedule. Things go wrong and the best filmmakers know how to keep the production moving.

I love the craft of programming, but I see a lot other craft-oriented programmers who want every line to be beautiful. If you want to write code poetry in your off-time, that's your business. But that's not the job.

At work we are bricklayers and cooks. We practice a craft, but also have time constraints. I try to do my best work while working at pace. Sometimes my code could be better, but it's not worth the time to fix. Ultimately the thing we make is the running software, not what's under the hood. The business people are sometimes right
by croes | 2025-11-28 23:37:35+00:00
> The "downside" of having good paying, high quality, stable jobs is the existence of billionaires.

This correlation doesn’t exist. Billionaires also exist where people have low paid, low quality jobs.

Often the billionaires are also shareholders of those companies.

So while they paid billions in dividends they also said the job guarantees are gone because 5 billions are missing.

It weren’t the workers who botched the development of new series but neither the management nor the shareholders feel the consequences.

And it isn’t only VW. Also BMW and Mercedes.

Right wing parties often complain about social security payments as unearned income, what are dividends and why do the shareholders pay less taxes on that income as the workers who actually build the products?

Billionaires are a symptom of a skewed economy where one side gets more and more of the wealth while the middle class is told it’s because of the lower class, unemployed and refugees
by thisislife2 | 2025-11-28 23:37:43+00:00
I can understand why this would be priority for Airbus even without the incident of a flight losing altitude - recently read that a major philosophical difference between Airbus and Boeing is that Airbus prioritises the safety of the Aircraft through controls (hardware and software) where as Boeing believes a human should always be the final decision maker and be able to over ride any control. An Airbus rarely allows a pilot to over ride any warning or allow the pilot to exceed the specifications of the aircraft, whereas a Boeing will warn the pilot about an unsafe action but will allow the pilot to over ride it. It will be interesting to see how things change when AI tech creeps into Aviation tech.
by RealityVoid | 2025-11-28 23:39:16+00:00
After reset, it went away. If it was this kind of hw issue, it should still be present.

Considering those units were designed back when they did not have EDAC mandated, I can believe it could have been a bit flip (along with some other stuff they will probably address to take into consideration this failure mode). Nowadays, most MCU's have ECC on them so the time of this excuse is mostly gone now. :)
by lillesvin | 2025-11-28 23:39:20+00:00
I know it's kinda besides the point and I don't know what language this was being done in, but I don't personally know any language where

String signature = "POST" + "\n" + "/api/v1/..."

and

String signature = "POST\n/api/v1/..."

don't result in identical variables, so I'm a bit puzzled why that would result in an error.

However, there's a quoting error in the failing example where the double quotes in the JSON body aren't properly escaped:

String signature = "POST" + "\n" + "/api/v1/query" + "\n" + token + "\n" + timestamp + "\n" + "{"body":"content"}"

It may just be the example that's not correctly formatted, but the other (working) example does in fact escape the double quotes in the JSON. I guess, depending on how forgiving the used language is with quoting, that could also be the source of the error?
by fragmede | 2025-11-28 23:39:27+00:00
https://news.ycombinator.com/threads?id=Kuraj

It's two clicks to get to that page from this page. Say the wrong thing here and some troll will go through it and find something you said years ago that contradicts something you're saying today. If the mere thought of that bothers you, I don't know what to tell you other than to warn you of the possibility.
by znpy | 2025-11-28 23:40:32+00:00
This overall makes sense.

In my experience at a FAANG working on one of the core services for both internal and external customers, essentially two kind of people crank out great code:

1. "rock stars": they joined the company at 25 and they're still there at 35+. they're allowed pretty much everything (eg: no RTO, work from home country) and they know many codebases across the services very deep. they aren't really motivated to go look elsewhere, their grass is already one of the greenest.

2. people with kids. the company pays enough. they aren't really interested in switching job, rather they want to provide for their family. they're good, and maybe every now and then will push through for a promo in order to face new challenges in life (another child coming or some kind of new financial burden).

i'm not saying either one is inherently good or bad.

but yeah. in such large companies you end up working in on a very large codebase that interacts with other very large codebases. all the codebases are proprietary and you're lucky if you can use some libraries that come from the outside world (that have not been heavily lobo^H^H^H^H customized - the libraries i mean).

you do what you can, you do your best, but you're essentially a relative beginner.