skysight-inc/HackerNews huggingface dataset:
I also lost my voice in a bizarre fire breathing accident and urgently
need to log into my telephone banking account.

Can anyone here give me a short list of relatively common ethical use
cases for this technology. I'm trying to refute the ridiculous
accusation that only deceptive, criminal minded people would have any
use for this. Thanks.

----

Edit: Thanks for the many good-faith replies. So far I see these
breaking down into;

Actual disability mitigation (of course I was joking about the circus
accident). These are rare but valid. Who wouldn't want their _own_
restored.

Entertainment and games

Education and translation

No further comment on the ethics here, but FWIW I'm nervously looking
at this having just written a study module on social engineering
attacks, stalking, harassment and confidence tricks. :/

And yes, as bare tech, it is very cool!
I've had ideas for side-projects before, but most times I never actually went to building them because I got too scared of holding private data (sometimes sensitive information such as financial data).

I thought of just building offline apps for the browser and letting the user sync data using Dropbox or some competitor, but never found an open source project to facilitate that kind of thing (an actual db that syncs through Dropbox). I also heard that locally storing a Dropbox token in the browser could be dangerous (assuming an offline-app-for-the-browser architecture, for example), which meant I'd have to build actual native apps. But then, isn't it dangerous to store a token in the OS as well?

I might never build a side project. But damn, I wish there weren't bad people willing to steal data out there.
A Little guide to building Large Language Models in 2024 [video]
cockpit is pretty nice as a headless alternative to manage and interact with kvms vs virt-manager

I also like storaged interface for exporting and mounting NFS and ISCSI. A killer feature would be to add support for nvme-tcp / nvme-rdma

Also have been meaning to look into what is involved for creating a plugin/extension for gtk-broadway - seems like the perfect fit for the browser.

Keep up the great work cockpit team
And that’s the core problem with key value stores, your data needs usually grow beyond key value scenarios. In the beginning it might fit, but then you add more pages with different needs, reporting/dashboards with different needs, APIs with different needs, and ETL processes with different needs. Trying to force everything into key value is short term thinking.
Typescript is something you learn progressively over years, and from what others have posted it might not be possible to refactor your package in Typescript (some approaches to problems that are possible in JS aren't supported by TS). But type declarations at the very least should be possible
Redesigning one of the world's largest apps is a significant challenge. How did Ian Spalter lead this process, and what learnings can we take from this case? Continue reading to understand this challenging redesign case!
> The March 25 New York magazine cover story laid out a stunning tale about Huberman—that he was seeing six women simultaneously. Further, that story says, his lab at Stanford, “according to knowledgeable sources, barely exists.” Whether or not you care about infidelity and hosts’ personal lives, listeners to Huberman’s podcast should not sweep aside the contents of the New York mag story as mere gossip.

I've seen _so_ much chatter about this on X and it can't help but leave me a bit confused. Respectfully, why should one care about the personal life of someone who gives you diet advice? Would Andrea consider him a more reliable source if he was a better partner? If that's not the case, why include it at all?

Lazy hit job; next.
Yes it does. You will always get close to 100% accuracy on small datasets if you evaluate the model using the train dataset - due to overfit.
Everything is simple if you ignore everything. Because in the mind of renewable proponents all that grid-level storage is either already available or can be easily and cheaply built, no biggie.

"We have existing infra" ignores that this infra took decades to build.

"We know how to build" ignores that the storage costs can vary between 7 EUR/kg and 1040 EUR/kg [1]

and so on and so forth.

The capability for wishful thinking in renewable space is staggering.

Note: no one is saying it is impossible BTW.

[1] Great article: https://www.sciencedirect.com/science/article/pii/S036031992...
I stopped listening to radio many years ago, because how predictable and simplistic i thought the songs were. Literally couplet, refrain, couplet refrain, a little variation of 10 seconds, refrain

It is insultingly dumb.

A happy enjoyer of Be'lakor here (EDIT: and old Infected Mushroom:)
>I had no insurance and it was reduced to $100. This was a large hospital in a major American city.

Thank You. While not perfect may be sanity is still a thing in the US.
What you’re describing isn’t an inherent problem with a key value store. Forcing everything to OLTP SQL is also short term thinking. Pick the right tool for the job.

It’s funny you mention growth as the limiting factor for key value stores, if anything that’s the one area where they’re objectively superior. Which is why most search databases and caches are key value stores.
Several years ago I bought a box of small toy Easter chicks and sent them in lots of envelopes over a period of a few weeks to my mother, as if they were 'migrating', getting workmates to write the labels and send them so they would have different postmark towns. The idea was for them to be anonymous. Some had several chicks in the envelopes.

They kept arriving at my mother's and provided much amusement, with all but one of them arriving. I also played silly games to keep the postman on his toes, sometimes leaving out the postcode (zip) or putting other typos in the address.

After the migration I visited my mum and she had the chicks everywhere, quite a collection.

Then, about three weeks later, she had one of those cards meaning she would need to visit the depot. So she went, saw the envelope and knew what it was. In this envelope the chick was standing up rather than laying flat, to make the envelope too large for standard letter rate, hence the fine. She paid up.

After hearing this tale I realised I had dodged about 57 bullets, for any of the envelopes could have ended up too large for the letter rate.

At the time the post was affordable, with it not costing £1.25 a letter. The stunt would have easily cost me £100 had I wished to repeat it this year. I would have also run the gauntlet of the fake-forged-stamp malarkey, with it randomly costing my mother £5 just because the Post Office deemed their own stamps-with-QR-codes fraudulent.

It looks like I won't be using the post for a while, which is a pity.
Most of the time I've tried to convince people not to move away from mongo i failed.

My only success was pushing back on switching from postgres to azure cosmos after Microsoft salespeople convinced some of our managers that we were making a mistake by not using their hot new toy.

This industry...
I do like this idea, but if I am honest I think this should be a feature of a BI tool vs a whole new tool.
> what not to do

I think that's the unique skill that old and experienced people bring.
Even if they're non-Americans, this is a verily heavily American-influenced forum so the people here most probably have more American habits compared to the average people in their countries.

> That's a bit universal for what's simply your opinion.

Yes, and that's a feature, not a bug, we're here to share our opinions, this is not a peer-reviewed forum.

With all that said, I still cannot understand how come a person who says he/she cares about food could eat re-heated takeaway stuff (supposedly at the microwave, which makes it double yuck-y).
Idk but its kinda cool
For every person who comments there are thousands and thousands who are reading. This is their target customer base -- highly sophisticated technical professionals who have the potential to influence many more non-technical people who take their expertise and opinions as a given. If they aren't worried about it then maybe they should think about it a bit more.
Talos appears to rely on existing components to a somewhat greater degree in comparison: https://github.com/siderolabs/pkgs
> French intelligence

What a great idea!
I pushed the company I work for to use Postgres instead of Mongo in all new services and refactors. Now I'm leaving it to join a new company, where they use Mongo. Sigh. I'll have to do this all over again.
As in "I counterfeit 99 stamps at a time then sell them. That esy I never break the law."
We can't prevent a flood, but we still have time to choose between a small flood and a big one.
He's always been fundamentally a zealot who sees most narratives in black and white terms. It's an extremely unfortunate characteristic of a software engineer.

It's the same reason he's so pro Trump I think.
> And anything they do with the content can be explained away as "necessary to provide the service". That's the problem: they're not constraining themselves in any way. They need money to provide the service, so why couldn't they decide that taking art I put on my server and selling it to people is "necessary to provide the service"? It seems like they could at any time decide that their pricing is unsustainable, so monetising customer content is "necessary to provide the service".

That's not how contract interpretation works.
Not really, I rented a box from hetzner and have ran mail-in-a-box for over a year now. The IP I was assigned was on the microsoft shitlist for a little bit, but I sent them an email explaining why I was using the server and they took me off the list. Also took a few emails to GMail to get off their spam filter, but a few emails to family and asking them to report not spam (around 3 emails) was all it took. The only server I've ever been rejected by is a corporate email server with very strict settings, but every other corporate email has been fine.
Not if you use a rdbms to store your key/values. Then you can do arbitrary queries with joins over multiple tables, add views, stored procedures, etc.
Yeah, maybe couple of USB-C ports, one for control another for power, would make sense for using a smartphone as the controller.
The Marketing Behind MongoDB (2017)
cssbattle.dev - The funnest CSS game
webmaker.app - The offline and fastest frontend playground
Vernor Vinge, Innovative Science Fiction Novelist, Dies at 79
To put this in different words, you're basically asking about steganography applied to a radio transmission. I think the answer is: unlikely to be noticed unless you were receiving particular attention for some reason. Though your noise might inadvertently violate bandwidth constraints.

If you search for radio steganography or acoustic steganography you'll find a bunch of papers on the topic.
Sam Bankman-Fried Has a Savior Complex–and Maybe You Should Too (2022)
Could be combined with translation to automatically create dubs for videos/tv/etc.
Sure, but that’s not related to what you said prior. Again, right tool for the job.
You are privy to Redis, Inc’s financials? You seem pretty confident that they are profitable.
> Why doesn't MongoDB use SQL

Perhaps not the right answer, but SQL literally stands for Structured Query Language. I suppose you'd need an USQL?
Ask HN: Good Resources to Learn Web Development Basics
What are some good books or online courses to learn basic concepts and fundamentals of web development?

I can use online tutorials and chatgpt to develop and deploy a full-stack web app. It’s quite easy but also annoying that I don’t understand what I am actually doing there. It’s a bit overwhelming, where to start? can you recommend something that helped you cover this broad field of knowledge?
Home Assistant is making huge progress in creating an open source version of Alexa, Siri, etc. You can train it to use your voice, but the obvious use is celebrity voices for your home. Alexa had them, then took them away, and refused to refund people.
Somewhat related: if someone whose technical proficiency you don't hold in high regard needs to perform a limited number of administrative actions on a network-connected Linux machine (like restarting a specific service or installing updates), there's OliveTin. You pre-program it with the list of actions you need by writing a small yaml config, and it builds a simple web interface which the person in question can use to solve simple problems without calling you all the time.

https://www.olivetin.app
Plastics Contain Thousands More Chemicals Than Thought, and Most Are Unregulated
This has serious “Get off my lawn!” vibes lol
> From my point of view managed databases only really make sense for toy projects

it is more expensive to buy managed, but you offload work. I would imagine toy projects are more cash constrained, and makes more sense to rent cheap servers and roll your own.

On the other hand, larger scale projects would rather pay to offload the work of managing and scaling redis.
Not at all. The validators get a small portion of the transaction fee for themselves and certainly they could ask for something different. But the ETH burn is built into the protocol. In theory that could be changed, if you got agreement not just from validators but from the rest of the ecosystem too. But nobody wants to change it. 1559 became very popular within days of hitting production, since it improved user experience so much. And the bigger the ecosystem gets, the harder it is to make fundamental changes.

But sure, in theory all the protocol rules could be changed. In theory Bitcoin could change their 21M supply limit. In theory, a company could sell its fixed assets and pivot to an entirely different business, or the US could change its constitution and take away property rights. But in practice, we usually estimate values based on the way things are working now, and put little weight on unlikely fundamental changes that might happen someday.
It's always amazing how someone's "indispensible feature" is something that someone else couldn't care less about.

I don't even really use the concept of open files. I mostly switch files using a fuzzy finder that lists files in the git repo. So what files are "open" in my session is irrelevant to my workflow. (Unless they have unsaved changes of course, but I basically always just use "Save All" so even that state is minimal.)
Might depend on your workflow. Let's say you are in a private feature branch. You do many commits, 1 per minute to create save points as you work on some mind bending logic.

You need those saves to go through no matter what, even when things are broken. You plan to squash all the feature commits when you are done so you don't care about the formatting quite as strongly for commits that will disappear soon anyway.
You would, but as someone who has interacted with all three big cloud providers at some level, and has seen demos using all three, and has colleagues that have had to do work and/or demos with all three... Azure is by far the worst.

Their security is the worst - they have had more than 10 critical security vulnerabilities, most of them cross-tenant, some of them trivial to exploit and should have never gotten into production, just over the past 2-3 years.

Their UX and docs are extremely bad. Not that AWS/GCP are perfect, but at least they're actually usable - the docs can be read and understood, and the UI and API don't take years to answer every single call.

As an anecdote, demos from their own Solutions Architects leave the impression everything is a slow disjointed mess. As another anecdote, I don't know any single Platform/Infra/SRE/DevOps/Cloud person that actually likes Azure, while I know lots of people who evangelise AWS/GCP for various reasons.

The main reason to go to Azure is because your bosses' boss was convinced to buy it at a golf course.
What local hardware is needed to run Bark AI? What is the quality? Looking for something as good or better than Eleven Labs.
The issue isn't that mongodb isn't suitable for some problems. I've used it before and it has not caused issues. It's that the problems it is suitable for are a subset of those that postgres is suitable for.

I can just as easily rapidly prototype in postgres. If I want to store schemaless JSON in postgres I can easily do that.

>In the end, I think it is good to have a selection of tools that are good at doing different things.

In the end I think every tool needs a niche - something it is good at that its competing tools are not good at.

Mongo doesnt have that.
Haven’t you just described a hypothesis? Hypotheses describe what you think will be the outcome of the research based on the researchers’ current observations and understanding of the world.

Scientists aren’t neutral observers standing outside the world. They have inherent biases and those biases shape the research that they conduct. It is both the scientific method and the scientific review process that are supposed to ensure, despite these biases, that the research was sound and the findings valid.
Yeah man, screw the VCs! That’s why we’re communicating through an open source platform… oh.

Well at least this site isn’t created by a VC… oh.

Things are nuanced. VCs can fund valuable useful things sometimes.
> Redict is a Finished Product

I am keenly looking on to see if the people involved in Redict see it the same way. As a user of Redis, I would like to switch to one of these open-source forks, and to be honest one which is "done" and focused on maintenance, bug fixes etc. rather than new features sounds more attractive.
> It links to identity of whoever purchased them with credit card.

How do you think this happens? The codes are not scanned at the shop.

> when transaction for these stamps was registered.

Where is this registered?
The crane requires wind? I don’t see that.
I'm building a storage engine.
GPL with CLA still allows such stunts.
The license change is only for future versions, though. The work already put in remains open source.
Monetization-era
I agree, buy playing devil's advocate, it's true that people without the time and expertise to setup their own install can find this packaging valuable enough to pay for it.

It would be better for all if, in Open Source fashion, this software had a FLOSS easy-to-install packaging that provided for basic use cases, and developers made money by adapting it to more specific use cases and toolchains.

(This one is not FLOSS in the classic sense, of course. The above would be valid for MIT-licensed or GPL models).
This has nothing to do with the license in question per se, and the GPL wouldn't help at all. It has to do with who owns the copyright. The copyright owner can re-license going forward to whatever they want, whenever they want. If you're really concerned about a license change then you need to be wary of projects with sole-ownership, either via CLA or not accepting contributions (it's the project of one person/company that they're putting out as open source for whatever reason, and very much not a community project).

I actually think the descriptive language commonly used here is a little distorting in that regard. A copyright owner does not, and cannot, "take something closed source", it's more that they're forking the project under a new license (which granted is a specific kind of fork only they can do, everyone else has to fork under the same license). Every single bit of code up until that moment remains under the open source license, so if there is interest customers or whomever else can take that and continue the same open source project going forward, and even surpass the original holder's new proprietary effort. As a practical matter that's rare because there has to be serious interest, but it does happen. OpenZFS for example is a wonderful project that has long since eclipsed the Oracle fork of Sun's code.

In turn I also think it is often a little more complex then (from the opinion):

>"switch licenses, leaving their contributors, customers, and partners in the lurch as they try to grab billions"

Let's be serious: rarely are these projects getting more then a token percentage of code from contributors, let alone anything else (though Redis definitely is). It's frequently 90%+ a single-company effort, and indeed this is nearly a truism. Because if the company is only a small component of the effort vs the community it is extremely likely any attempt to do a proprietary fork will fail and the open one comprising the majority of effort will dominate, and by definition there is major interest. This doesn't make it non-irritating, but it's still a net positive, a lot of useful code was contributed open and is a much easier springboard. And it's a much MUCH better situation then the even more common proprietary-all-along-software changing terms which happens all the friggin' time, like going subscription-only. If nothing else you get a much better off ramp.

Companies forking from open source to proprietary with their projects can suck, for sure. But I think in the last year it has started to also get a little overhyped. I'd still rather have years of open source first. And again, everyone can always evaluate who owns the copyrights. Diversity is important for longevity ANYWAY too. Like, if all the effort is happening by a few devs or a single company, what happens if they get hit by a bus? Go bankrupt? Simply get old and tired of it? At some point the community has to step up, or not.
It is not owned by the company. You are free to create your own fork of the code with all the attendant benefits, including monetization, if applicable.
Or “weak” licenses are used by people that don’t care about the things that the license allows for. Or better yet, actively want that degree of permissiveness.

All this license hubbub is often just people not actually thinking thriving which license they want to use. “MIT sounds like a pretty good university”.
Doubt anything at Boeing would have changed if everyone had state healthcare. These pernicious decisions weren't driven by healthcare at all. Younger employees can be more easily coerced to an executive's vision, forced to break compliance laws and also be paid lesser than senior folks.

This is the terrible rot of modern business culture - all driven by short-term profit making at the cost of long-term sustainability.
I wonder if Oregon is a small enough market that Apple just halts all sales in Oregon.
Actual title: "So, Should You Trust Andrew Huberman?"
I think it is even beyond this.

Most of the time humans are talking about the wonders of polywater to each other.

A giant game of telephone telling each other complete nonsense.

"The soviets have found a new form of water that freezes at –40°F, pass it on!".
Yeah, the title was easy enough to translate and mentioned in most English news, but I was disappointed that none of the articles (or anywhere else I could find on the internet) summarized the book's content.

That's definitely a bit more debatable, for thematic purposes as you said, but I think I (personally) would want some utility in the book (instead of a more artistic or philosophical work) to justify a skin cover.
I find the title and general feeling around this issue a bit exaggerated. SSPL license is indeed more restrictive but as far as I understand still allows internal usage of the software (without providing it externally "as a paid service").

I generally don't think everybody needs to push any point to the extreme (in this case, software licensing). For some a more restrictive license might be required (SSPL) while others can live with more open (BSD).

In the end, I would claim it is not "software vendors" that should drive most development, but rather "hackers" (passionate people that could potentially earn their living in different ways). Expecting "companies" to be the drivers of open source seems a bit idealistic today.