skysight-inc/HackerNews huggingface dataset:
It is known which priests were kid rapist and the police didn't do much about it. Despite of their low interest in the past now they are very concerned about child sexual abuse and they want mass surveillance.
Sitting on a tram in Sheffield, early noughties, a chap with a magnificent unreconstructed ROCK mullet gets off. I see two women chatting on the street, they are stunned into slack-jawed amazement as he struts past -- one of the women makes a scissor-snipping hand gesture behind him as he passes, the whole tram erupts in laughter.
I know it is editable, it's just inconvenient af to edit the text if the diagram is being drawn right over it.
I once had UUID collisions in Linux Boot IDs when we started developing our own embedded systems at my company.

Found them because systemd-journald isn't very happy when Boot IDs repeat and (apparently, then) stops showing earlier boots once it hits a repeating boot ID. And I wanted to see an earlier boot. Then I started logging the Boot ID in a textfile myself and it took less than 10 reboots to have duplicate Boot IDs.

Long story short, some weeks earlier, I "optimized" the Kernel config for that system and some config flags that didn't sound like something I'd need. As it turns out, an ARCH_ZYNQ target apparently also needs ARCH_VEXPRESS set. Otherwise it works absolutely fine, but with a broken RNG that you will notice weeks later.

That was a valuable "don't take down a fence until you know the reason why it was put up" lesson. Don't unset kernel config flags until you know why they are set.

Aside from breaking RNGs, I've never experienced any UUID collisions either.
Ha, took me two minutes to make that code sandbox.

Can you tell me at least if it is possible in Nue to create something functional like this and how? Or is it just a bunch of macro with some weird imperatives inside usual XML syntax?

I really want to see 4 lines of code doing the same thing 2x faster :D
But the private data you are protecting (the user's account creation time) has the same properties as an eternal secret.

Therefore there doesn't seem to be much downside in this specific case.
> Moderate amount of well implemented obscurity is helpful.

You're getting that wrong: Everything else being equal, the more obscure system will always be the safer one. It's just that obscurity can easily be lost, so your system should, if in any way possible, still be secure even if fully known.
In the end, however, no system is 100% secure, but more obscurity will make it harder to find the inevitably existing issues.
James Webb Telescope makes 'JuMBO' discovery of planet-like objects in Orion
> Serfs were not one thing.

Well yeah, never implied they were. That comment was a reply to a specific claim about serfdom being a relationship which might have been beneficial to both sides. That certainly wasn't the case by the 18-19th centuries. Nor was I 'making any general statements about serfs' in the medieval or pre medieval periods (or outside Central and Eastern Europe for that matter).
Thank you, Alan!
> Software is software, people are people and governments are governments.

While that is true, it is also true, that people can easily be forced by bad acting governments to do things to the software they write.

We don't need to condemn the people in general, but we can still be wary of the product they make, while being in the influence zone of certain governments.
I'm not the author, but I work at the same company. ULIDs are nice, but we're a 10 year old company with many TBs of data across multiple logical databases and most rows had UUIDv4 ids.

Maybe if we were starting from scratch ULIDs would have been an option, but given where we were UUIDv7 was a much easier transition.
This was a good interview with her: https://josephnoelwalker.com/147-katalin-kariko/

She had a very interesting life, I hope she writes a memoir.

Edit: She has a memoir out 10th Oct: https://www.penguinrandomhouse.com/books/706251/breaking-thr...
We cannot draw a legitimate statistics, as that could be our own bubble. But it’s incorrect to say an average Joe doesn’t support the war. Even those who oppose the war, do they do something? Or do they like ‘I don’t like it, but there’s nothing I can (want to) do.’
What I haven't found a solution for, is being able to synchronise and open a gocryptfs with cloud sync on Android. Dropbox/Drive/pCloud folders aren't directly accessible or mounted in Android. One work-around could be to export a zip of the folder from Dropbox/whatever, then extract and open that, but that's one-way.

Do you have a solution for this?
The US has become so hawkish that Kissinger actually looks dovish these days. Surprising but true.
> if Google stopped developing Android

Maybe someone else will try to make something from it or not.

> Or would they switch to pushing Tizen forward instead?

And it would fail. As much as Windows phones etc. The ecosystem isn't big enough. Phones are only useful because of what runs on it. Samsung only doesn't have the push to make it happen and it'd increase their already low margins.

It's not like Samsung is making lots of $$$ at the moment. For context, the government had to give their leader a get out of jail card so Samsung can be fixed. In the past, they had to spy and steal from TSMC to make their fabs work. I doubt they have the ability to create a new ecosystem.

Android collectively is still less attractive to developers vs iOS. What makes Tizen better with a drastic cut in market share?
PN 2.5 data is also pretty bad https://www.theguardian.com/environment/ng-interactive/2023/...
Deep-Sea Octopus Nursery
On the whole, the answer here is "not at all," or if anything, slightly increases the likelihood that I'll use it.

1) There's a difference between a government and people living in that country. If my country does something evil, that doesn't mean you should attack me (personally). The firebombing of Dresden by the allies in WWII is widely considered a war crime since it targeted civilians and killed many little children.

2) With sanctions on this war, I see two valid goals: (1) Regime change (2) Not funding / supporting the war. To be clear: Punishment of people in Russia is not a valid goal for sanctions.

3) With a country doing something evil, simply cutting off ties doesn't have much positive effect (see North Korea).

4) Attacking people simply polarizes them to hate you and supports Putin's message.

5) Even under sanctions, there are constructive ways of engagement. These generally center on communications and cultural engagement. Things like rock-and-roll, Disney, Coca Cola, McDonald's and blue jeans played a pretty significant role in the downfall of the Soviet Union. Trade helped open up China (it's not open, but it's a much freer, nicer place to live than 50 years ago, largely due to people doing business across borders).

My general conclusion here:

1) I don't think we should be buying anything from Russia. That provides money to support the war effort.

2) I don't think we should be exporting anything which can in any way be used to help build weapons (e.g. technology, raw materials, etc.).

3) I'm also on the more extreme end of sending more weapons to Ukraine (much more than we have been).

On the other hand, with Russia, I am fully in favor of scientific engagement (think blue whales and not radar research), educational engagement, cultural engagement, as well as things like open source.

Controversially, I'm also supportive of /selling/ luxury goods to Russia. I don't think it supports the regime in any appreciable way, and a Gucci handbag won't help the war effort. It does bring in Western culture and leads to capital outflow.
Looks like Floorp in relation to Firefox is the same as Vivaldi in relation to Chrome: a fork aimed at power users with a native support for vertical tabs. Will keep an eye on it. Meanwhile, I spend several minutes trying to create a new workspace and failed to do it. It's ok, will definitely give Floorp another try when it transitions from Beta to a stable release.
The onclick="addFruit" calls an instance method between the inner script tags. Similar to how JS would call a global window.addFruit with a similar syntax.
True, most issues are with RAID, but there are still many others listed here[1] that I wouldn't be comfortable with.

Perhaps I'm being overly cautious after years of not experiencing issues with ext4+LVM+LUKS. BTRFS always gave the impression of being in a perpetual state of instability, but maybe I should take another look at it.

[1]: https://wiki.debian.org/Btrfs#Status
> Real people with problems to pay rent and buy a house cannot afford (like us) live in the center of a city anymore and wont be in the near future.

People who don't have a car aren't real people?
The Greening of Milan: Porta Nuova and Vertical Forest
That sounds anecdotal. There's not really evidence of it being more productive than anything else
Looks like they made the same design decision as Rust's early green thread implementation. Quoting that link:

> The key benefit of green threads is that it makes function colors disappear and simplifies the progr'samming model.

As a point of order, no, green threads don't make colours disappear. They can't as the whole point is to run multiple tasks, so no green task can be allowed to make a blocking I/O call like native code does, so you have re-do every I/O library using non-blocking I/O. And thus green threads must use the non-blocking version of the library, aka as a different coloured code.

Where green threads are different to async is the language library can make the colouring disappear for green threads. It does that by, on every I/O call, checking if a green thread is making the call and switch between blocking and non-blocking I/O accordingly. That incurs a speed penalty of course. And it doesn't just hit green thread code, it slows down native threads too.

Looks like .net decided that overhead is too high to bear. Fair enough - but that's a consequence the decision to hide coloured code, not green threads per se.

While you could do the same trick to hide blocking vs non-blocking for async code too of course, it wouldn't hide colouring. That's because async colours code in other ways too - for example it introduces a whole now call / return syntax. Unlike "not needing colours", not needing a new syntax is a real advantage of green threads over async. Another one is saving state on the stack rather than a malloced block. (If writing function locals to a malloc'ed block was faster than pushing them on a stack was faster we would do it everywhere.)
Yeah the problem with these (pipelines, compilations) is they last long enough to take some of your time but not long enough to, say, read a full article, complete a tutorial, watch an educational video from the beginning to end etc. So HN somehow falls nicely in there.
I'm literally answering a comment claiming the US has never done anything of the like.

It's not whataboutism to bring up a counterexample in this case and calling it such is nothing less than jingoist propaganda.
Fyi, the timestamp is already encoded inside uuid4.
But for having a good distribution of values, the low bits half of the timestamp is stored before the high bits half.

Here uuidv7 will just re-order that. So the content of the uuid in itself does not change.
> but the tools that have been brought into the mainstream like Kubernetes

unless you are running real steel, kubernetes is at best a complication layer over the underlying cloud tools. In 2018 me and my team built a real time, ML-based processing API. It was hugely scalable, optimised for speed, price and uptime.

At no point did we use need to use kubernetes. Not only would that have eaten most of our innovation budget, all it would have done is add latency and driven up the money we spent on inter VPC transfers.

> I remember the days of Nagios, Zabbix, SolarWinds etc

So do I, they were recognised as shit even in 2015. $work allowed me to lead the migration away from them and by then we were half way through replacing most of splunk with graphite/grafana based metrics instead. The rest of the alerting was mostly handled by a custom inhouse /__status end point parser.

> The previous iteration of platform at this company was all self-managed VMs with the old school sysadmin mindset. They were managing hundreds of VMs by hand or using some light ansible that was retrofitted to work with pre-existing machines, we were using corporate F5 load balancers and VMware which are immediately out of date the moment you deploy them.

That, again, is just bad sysadmin. Unless you have complete control over your stack with ansible, then its not ansible, its just sparkling bash script.

I worked at a VFX company that deployed to all real machines for virtually everything. They used a GNU configuration system that was older than SSH (I can't remember what its called, it used to use rsh, that's how old it was.) All the machines were fungible, We could replace a file server at the drop of a hat (the only limit was how fast we could copy 160tbs over 2x10gig nics) Most of the place ran on perl, in one git repo for just configuration. OS updates were applied weekly, and we pushed system changes daily. This was in 2013.

salt made all of that easier, especially as we had way too many hosts to sensibly run ansible at the time(I think we worked out it would take >1day to run a basic role).

They had automated it to the point that you could plug in an unconfigured blade host, turn it on, and within 30 minutes, the bios was updated, networking configured and each blade was starting to be installed.

Automation is an attitude. You can either invent new tools to solve hypothetical problems badly (k8s supposedly is high scale, but cant practically get above 1k hosts, its also balls deep in ipv4 ), or actually use/create tools to solve the problems you have now.
Well, you could hook it to an AppleTalk network w/ stock hardware and then setup a Mac gateway to get it onto an Ethernet network. I think I've got a setup for that around here somewheres...
I don't find it weird at all that simpler languages are more popular/successful.

They're easier to pick up and support the idea of plug and play programmers that is very popular among managers.

Productive as a consequence of the above, maybe; in that more code is written in Go; but certainly not as a quality of the language.

And there's numbness and denial involved. I've been writing Go full time for about a year now at work. Every time I use another language I'm reminded of how much time and energy I'm wasting.
The PET had an IEEE-488 bus and these more rounded PETs are gorgeous machines.

Sadly, these are not abundant at all - they were far from a commercial success. As why they are attractive over x86 and Macs, is because they are different. Much like the Lisa, they represent the road not taken, or, at least, a past long lost.
Perhaps it's because now these people can finally afford the stuff that they could only dream of when they were kids?
Airbnb Is Fundamentally Broken, Its CEO Says. He Plans to Fix It
I read the title as "two kids in trench coats" and was thinking about Columbine.
Do you have to pay ULEZ charges? I know this is an issue for many people with older cars.
Half of the articles in the category are WWII campaigns.
You could simply base32, base36 or base64 encode the UUID's (as an example).

Other than that; in IE6 times URL's had a limitation of 1K or 4K or something around that lenght IIRC, so unless you're using dozens of UUID's in a URL this hasn't been a problem for ages.
What's "lower level" in this context? And why shouldn't we assume that assembly language or even circuit design will also be affected by describing in natural language?

We've heard variations on this argument for decades and I see no difference why LLMs, despite their immense capabilities, will be massively different. They still take guidance and produce garbage output which requires knowledge and expertise to turn into a cohesive product. Will they replace some script writing, or some business logic translation? Of course. But so did SQL, no-code, and plain-English testing frameworks. LLMs are an incredibly powerful tool but they're not a silver bullet.
Burning the wrong kind of plastic produces dioxin.
“Eye comfort” requires qualification. E-ink contrast is so low that manufacturers are careful to not mention the actual contrast ratio (generally in the low two-digits to 1). Depending on individual eyesight, that can be quite straining.
My company literally can’t fit all its staff in offices. It’s simply got rid of its leases on buildings as they expire.

This is a company that has a required in person presence for many staff, operates 24/7 and did so throughout covid.
IMO the benefit of UUIDs over integers is that they can be generated client-side without clashing. But you cannot trust timestamps generated by clients and therefore the order. So what is the benefit over UUID4?
The massive Javits Center was also made available. 2500 beds, only 141 used.

https://gothamist.com/news/fema-begin-strategic-drawdown-lar...
> BUT my problem with this is "where do you draw the line?"

Wherever it makes sense for you and your organisation. There's not a list of approved "boring technology" and unapproved "exciting but scary technology". It's not about the age of the technology, but your level of experience with it. If you know it inside out, understand its failure modes and can easily find information when something goes wrong it's "boring".

If your team can configure AWS services in their sleep but have never touched a bare metal box then AWS is boring. On the flip side, if you're a bunch of Linux greybeards and wrote the book on iptables but can barely spell VPC then on-prem is boring.

This is also where the concept of "innovation tokens" comes in. C++ is well established and quite far from innovative on its own, but if you're building a web app and your team is full of new graduates and interns that have only ever touched Javascript and Python then using C++ would spend one of your "innovation tokens" as your team is busy learning it instead of learning the business domain.
Isn’t that almost the same as v1?
Build simple fuzzer – part 6
Do those dashes cause any meaningful performance impact, or is this just a microoptimization obsession?
Ask HN: Why use any other languages when Python can do the job?
Hi all,

Python is becoming one of the most popular languages. And with all the backing from big corporations, it will only get faster and more ecosystem. Even when performance matters, the worst case is to write a small bit of your application in Go/Rust/C.

If you are creating a new product today, why would you not choose Python?
Is this the first practical, mass deployable remote code execution in a human? Or was there something earlier?

I particularly enjoyed the unreasonably effective antivirus bypass achieved by slight modification of the payload by introducing pseudouridine (Ψ), which the antivirus had never seen before and therefore ignored. Such a bypass definitely deserves a Nobel Prize!
Don't know, because uuidv7 has been coming for ages...
https://www.ietf.org/archive/id/draft-peabody-dispatch-new-u...
There's perf/watt but also area on the core that's an important factor. Watt and area are often related but not always. Do you know how the A510 cores and Apple's efficiency cores compare on area?
This sort of pathetic political misinformation should have no place on HN
There's an rLCD 32" monitor from a vendor called Sun Vision, at roughly the same price. They usually make outdoor signage displays, but recently decided to produce a desktop monitor too. I spent some time researching it a few months back, but didn't end up buying it because there's no way to test it before buying where I live (only in the UK where they have a sales rep).

Reportedly, rLCD looks spectacularly good in bright sunlight. It also doesn't have the ghosting and low FPS issues that eInk displays (still) have. Its resolution might be lower than eInk (equivalent of full HD IIRC), but that's hard to compare I guess. Anyway, rLCD seems like a more promising solution to eyestrain to me - with enough ambient lighting, those are almost equivalent to a normal display.
They did reduce transmission. We have actual data from US prisons.

If you want to look at dodgy science, anything around "moral hazards" is on very shaky grounds...
Calling it that feels wrong to me. They're putting a label on people who ignore their manipulative trash. Plenty of people don't use social media, or watch news and movies, they're not in "monk mode"
That question is pointless if you're using windows
Not parent commenter, but I believe everything social should be kept to real life. The dynamics of online social media have almost nothing to do with real human interactions. It is a waste of time and a harmful superstimulus substitute, like empty calory fast food for real nutrition.
Purely random identifiers are the recommended primary key for plenty of databases - eg. spanner.

Random identifiers spread work evenly between shards of something sharded by keyspace. They also don't get 'hotspotting' on more recent records - recent records frequently get more than their fair share of updates and changes, and database query planners have no knowledge of that.
Also, as far as I know, no one has ever dismantled a navy reactor. Every such reactor that has ever been built is in service or sitting in some yard. Any scheme that would make use of navy sized reactors would create a stream of reactors no one knows how to safely dispose off after use.

Compare this to civilian reactors for which dismantling and repurposing of the location is part of the cost calculation nowadays.
Everyone's throwing out suggestions, so I'll say what I've found to work well after years of sampling the options.

pfSense box + Ruckus WAP

I went with a Netgate SG-1100 and am happy with it for 200/100 WAN. I have a Ruckus R610 (used on ebay for $100) that gets regular Unleashed firmware updates and is far and away the best WAP I have ever owned.
> I can't change other people's behavior. I can only change mine.

Ah my friend, you totally can change other people's behaviour. go on. hug an ops, sit next to them and work with them. show them a bit of love and make them feel part of the team. Think about it from their view, why don't they trust your scripts?

Why dont they feel empowered to spin up a staging area? is it a skills gap? fear? or do they not feel confident enough to ask.

It sounds like solving their problem will also solve yours....
Where I live almost all waste, including nonreyclable plastic, is already burned for fuel.
It’s kind of exactly what it is tho
Having sequential ID's is more than just a security risk, it's an information risk. Competitors can use them to estimate the size of your business, the number of customers you have, and all sorts of stuff.

This was used in the war to estimate the number of German tanks based on the sequential IDs

https://en.wikipedia.org/wiki/German_tank_problem

So just for business intelligence you don't want to leak your IDs.
Good thing we have data that proves lives were saved and you don’t have to guess.
gh link -> https://github.com/skanaar/nomnoml
All viruses are "remote code execution" - including vaccines made from weakened viruses or repurposed viral vectors.

mRNA tech is just cutting out a lot of cruft and mass-producing and delivering tiny mRNA strands directly.
If you're scaling horizontally it's doubtful that language choice of rust Vs Go is going to make a difference.

Not enough, anyway, to make a complete rewrite more profitable over adding features.

After all, it's not as easy if influx was plagued by concurrency bugs, was it?

A move to a safer language than go just doesn't seem worth it, and there's little to no performance gain when you can just throw more hardware for that tiny performance difference.
I don’t understand this comment. In a city like Amsterdam you certainly don’t need a car to go to the supermarket or college. I’ve lived in cities with far worse public transport and no car and had no issues.