skysight-inc/HackerNews huggingface dataset:
I've always found it a bit disquieting how many times people feel the need to update these "cryptographic right answers" blog posts.

This is what, a fourth or fifth version since 2009?

Meanwhile everything from ubuntu's apt-get to my connection to HN is secured with 2048-bit RSA - an algorithm invented in 1977 and in widespread use since at least 1995.

Am I getting crypto advice that will keep my data safe for 30+ years, if the advice changes every 3 years?
I made the same thing a few years ago. Youtube embeds, react, socket.io and postgresql on a node.js server. I got the idea from poolside.fm's video player.

https://wem5637.medium.com/i-made-a-probably-illegal-youtube...
Funny how one of the the few comments actually discussing the content of the article gets downvoted while generic memes that have nothing to do with it get upvoted.
Absolutely. A message queue with pattern-based retrieval is a hacky way of getting the first two-thirds of a tuplespace. But, like using a database as a message queue, while it kinda sorta works for the most part, the benefits of the model come in when you start to treat it on its own terms rather than via an encoding. Tuplespaces have a little more to them (not a lot, but some) than just pattern-based retrieval, but some of the research work on them has been focused on appropriate fault-recovery strategies, strategies for sharding and distributing the spaces, etc etc.
Show HN: Free Tools for Tabs, Chords, Lyrics Use 8 A100 GPUs
I swear I've seen this cover before... is this a new release or an updated edition of an older book?
The Syndicated Actor Model started off (see dissertation) without any notion of object or actor or entity reference at all. Actors inhabited a single dataspace and there was no baked-in addressing. Since then various developments have led to introduction of entity references (like object references in E). Taken together with dataspaces, this gives you several ways of introducing spacelike separation: you can use different message shapes+patterns, like in "classic" Syndicate or like in tuplespaces; you can use entity-references to have multiple dataspaces on the go at once, forcing isolation that way; or some combination of the two.
Written or Oral. We can't all agree on what happened 2 years ago. So multiply how we all view the last 2 years, then extrapolate that to what you tell your kids, and they tell their kids, and add a 100 years.

The last few years has caused me to doubt all history. All written or oral records are all
I literally setup an alias last week in O365 Outlook using the pattern a.b@c.com? I’ve been able to receive and send using the alias as well. Maybe this is a new feature/behavior?
Book is not yet published but in early access since a couple of years

Was featured here a couple of times.

Unfortunately the timing of the release is quite unfortunate with regards to the summer holidays. Will take a look at it next year
> I think the original link already includes the conversion w/ inflation. It says that the book retailed for fivepence in 1735 which is ₤10 8s. 4d in today's money.

No, it didn't say that, that was the total. It said that 500 copies of the book at fivepence was worth ₤10 8s. 4d, and the maths checks out on that: 5500=2500 pence (written 2500d as old pence). There are 20 shillings in a pound, and 12 pence in shilling, so 2400d = £10, with 100d remaining. 8 shillings is 96d, so from 100d leaves 4d remaining, which matches exactly what was originally written.

The post-decimalisation equivalent preserved 20 shillings to a pound, so 1s=5p. An interesting fact is the new 5p coins were the same size, and existing shillings continued to be legal tender for another two decades, until the size of the 5p coin was changed. So, the parent to your post was totally wrong with the $10.84, it should be £10 + 40p + 1½p (closest to 5p4/12), so £10.41½ after decimalisation. The closest conversion rate I could find to the time the US introduced the dollar was £1 = $4.55, because it was done at the prevailing values of gold and silver at the time.

Using your link, and adding precision to the numbers, £10415 in 1735 would be £1,889,613 today, so £108s4d then would be £1889.61 today as the total gift. Dividing by the 500 copies gives £3.78 each today, which is close to your approximation (most of the difference will be the accuracy lost in rounding 5/240 to 0.02).

The inflation rates are also certain to have been difference in the US though, if for no other reason that the current exchange rate is approx. £1 = $1.28, so at the very least it's close to a factor of 4 out in the period since the US dollar was introduced.
10 Must-know cloud security strategies for 2024
Surveillance Watch: map of intricate connections between surveillance companies
Happens to the best of us. Life is a dance not a maze.
I think that many websites need to focus on the local context first. Modernism was founded on the ideals of an international literacy which is why it can be so plain.

The internet’s global reach may distort the real world practicalities of a website’s function.

I hope we are soon hit by a wave of “narrowcasting” vs. “broadcasting”. The distinguishing feature between the 2 is the sustainability of the publishing apparatus.

Broadcasting requires large audience acceptance to be sustainable and narrowcasting requires at least 1 avid publisher/producer.
As far as I know, most of the developed and in development countries have this kind of database, I also know some poor countries does too, but they often lack security measures
It's apples and oranges.

If a founder is successful they stand to earn billions in intellectual property value, not to mention the income from the product itself.

PHD's earn practically no money even if they are succesful, apart from earning their degree. (Which has an abstract long-term monetary value)

Seems very different to me. Apart from this, PHD's are employees, while founders are... well... bosses ;)
Also paywall.
The Decline in Writing About Progress
Dissertation didn't touch on the connection to Ambients too much, but there's clearly some kind of "there" there. Future work, still, I'm afraid.
https://archive.is/B1BjC
Zamm v0.1.5: Odds and Ends
Poolsuite.net
Whether you like or dislike Agile, this article is extremely biased to an agency context.

Which is interesting because I would argue an agency can never care as much about a product as an in house motivated, customer centric team.

Marty Cagan’s mantra at times is missionaries not mercenaries, and an agency is the exact definition of a mercenary.

Good product development should never be outsourced and I don't think this article is meaningful for engineers and other knowledge workers operating in startups and tech companies.

Clearly a lot of people have been burned by Agile and are not working in agencies, but I just want to highlight the context of the article a bit.
I guess the idea is was that Firedancer is designed with fixed update rate in mind. And the demo makes an assumption that it will run at 60 FPS = 60 updates per second, probably becoming very fast and hard on 360 Hz screens.
But that's just nitpicking on details in library demo. It would be bad to have such mistake in a real game or game engine demo, but it's not that surprising for example code to skip details for the sake of simplicity. The main purpose of example is demonstrating the library as cleanly as possible without distracting reader by containing more boiler plate code for third party game engine than the thing it's attempting to demonstrate.
I don't see a reason why you couldn't update FireDancer VM at whatever fixed rate you want (faster or slower than typical FPS) just like many games and game engines with fixed tick rate for physics or game logic handle it.
Well I'm in Europe (Romania) too and street crime is basically nonexistent where I live, yet I don't let my 11 years old kid commute home by himself. Problem is cars, he only has to make a mistake once and I can't afford that mistake.

I grew up in the countryside in the 80s, cars there were as rare as hen teeth at the time so entirely different situation. Also parents used to have 2-3 kids back then, I only have one so gotta pay extra care coze there's no backup :)
I'm sorry about the state of the docs. I am slowly working on improving the situation.

You might find the ~blog/journal part of the site interesting, wrt examples: https://syndicate-lang.org/journal/ -- still not exactly an embarrassment of riches, but it's something.
No, in animated models, there is no gap between polygons. And if you only compute single-polygon coverage, you can’t determine whether for two polygons that each cover 50% of a pixel, they both cover the same 50%, or complementary 50%, or anything in between. In practice, systems like that tend to show something like 25% background, 25% polygon A and 50% polygon B for the seam pixels, depending on draw order. That is, you get 25% background bleed.
Or for that matter, on all of the above, and any other groups one can think of; and perhaps also a "group of random individuals" study or three.
It should be approximately the same in theory - £1 was pegged to the price of silver, although of course there might be local differences in demand causing the price of silver to vary relative to the price of gold. In practice, I think the values should be approximately the same, as significant regional variations would be normalised to speculators moving them around from place to place to make a profit until the demand reached an equilibirium.
‘Homosexuality’ is similarly an abomination: first part’s Greek; second part’s Latin.
Here’s a comprehensive list of books banned in Texa, school district by school district: https://www.dallasobserver.com/news/list-of-texas-banned-boo... . On there you will find obscene books like “the Handmaid’s tale” and “the hobbit”
an algorithm publicly published in 1977.

The Ellis, Cocks and Williamson algorithm has existed since at least 1973.
Really cool! I can’t wait to try it on a blog using the techniques mentioned, nifty.
Orleans is neat because it tackles orthogonal persistence and fault recovery at the same time. Lots of interesting future work remains to be done with persistence, though: wouldn't it be interesting if there were some "third way", somewhere in the middle of spectrum between (1) traditional orthogonal persistence, which serializes the entire nitty-gritty program state (stack, register file, heap, etc etc; totally implementation oriented), and (2) the Orleans or SQL-ORM approach, where the programmer manages records explicitly and, if they're lucky, gets a bit of support to give them a reactive feeling? I'm imagining some kind of domain-specific reflection on machine state, so, a bit like traditional persistence, but filtered through a domain-specific summarization function to yield a domain-relevant data structure describing the state of the actor.
It’s not really clickbait, but I agree that the style is a bit jarring and overly ‘modern’.
That scenario is completely missing the point. Bob has to drive because of the lack of good public transportation and the fact that he can't afford a house near his work. Not to mention if he can't afford a car with insurance it's because his job simply doesn't pay enough.

It's much more likely that external factors put him in that situation, rather than himself. Yet you propose we should punish him personally and paint only Alice as a victim. That's naive. Both are victims.

These are systemic problems and trying to solve them with individual punishments is only going to hurt individuals while not fixing the underlying issues that really matter.
It'd be funny if it turned out to be an epic style rickroll

"For many moons and many suns have passed, as time, relentless, flows,
Since first their hearts, like twin flames, danced in love’s eternal fire.

Yet, the hero, of noble heart and steadfast will, did speak,
"My heart yearns for a bond unbroken, a pledge that none may sever.
No fleeting fancy, but a troth eternal, one that the gods themselves would envy.
For such a vow, none but I could offer, no other man could dare."

With eyes like the stars in the firmament, he gazed into the soul of his beloved,
And spake thus, with the voice of thunder, yet with the gentleness of the west wind:
"Hear me, O cherished one, for I must reveal the depths of my heart.
Never shall I forsake thee, never shall I let thee fall,
I shall not stray into the shadows nor abandon thee in the wilderness,
Never shall I bring sorrow to thine eyes, nor bid thee farewell.
Never shall my lips craft falsehoods that wound like the sharpest spear."

Through the ages, their bond had grown strong as the oak,
Though the maiden's heart did ache with a silent pain,
For fear held her tongue captive, her love hidden in the shadows.
But the hero, wise as the elders, knew the truth of their shared plight,
For both had danced the dance of fate, and knew well the game they played.

Then again, he spake, his voice a balm to the troubled heart:
"Do not be blind to what lies before us, for the path is clear,
And if thou wouldst ask of my heart's burden, know this:
I shall not waver, nor falter in my love for thee.
Never shall I forsake thee, never shall I let thee fall,
I shall not stray into the shadows nor abandon thee in the wilderness,
Never shall I bring sorrow to thine eyes, nor bid thee farewell.
Never shall my lips craft falsehoods that wound like the sharpest spear."

Through the years they had known each other, their souls intertwined,
Her heart had borne the weight of unspoken love,
Yet now, the veil lifted, they stood as one,
United in purpose, ready to face the trials of love's enduring quest.
And thus, the hero pledged once more, with a heart pure and true,
"Never shall I forsake thee, never shall I let thee fall,
I shall not stray into the shadows nor abandon thee in the wilderness,
Never shall I bring sorrow to thine eyes, nor bid thee farewell.
Never shall my lips craft falsehoods that wound like the sharpest spear."

So spake the hero, and the heavens themselves bore witness,
As love, unyielding, forged a bond that time could not erode.
And thus they walked, hand in hand, into the dawn of a new age,
Their hearts as one, forever bound by the sacred oath."
Only so many hours in a lifetime. I'd like to do an Erlang implementation sometime though (especially considering that Erlang/RabbitMQ is one of the places where this research started from). Or find a student interested in doing one.
Gov.uk can push a login system because it already has penetration across departments of the civil service.

It has that because of political will to implement it, combined with a coherent design language implemented as a set of well-thought-out components. It is a "pit of success" - departments get better quality for less expense, so they don't chafe about it being mandated.

I don't see the political will in America. The population hates anything that the other side touched. "The proud state of Mississippi was built on jQuery", etc.
If there's one thing I've learned from image processing it's that the idea of a pixel as a perfect square is somewhat overrated.

Anti-aliasing is exactly as it sounds, a low-pass filter to prevent artefacts. Convolution with a square pulse is serviceable, but is not actually that good a low-pass filter, you get all kinds of moire effects. This is why a Bicubic kernel that kind of mimics a perfect low-pass filter (which would be a sinc kernel), can perform better.

It is tempting to use a square kernel though, because it's pretty much the sharpest possible method of acceptable quality.
>I still don't get why people are calling these "religious fears".

People are calling these "religious fears" because they are fears very often based on religion. People who fear the Mark of the Beast aren't simply worried about being tracked by powerful institutions, they're looking for prophetic signs of the antichrist and Satanic one world government that their holy book says will lead to the second coming of Christ and Armageddon. Even though it was really talking about Nero Caesar. You can't separate the fear from the religion.

>You do not want to make it easy for every rapacious for-profit corporation to pressure every citizen to cough up an identifier that can be used to track their every move.

Then ban cellphones. Those are far more useful as a means of surveillance and control than any serial number in a database. They're also held in the hand and to the head, and used to buy and sell goods, which conforms far more closely to the mark of the beast than, say, RFID chips or SSNs or serial numbers on currency. Which the mark of the beast people were all against, in their time.

Unless you want to go full Kaczynski and run off into the woods to live off the grid, you can't avoid having identifiers attached to you. Your birth certificate, vaccination history, criminal record, credit score, address and phone number, the license plate on your car. Even the cookie that leaves you logged in to Hacker News. Governments and corporations already know who you are and where you are. Are there massive negative externalities to having our identities controlled by forces we have no agency over? Absolutely. But fearing every number as a slippery slope to a global satanic dystopian hellscape isn't reasonable. Unfortunately that's the context in which many people have this conversation, and that needs to be recognized.
Hey, we do cool stuff with gbq billing, which helps reduce computing costs.
Basically, we show how much money every pipeline costs coming in BQ, executed in BG, or leaving it. We do not query your data (do not need permission to read or edit). Everything is done using GBQ logs. I mean, we do not use your information_schema either. What we saw from our clients is at least 10% compute cost reduction in 10-30 days after deployment. Happy to give a fee trial to test it out.

Here is one of the examples
https://mastheadata.com/yalos-cost-management-blueprint-elev...
That just means the tech moves to 200 years away.
> GCHQ, the agency that cracked the german enigma codes.
And helped to spy on US citizens...
Maybe. I would not bet on the well-being of my children.
I hadn't planned on something so neat. I was just thinking I'd put them on the path with nonstandard executable names like `pvim` or `pcode`, and then people could use them in combination or not, individually enable-able as devenv modules. One of them could be aliased to `edit` or something like that if configured as the default editor, though.

So the interface would look like

editors.vim.enable = true;
editors.vim.package = pkgs.neovim;
editors.vim.plugins = [];
editors.vscodium.enable = true;
editors.defaultEditor = "vim";

and users would set or modify that in devenv.local.nix¹.

And the editors module would handle constructing the customized editor packages from the specified base packages, lists of plugins/extensions, included config, etc., as well as wrapping them so that they are called by the names `pvim`, `pcode`, `edit`, etc., and pointing them to gitignored RC files that live in-repo which users can edit.

--

https://devenv.sh/files-and-variables/
Physical security, specifically encryption and backups for after an incident occurs.
The way I understand it. (and here I'm just telling you what I have heard from other people) is that the brick we use has two layers. So going from the outside to the inside the structure is: layer1, layer2, graphite crucible, metal to be melted.

Layer1 is thermally insulating. Keeps the heat in the brick. It is still 300ish celsius at the end of the melt, and it increases further as the whole structure "cools".

Layer2 "captures" the microwave radiation and is the thing the microwave oven heats. All that energy is captured inside the brick and layer1 doesn't let it out so it heats up very quickly.

And then layer2 heats up the crucible via mainly heat conduction (so the interface has to be neat between them) and only to a lesser extent via heat radiation.

The main dangers of the operation is the same as with any other process which results in tens of grams of molten metal. Those would be not new to anyone who casts metal. (But entirely outside of the experience of someone who never worked with molten metal before.) Everyone with normal household experience would know that molten metal is hot, what might surprise someone without specific training or very good intuitive grasp of physics is that if it contacts water the water immediately turns into steam and that will make the molten metal fly everywhere. [1] So that would be the first unexpected turn of events. Hopefully you have a bucket of sand ready to put out the resulting fire, because water is not your friend in this situation.

It is also important as you pack the crucible to not form a "bridge" between the walls with the metal. Because before the metal melts it expands. And if you pack the to-be-melted metal too tight it will crack the graphite crucible. Which would ruin the brick.

Then the other surprise is that the layer1 keeps heating up even after you have removed the brick from the microwave. (because layer2 is very hot, and that heat is slowly dissipating through layer1) And if you use the brick too much without letting it cool down between melts it might crack, or it might crack the glass plate of the microwave.

1: this is how that looks on a much bigger scale https://youtu.be/oWSHEC1N770?si=lc1ZKXxQ9kOsuhz0
DBA at my previous job wanted to use SSN as a primary key. I felt like I’m talking to a child trying to convince him not to do that.
> the inner lining of your insulator will be designed to do the absorbing.

That is exactly the case with our setup.
>I usually sell my $1k phone after a couple years so I end up paying much less than $1k in the end, while getting a better phone out of it than had I just bought the $500 phone up front.

Yes, there are different ways to go about it. I buy the best phone of last year or the year before, and run it into the ground.

But is it just me, or are the changes so incremental now it's hard to justify a new model of any brand? Sure the processors get better etc, but I use my phone to browse the web, text/phone and email.
That's where I learned he was a self-righteous pompous prick who was probably shunned by his peers and never invited to the good parties. Kicked out of his own family when he was a young self-righteous pompous prick and never reconciled, he undertook the weeks-long journey from Boston to Philadelphia (including a shipwreck and washing up on the islands off the shore of Brooklyn, New York) he eventually ended up bonking his landlord's daughter and had to flee to live in the UK for a while (remember, he was British not American, just like all the other white men in the 13 colonies at the time) . Also, he was a proselytizing vegan teetotaller.

I also learned a lot of interesting history they don't teach in school, like how he was involved with an effort to form an alliance between the English colonies and the Iroquois Confederacy for the defense of North America but the collective colonial governments rejected the alliance and favoured bringing in overseas troops to conquer the Iroquois instead. He was a really smart guy as well as a self-righteous pompous prick, and he would certainly not have fit into today's USA what with his "radical left" "socialist" "woke" views. Not sure he fit into his contemporary society either because of those views.
Marian Rejewski, Jerzy Różycki, and Henryk Zygalski, mathematicians of the Polish intelligence service, were first in breaking the Enigma cipher.

Also first in building bomba an electrically powered aggregate of six Enigmas, which solved the daily keys within about two hours.

https://en.wikipedia.org/wiki/Marian_Rejewski
This looks cool, been interested in learning more about compilers since I did the basics in college. Lots of things seem to focus on making interpreters and never make it to the code generation part so its nice to see that this features information about that.