Hacker Newsnew | past | comments | ask | show | jobs | submit | afiori's commentslogin

Long term archival is often also about long term support and there just going with the most popular/supported ones might be a safer bet, eg in the extreme case if I wanted to save some digital photos in a time capsule I would likely choose PNG and JPEG

Maybe even split it into a set of small reusable coherent utility classes


federations are the only decentralization model that scales, the issue is that most "federated" systems are actually just "distributed centralization" eg mastodon.


There's a technical difference between a "distributed" system and a "decentralized" system.


What is federation if not ‘distributed centralisation’?


In cryptosystems there is a difference between things that can be changed and not, eg passwords/keys are a secret that can be easily charged. Algorithms not so much.

"Security through obscurity" refers to the practice of using an hard to change "thing" as a secret, which is indeed bad practice


Not exactly.

Security through obscurity in cryptosystems would mean defining your own crypto algorithm (or using a secretly-defined one, secret in the sense that it is unknown to the adversaries) to protect your system.

It is NOT bad in itself. It IS bad if you only rely on that. Even if you'd use a "secret" algorithm, you MUST protect the keys as with a public algorithm. Also, being secret means you cannot benefit from the cryptanalysis of the community, which is in practice very important. BUT... if you have a lot of cryptanalysis expertise at disposal, then using a secret algorithm can be very effective.


The US and its allies are likely the biggest sponsor of terrorism and genocide worldwide


Maybe maybe not. But doesn't change what Iran does. The Iranian embassy in the UK just encouraged violence in the UK. Then next day random jews were stabbed.


Naval blockades are an act of war even according to US own laws.


The hosts file is enough, what is needed is a way to assign an ip address to a process/service like you can with port numbers.


You can trivially have a server process bind a listening socket to eg. 127.4.3.19.


Imo there would be ways to do it so that it could have a similar effect to the capitalized nouns in German


Some come to async from callbacks and others from (green)threads.

If you come from callbacks it is (almost) purely an upgrade, from threads is it more mixed.


Yeah, that's what annoys me, async comes from people who only knew about callbacks and not other forms of inter thread communication.


Not true. I’ve used both, and I often prefer the explicitness of async await. It’s easier to reason about. The language guarantees that functions which aren’t async can’t be preempted - and that makes a lot of code much easier to write because you don’t need mutexes, atonics and semaphores everywhere. And that in turn often dramatically improves performance.

At least in JS. I don’t find async in rust anywhere near as nice to use. But that’s a separate conversation.


Pardon power competes with governors (at least NY) being able to edit laws before signing them for most anachronistic/dystopian feature of the US state.


You've reminded me of an absolutely bizzare line item veto story.

https://en.wikipedia.org/wiki/Line-item_veto_in_the_United_S...

> In 2023, Governor Tony Evers used a line-item veto to extend what was supposed to be a two year temporary funding increase for schools to last over 400 years.

https://www.businessinsider.com/wisconsin-tony-evers-400-yea...

> Evers was able to make the nearly 400-year-old addition by vetoing part of a phrase that had referred to the 2024-25 school year, by striking a hyphen and the "20." When read together, the legislature's previous proposals for the 2023-24 and the 2024-25 school years became 2023-2425.

The WI Supreme Court upheld it. What a fucked-up system.

In picture form: https://platform.vox.com/wp-content/uploads/sites/2/chorus/u...


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: