skysight-inc/HackerNews huggingface dataset:
What's with the Apache Foundation being the literal farm where projects are sent to die? Over the years I've come to associate any of their project with "it's basically abandonware, avoid" which has also coloured my opinion of the Apache web server, which was very much alive at the time. In fact, these days even the Apache server project has gone silent and virtually dead to most [1], except for those that still run the classic LAMP stack.

So, why has the Apache Foundation basically become synonymous with final resting place for everything under their stewardship?

1: fun fact, Apache ran 50% of websites in 2009, by 2022 this share fell below 25%.
We've already seen problems from that system where they try to enforce copyright (prevent the model from generating copyrighted materials).

I've also encountered the content moderation system when summarizing a book on Islam and I still don't know what triggered it, I certainly wasn't asking it anything offensive. The message was able to regenerate with no problem.

I think generally people are opposed to content restrictions outside of their control being placed on the system they're paying for.
JS divergence isn't just the average. it's 0.5(KL(P||M) + KL(Q||M)) where M is the mixture of P and Q: M = 0.5(P + Q)
Have you ever wondered what if time travel was possible and we were already living in one of the optimal worlds of possibilities corrected by time travelers? Suddenly such terrible things that happened in history were inevitable because the other alternatives would have been much worse?
Anyone can become a PI in Colorado with just some business cards.
While, making it easy (and possible in the first place) to write procedural code directly in a transaction is a core part of FQL's design, it is certainly possible to implement safe read-modify-write via FQL, it's just less efficient.
But don't you need to install lot of packages for it to be useful?
Well .. if you hire people solely based on leetcode style interviews, this is what you get.

Or maybe this is the fate of the industry gorilla? The other company that falls in this relaxed camp is Microsoft. I am sure there are others.
If it is humanity's destiny to discover time travel and kill Hitler, it would have already (had?) happened. If time travel becomes possible we already are in the "modified" time line.

I don't know what "free will" has to do with it. Hitler had the "free will" to do what he did, has nothing to do with time travel.
Ask HN: Why can't you unsubscribe from Apple promotional emails?
Every week I get promotional emails from Apple: 3 months of free Apple TV, or a month of free Apple Arcade, or a month of Apple Music, etc.

My impression was GDPR says you have to give people a way to unsubscribe from your emails. But it seems like Apple doesn't give this option (I don't see an "unsubscribe" link anywhere on the email).

Is this legal?
Muscle memory is not a bug.
Unless it's a complete wipeout, there will be plenty of bicycles, solar panels and IKEA knives left - that's a significant leg up in rebuilding civilisation.

Before coal there was wood, before oil there was whaling - when the global population is under 1bln, energy isn't much of an issue.

The wars over it though - that would be the tough part.
The wikipedia for Ellen doesn't mention Jeffrey Ullman by name. Is there a reason which people prefer not to refer to, which explains why the coyness, or was it some other computer science Ullman which adopted Ellen? It does state she was raised in a computer science family.

People deserve to stand on their own two legs, and if its "not in the shadow, shines by herself" I can get behind that. Or indeed "no, it's just a coincidence, the adoptive parent isn't Jeffrey and his partner"

(I too was raised in a computer science family, 3 generations now. In my own case, regression tended to the mean but I have high hopes of the next one.)
> Semver in applications tells you important things such as how different a release is and how much incompatibility to expect

I disagree that it tells you either.

Release A adds massive new features, with hundreds of thousands of lines of new code, dozens of new third-party dependencies, but with zero (intentional) backward incompatibilities – increment minor version only.

Release B only removes one tiny obscure legacy feature which almost nobody used. But that's backward incompatible, so must increment the major version.

For any user considering whether to upgrade, release A is almost surely a much bigger risk than release B – yet semver tells them that B is major whereas A is only minor.

Similarly, consider release C which removes dozens of features, many of which are widely used. Obviously release C is a much bigger risk than release B which only removes a single obscure legacy feature – but since semver treats backward compatibility as a binary "yes-no", it fails to communicate that release C is a much bigger deal than release B.

> True, semver doesn't literally tell you how old a release is, but how often is that important?

Well, if the year is 2023, and I'm running WhateverApp 2010, I instantly know I'm running a really old version, and ought to look into whether there is a newer one. Whereas, if I'm running WhateverApp 2021, it is only two years old, so I'll put researching newer versions a lot further down my priority list.
> Does something like that sound useful to other folks?

Very much so!

One piece I'd like to have is a good output format from my program. Right now I have stuff outputting logs in JSON format to stderr/local file (then picked up by the Opentelemetry OTLP collector, Datadog agent, AWS CloudWatch, whatever) and the traces/spans actually sent from my process to the collector over the network. It baffles me why the traces/spans are done in that way rather than placed in a local file (and for compressibility, ideally the same file as the logs). The local file method would make it easier to have simple local-focused tools, would lower the requirements for outputting these records (no need to have async+http client set up, just the writer thread), and would better handle the collector being in a bad mood at the moment.

That's the most important piece, but if getting that done requires inventing a new format (it seems to?!?), there are some other details I'd like to it to do well. You should be able to see all the stuff associated with each log entry's matching span, which means that spans and attributes should be recorded on open, not just on close. (Attributes can also be updated mid-span; the Rust tracing library allows this.) (OpenTelemetry notably only supports complete spans). It could be more efficient by interning the keys. some care about how rotation is handled, timestamps are handled, etc.
Court Says No Human Author, No Copyright
> It's a tarpit for staying in the local optimum that most Nix use is in right now.

I know that pre-flakes conventions for reusing Nix code are pretty open-ended, and naturally 'pure evaluation mode' means turning a bunch of things off. I can also see how if you are interested in integrations with stateful systems or maybe relaxing certain constraints or allowing/tracking some 'impurities', that might also seem like a step in the wrong direction.

Do you have any possibilities (or examples) in mind for how Nix might be used beyond the 'local optimum' of most current usage?
Look I'm not trying to make this an attack on you. My generous read is that you just chose some poor examples. But teams can and do succeed despite bad management techniques like poorly implemented OKRs all the time.

If the goal is to build a managed k8s service, a team of talented people can build it without the need for OKRs.

Coming from an SRE backround I see a better OKR breakdown on the Engineering side as follows:

* Objective: A stable Managed service that the business can sell
* Key Result: - A monthly availability of 99.99%
* Key Result: - Monthly P90 API latency below 500ms
* Key Result: - a new instance of the service serving customers in the new region by the end of the quarter.

(Yes, these are really just SLOs, they're a good fit for this)

I know the objective rolls up to the business goal of a revenue target.
I know that if i'm meeting my own goal buy the metrics we can measure from the service.
I know how to prioritize engineering work. If one target is being missed consistently, the fixes are going to be prioritized
At review time, I can point to improvement work that fixed/improved the results an know the business thinks its important.

Give me some vague objective and unmeasurable of researching and understanding something? I'll BS my way through filling out the form and go back to improving the service
This link (for me anyway) doesn't cause the loop like the other one:

https://archive.is/rRVo4
The pricing page is confusing to me. It doesn’t mention anything about email in the free tier. It just says:

> Unlimited pages

> Desktop, tablet, and mobile access

> IPFS support

> Full text search

Which seems to be all about the document service, but it also doesn’t mention how much storage I get. I assume it’s not unlimited despite saying “Unlimited pages.”

Also, I can see that Skiff has raised over $14M in VC funds[1], so as a privacy-focused product with a free-tier I think it’s fair to ask what they see as their path to profitability is without compromising either their privacy or their free offering.

1. https://www.crunchbase.com/organization/skiff-402f/company_f...
I think people are confused by the README showing localhost in some places and your instance url in others, causing them to assume you were centrally issuing tokens for using this project.
The waterfall effect is basically just blur! The problem with adding blur is that—although it makes the waterfall effect work—it makes the image blurry.

Personally, I don't think it's that the CRT is better than the filters, I think you're just used to the imperfections of a CRT.

Also, I really do think you need a 4K HDR screen (with good HDR, there's a lot of variance) in order for filters to really emulate the look of a CRT.
The first commercial microprocessor?
I guess PureOS is one way of solving the problem of large log files taking too much space in Android.
I honestly don’t get why people are so furious about this. I asked my two siblings, two friends from my uni days and two friends from work and none of them have used the Lightning (soon to be USB-C) port for anything but charging and music.

None of them even remember connecting it to a computer past the iPhone 5S.
But you can't read a dozen sheets of paper at the same time anyways.
I'd never heard the hard-G pronunciation until the late 90s. I was assuming it was an internet newb thing due to correlation. And then one day in the early aughts when I heard someone who'd been a netizen for as long as I was.

At that point I realized it was just a thing :)
> Instead, we should ban the things TikTok does that we think should be illegal, and then apply the law equally to US and foreign social media companies

This would would destroy billions of dollars in profits, take down most of the ad-tech industry, which is why I suspect it will never happen. It's much easier to target individual companies like TikTok, or Cambridge Analytica while leaving the gravy train going.

For the record, I fully agree with you on what the remedy ought to be - just cynical about viability.
Nu_plugin_DNS: A Nushell-Native Dig
lnav is neat but doesn't really do structured logging AFAICT, just predetermined fields for the format.
Did you opt for LORA or did you tune all of the layers?
RISC-V Star64 JH7110: Inside the Display Controller
It’s almost certainly just a LoRA
There's a continuation of the story at https://www.civilbeat.org/beat/state-water-official-who-dela...

I am not familiar with what happened to make any judgement, just linking the part 2.
As a personal user of calender versioning, it solves some of my problems with sematic versioning, telling when it was released at a glance, and it makes it easier to apply; just look at the date, making it 0-1 clicks. Sematic versioning, on the other hand requires you to remember the last version, and apply accordingly, which takes 1-3 clicks for me.
> How is the title 'clickbait'? Calling It "LibreOffice Changing To Year.Month Based Versioning Scheme" or similar just makes it longer and less immediately clear... Really I honestly fail to see how it could be considered 'clickbait' for phrasing it as simply as possible.

"LibreOffice Changing To Year.Month Based Versioning Scheme" is far more clear than "LibreOffice 24.2 Will Succeed LibreOffice 7.6". The only reason I clicked through to the comments is because it was not immediately clear to me why LibreOffice would choose to skip to 24.2.
I understand where that sentiment comes from, especially looking at the slew of mid-sized companies that have never turned a profit despite paying multiple hundred K TCs, but if you look at the profits of the giants, it paints a different picture. The labor of thousands of very highly compensated engineers is still a drop in the bucket of the revenue generated by their labor. Alphabet seemingly employs somewhere between 20-40 thousand engineers, and it is their labor that produced all (?) of their revenue generating products. Spreading last year's revenue (~$282B) across their engineering staff would yield a revenue in the ballpark of $9M per engineer.

We all know that their engineers are paid well, but that's still potentially more than an order of magnitude off of the value they generate. Of course, there are many other expenses to running their business, but to claim that broadly developers are overvalued when one of the most prolific employers of developers is generating 10x+ the revenue of what they spend on them, is likely no more than only occasionally correct.
Hah, fair. I guess my main gripe is that there doesn't seem to be any avenue for backpressure - the security team makes an edict about how things have to be in order to be secure, and after that there's no reasoning with them. No explaining why their argument doesn't apply in this case, etc. etc. Perhaps because they are so used to everyone hating them that they can't listen, since people will always argue with them.

Our security team also engages in social engineering - making practices deemed insecure gradually more and more difficult through artificial roadblocks (e.g., adding y/n dialogues to commands that previously had none). Doesn't do a whole lot to build goodwill
Across every consumer-facing device where it has ever been deployed—which is probably in the billions at this point thanks to iPhone alone—consumer-grade biometric face unlock technology has a body count of precisely zero.

If I turn out to be the world's first facial recognition casualty, that would be SUCH a hilariously unlikely way to go that I almost couldn't even be mad about it.
Ha! I recall the exact same thing happening to me. I guess they decided that if they sign people up for some nonsense service then there is a "business relationship" and they're free to spam all they want.

glad to see it getting slapped down.
It’s very interesting to me that copyright lawsuits in the US may end up resulting in a lot of content restrictions which have some similarity to Chinese censorship laws. Zooming in they are different of course, but it is certainly a reflection of values.

In the US it is very possible we could end up with a neutered ChatGPT due to ongoing copyright suits. OpenAI easily can’t prevent its chatbot from regurgitating copyrighted material.

Although not the same, it is reminiscent of Chinese censorship of political topics, since it’s also not possible to prevent the bot from authoring a pro-democracy screed. In the same way the West doesn’t mind ChatGPT’s political musings, China is unlikely to care about any potential copyright infringements.

Maybe it’s obvious, but I find it interesting how a chatbot which is trained on all online text pushes the boundaries of societies differently. In China, it’s you can’t say a thing because it is transgressive but in the West it’s you can’t say a thing because it has been privatized.

And in the West, copyright is again coming for free expression by suing IA.

Perhaps the logical conclusion of this is the US National Anthem somehow being copyrighted and the only place it can be legally played is in China.
Who would buy these net additional exports and where would they get the funds to pay for them?
Is it true that these frameworks only work with async compatible libraries? Will a typical pypi lib work with them? For example, a css or xpath parsing library, or date time library - do I have to worry about those blocking and not working properly with asyncio or the others? Or only network and file reading libs?

I wish the article had spent more time on this. Without more info I would probably just use what the author mentions at the end as the Pareto ideal solution (ThreadPoolExecutor) because usually async frameworks in not historically async languages end up being islands within the larger community that need their own bespoke libraries.
As another perspective, I personally prefer products that are paid because it makes me less concerned that my data is the product, and less concerned that the product will disappear or stop improving.
No one said they don’t have the resources. They just asked why it’s incumbent on Apple to spend them, which your response.. doesn’t address at all? If we’re going to post with that much sarcasm let’s try to have equal amount of substance to go with it?
Ah i get it - yes thats true indeed. They do a lot of reading, but sometimes its hard to find a book that suits the age range, subject and isnt too "textbook" like but still covers the main points on the curriculum.

But your right and in fact found a great one for science for my son just now!
This is structured logging. Stubbornly insisting that "structured logging" === "map" is dumb and ignores a large fraction of use cases where performance matters.
What would those dire consequences be? The US economy is humming right now.
Oh nice catch. All this time I had been thinking the wrong thing.
There is a quite common "design feature" in official functions which says if you stick to a rulebook you can be covered for indemnity and if you divert from a rulebook you are on your own. It stops risky behaviour. It is designed to stop things like Chernobyl.

In some situations, it turns into a flaw. "Computer says no"

This played out in Queensland over a flood which had a dam release issue, and went to law between 2 agencies, the government overall, and the affected businesses and householders who were flooded. The case had to be tried in another states courts, to avoid systematic bias issues.

Of course you need to stick to the rulebook. But the rulebook needs to be written to handle unforseen situations, which might be hard, but not impossible. Put it up the food chain, or provide from some limited relief from risk.

So, the emergency sirens weren't used because "they aren't for this function" and now we have "can't approve the water release" -Sounds like the reaction of somebody who is concerned they will answer for a decision not explicitly covered in the rulebook.

Or, they simply didn't understand their role, and their authority to act. Which of course, should be explained in the rulebook.

[edit: people are pointing out there were huge risks in using the sirens, and the rulebook was really explicit, and the community understood their narrow intent. So, its probably a bad example of my hypothesised "rulebook says no" thing]
Even before the digital/internet sea change, this didn't capture the whole music industry. There were artists who made good money off their recordings either because they DIYd it, or found better labels, or negotiated better deals. None of those paths has ever been easy but before recording revenue got kneecapped it was more available.

But let's say for the sake of argument that's how it worked before the internet. If so, why did we let that level of disruption just replace one set of bad guys with another?

What we should have had instead was what we were on track to have: multiple-scale digital recording retail, Apple to Bandcamp to individual artist site to local indie collective as point of sale. Charge whatever artist and buyer choose and can clear a transaction at, they keep 70-90%. True streaming, some with a format, some algorithmically customized for both audio wallpaper and music discovery... but in every case not user-programmed because that's how you justify the difference between the ridiculous fractional cent payouts and recordings.

That's the world we could have tomorrow if the policy was there.

More likely, everybody's too used to a decade of having the privilege of an unlimited basically free recording buffet that Spotify used to cannibalize the industry and we won't do it no matter how it erodes the economics of creation. But we could.
I always thought you wanted to minimize, not maximize, the unsprung mass. So putting giant hub motors on would kind of defeat the goal, no?
Reading the article this seems perfectly fine.

"DLNR delayed releasing water requested by West Maui Land Co. to help prevent the spread of fire, sources familiar with the situation said."

The priority should be to stop the spread of fire not prevent houses being burned down.
Metal is not a standard graphics API. It's a platform-specific Apple thing. I use it and it's pretty nice, but it's not a cross-platform standard.
Also fake words used in dictionaries for the same purpose

https://en.wikipedia.org/wiki/Fictitious_entry
GPT 3.5 is so bad it's useless to me - for writing it's too repetitive of the same kind of jargon, for coding it's wrong way too often. The NLP is also worse, I have to be more explicit. It's just an average chat bot IMO.

GPT 4 @ $20/mo. is significantly better at everything, I use it for doing stuff in Angular lol - when you have an AI explaining the why behind everything, this over-engineered mess of a framework starts to actually make sense. Definitely nice to have around as a translator/teacher or troubleshooting assistant. Can't imagine googling for answers to problems if this gets any better. The main thing is just habit - GPT 4 is lower effort to arrive at more direct, bespoke answers.

The one feature I want is built-in prompt-splitting, so we don't have to use third-party tools. In my all-wise random person's opinion: Forget the old versions of GPT, and forget the phony ethics, and focus on the best version of this technology, sell it for $20/month, make billions and disrupt a lot of things online.
https://archive.is/DjPjo
Perhaps it was fast due to lack of tight security policies etc. These days, everything has to be containerized or be in a sandbox. That adds layers of overhead. Probably also why Google killed NaCl (Native Clients for Google Chrome). It was loosely in the same space as Flash and ActiveX - anyone remember that?
Can you perhaps think of any other meta books in other (or same) domain?
It's not always obvious when music players are changing the metadata of your files vs storing stuff in some other database.
You’re overstating the risks.

Respiratory risks of solder aware minimal, particularly ironically the leaded variety. If you’re worried solder with the window open or get an extractor. I haven’t needed either in the last 40 odd years.

The lead itself is harmless unless you ingest lots of it. Wash your hands. That is all you need to do. Take it to the WEEE bin or waste disposal if you discard it.

I learned to solder when I was 8. My kids when they were 10. It’s fine. I built my first amateur radio transceiver when I was 12!

Soldering kit is cheap. Even decent metcal stuff can be had for virtually nothing if you shop around.
Skiff says they encrypt email subjects while protonmail does not. I cannot determine from browsing if they encrypt the sender and receiver addresses.

Skiff's free tier also has a 'generous' free tier with 4 aliases, 10GB of drive (only? combined with email?) storage, and custom domain support (? !)