skysight-inc/HackerNews huggingface dataset:
Of course we should just give up and give all our data to anyone who wants it, lest we burden the developers in any way.
Not really necessary if the client can connect to multiple servers.
The CA can't solve it for you.

The certificate authority signs certificate requests, creating certificates. The revocation process is necessary as well, but the CA doesn't have the ability to change the already issued certificate, thus it cannot take action.

A software like certbot can solve it for you, but that's not affiliated with your CA
I think this post was supposed to link to the newer draft (June 20). I'm not sure how different it is (their diff tool didn't work for me).
This is disingenuous considering there's plenty of Lemmy servers that aren't federated. Just because a thing supports federation doesn't mean it must be federated.

If Revolt supported federation it would be trivial to just turn that feature off if you had privacy concerns in that regards.
For a number of weeks HE tunnel users have being reporting packet loss, it's thought this might be due to abuse.
I started self-hosting Miniflux as a New Year’s resolution. Very simple layout & integrates with Newsboat.
> thinking that the hot new tool X or architecture Y is going to solve all of the problems

Wanting to use X and Y and finding a way to shoehorn them into usefulness is called "motivated reasoning." Does that look any different from "coming from a good place?" Heck, it could be both motivated reasoning and coming from a good place.
Callbacks are no more 'what actually happens' than coroutines are; what actually happens involves a lot of jumping to memory addresses, and closure state is just as much a compiler invention as async/await. Blocking-style code, by comparison, is how we actually think about the business logic; language features that abstract over callback hell to let you write it make code inherently more clear. People always say it because it's true.
In practical terms there's pros & cons I guess, but in general doesn't loading a Context with session variables make code more concise and easier to understand ? DB connections, loggers, and the like. If you really want to pass around Context's in all your API signatures then at least try to make the most of it.

Are pitfalls ever actually encountered ?
'I moved to a country where I have zero family, but even here I have friends I could stay with if I ended up being unable to pay the rent.'

Not parent post but...

Imagine a scenario where friends and family are the last people on Earth you are going to ask for help. Not everyone is of the same mindset you describe.

Pride, mental health issues, family history, etc all play a part. I was homeless once, a combination of these things is what stopped me asking for help.

I have relatives who are regulars on the Sunday Times Rich List, some good loyal friends and 3 siblings. Go figure.
Not at all. Shielding against what? It's light. You only need enough of a protective coat to make sure it's stiff enough to not twist and stretch too much and to make it neutrally buoyant. No repeaters needed, base range is about 40-60 km. ROVs going to greater depths use them all the time without major issues.

The real reason is that they were stingy as fuck and that it's mildly impractical which outweighed their complete disregard for safety.
> You just compile them

I can't tell if you're being sarcastic or not.
Okay, I'll amend my statement: no one should be using a WASM-powered Postgres as their production DB.

Right now compiling to WASM is sort of the equivalent of "but will it run Doom?" People are doing it for everything, and it's a fun experiment to stretch WASM. I could see it being useful in making some things available in the browser that otherwise couldn't be. But that doesn't mean it's going to replace containers in their rightful place. It'll be another option, and unless you're trying to solve one of the few problems that WASM was designed to solve (like running in the browser), it will be the wrong one.
"Any headline that ends in a question mark can be answered by the word no."

i worked in many different companies (including multi-billion revenue per year), and all of them used centos in order to have "proper enterprise linux" but for free. The only cases when real redhat was used is for something that actually required it by licensing/support terms - like Oracle, or alternatively contractual obligations for SLA.

Pretty sure that IBM/Redhat know this as well and "third party open source packages compatability" not exactly something that they care about. Availability of sources only takes business from them.

I personally somewhat happy about it. I moved to Debian 20 years ago and it "uncomfortable" to live in RH derived world. Even though Redhat 4 (or 4.1) was first ever Linux distribution that I installed back in 1997

PS. Also when RedHat "partnered" with CentOS back in 2014, it was somewhat obvious what is the direction. If there is anything that it surprising, then it will be that it took so much time.
Do you have any particularl inside info on this other than what you’ve read in the news over the last couple of days? They’re pretty strong accusations you're making.
Every chance I get I try to promote the Cahill-Keys projection. Not only does it better preserve area and reminds you that the earth is a sphere, it is also one of the more esthetically pleasing projections out there.

https://en.m.wikipedia.org/wiki/Cahill%E2%80%93Keyes_project...
Smallest chess engine in 288 bytes: https://leanchess.github.io/
Can you elaborate why a market cap of 2.2 billion makes SUSE not a viable alternative? If anything, this makes me feel like they're undervalued, especially now that they're the only company shipping an enterprise linux with an open source and privacy respecting (looking at you Canonical) base distro.
> when I presume there is camera footage of it available.

Not sure if this is sarcasm...
If a project has toxic people in it, will a CoC make them into pleasant people? Will they drop all those people from the project after they adopt the CoC? What if it's the leadership that's toxic? If the leadership on the project wasn't toxic, why didn't they drop the toxic people earlier? What about a CoC helps them do it now?
So we have to be the smartest because it's been 3 months we are investigating an issue :D
wasm literally came out of asm.js and browsers. And its original goal is literally to make stuff in browsers more performant compared to Javascript.

So when people say stuff like "high-performance latency-sensitive use cases are applicable to wasm" they clearly only understand performance and latency in comparison to Javascript.
And default off, for privacy.
Isn't that how git is designed to be?
That was fun, I scored lower (2.1) dogmatism and higher on the test (840), which they claim supports their hypothesis.

In day to day life the major difference I notice in terms of speed and intelligence personally is that I'm often slow to respond to questions.

It didn't even occur to me to be self-conscious about this until eventually a friend pointed it out, but he kindly framed it as "you think before you speak" and this seems to have served me well.
Translation:

"50 year old white guys have a lot of experience but would cost a fuck ton of money. I prefer to exploit, er, um, employ, 25 year old white guys and gals because they are about 1/4 the cost."

When you take all the BS justifications out of it, that's really what the guy was saying. Elon Musk school of capitalism. Play stupid games, win stupid prizes.
Henry Petroski, Whose Books Decoded Engineering, Dies at 81
It's the government's job to regulate people not being allowed to pay for trips to the bottom of the ocean in submarines that look like they were built on Linus Tech Tips.
It appears that you hold the belief that extracting revenue and information from users is an essential aspect of software usage. However, I beg to differ, and I shall explain why.

Firstly, the notion that people cannot use software without the vendor incessantly monitoring their activities is far from accurate. It is indeed preposterous to assume that every user action must be surveilled and recorded. In fact, respecting users' privacy and allowing them to have control over their data should be fundamental principles of any software. Rather than exploiting users for financial gain, we should strive to create software that empowers individuals and respects their rights.

As for your claim that your terminal is the first of its kind, and no libraries exist to accomplish the tasks you mention, it is important to note that innovation builds upon existing technologies. Many robust and efficient libraries exist that enable a wide range of functionalities. Instead of reinventing the wheel, it is more prudent to leverage and contribute to the existing open source community, which encourages collaboration and knowledge sharing.

Regarding the assertion that your terminal is "AI-powered" solely for the purpose of capturing keystrokes and collecting user information, I must express my deep concerns. Transparency and informed consent are crucial in any software endeavor. Users should have full awareness of the data being collected, how it is used, and the potential implications for their privacy. It is unacceptable to exploit the AI buzzword to justify invasive surveillance practices without providing any tangible benefits to the user.

Lastly, the assumption that a company cannot be profitable without coercing users to log in reflects a narrow perspective on business models. While some companies may adopt such tactics, there are numerous successful alternatives that prioritize user trust, value creation, and fair pricing. A sustainable and ethical approach to business involves offering products and services that genuinely benefit users and respecting their privacy choices.

In conclusion, it is essential to shift our mindset away from viewing users as mere sources of revenue and data to be exploited. Let us instead focus on creating software that respects privacy, empowers individuals, and fosters a culture of openness, collaboration, and user-centricity. Only then can we truly advance the field of technology while upholding the values and principles that benefit society as a whole.
https://archive.is/JohMZ
Well, the morbid silver lining I guess, I was watching an interview with some expert earlier in the week, and he said if it developed a leak at those pressures, it'd implode and they'd all be dead before they even knew it.

For me at least, that'd be much more preferable than being stranded in a tiny box with no hope, waiting to die.
> why use containers ? You can just ship VM images.

Lower overhead.

> clever hack to get existing apps packaged up and reduce the overhead of VMs

Yeah, exactly.
To be more precise, if you wanted an isolated process, docker already gives you that. Along with the overhead of spinning up a new process for every request you want to handle.

What wasm people seem to be interested in is to eliminate the process (and hence a language runtime) spawning overhead, and directly execute the specific function of your application..

"Write your serverless function in any wasm compilable language and our multi tenant runtime can host 1000s of such functions and invoke them without much delay"..

Of course, that only makes sense for programs which are written in wasm compilable language. When they do crazy things like running js scripts on top of a quickjs interpreter compiled to wasm to run on top of a wasm interpreter "for portability and safety", it gets weird to see the benefits..
The watch prevents me from reading the internet. While still remaining connected to the world through SMS and calls and purpose-apps. The watch allows people to un-nerdify.
A few other notes from the USCG statement:

- No noises were heard during rescue operation (the implosion likely happened around the time the communication was lost, as opposed to in the days following)

- The "banging" noises discussed earlier were unrelated to the submersible.
Right, but that trick also isn't new. emacs was doing it decades ago and there are JVMs that also do it. That's how GraalVM native images can start and run faster than C programs do: the app is initialized at build time and then the state is just mmapped into a pre-compiled native process.

HotSpot has a less aggressive version of this where you can pre-initialize a lot of VM state and dump it to a file for faster startup time. It's about a 30% win and that's going up over time, but it doesn't AOT compile everything.

Of course, if you're serious about instant startup from zero then you end up going the native-image route, but then what value is WASM adding? What's being shipped to the edge in that case is a compiled binary anyway.

There is some scope here for threading the needle - for example, an edge worker implementation could be given compiled bytecode of some kind and then do the compilation and dumping process server side. This is a bit like how Apple compiled LLVM bitcode itself for delivery. However then the build process needs to be sandboxed and at that point why not go full FaaS and let users upload whatever binaries they like? AWS is doing it successfully.
True, but you still won’t get a coherent picture of someone picking their nose I bet.
As I said most of this is subjective so I won’t disagree but:

> copying similar code over and over

This isn’t true. Svelte is more than capable of reusing code internally.
Deadly Fungal Infections Confound Doctors–‘It’s Going to Get Worse’
I don't know. But sea water isn't a homogeneous medium as far as sound propagation is concerned. There are layers of changing salinity, temperature etc and these can effectively cut off sound propagation. Submarines (used to?) depend on such effects to avoid detection.

Also, would the implosion necessarily be that loud? It would be like crushing a large tin really. Maybe blends in with background noise.
See also White Rabbit Project, i.e. how to synchronize clocks over the internet with sub-ns accuracy https://en.wikipedia.org/wiki/White_Rabbit_Project
> Who knew that 60 to 70 percent of employee's time was mostly just BS

A lot of it is software industry's fault.

Think back to all those office jobs that got eliminated by software in the past 50 years. Like secretaries, in-house art departments, ${whatever the people distributing internal memos around the office were called}, etc. The jobs may be gone, but their tasks didn't disappear. Instead, they were smeared out over the remaining workforce.

How much time a week each of us spends on trying to sync up meetings with different teams, writing reports, preparing slides, managing our mailbox and calendar - or all the other tasks that are not the actual thing we are specialized in? All those things were done by in-house specialists, and like with all specialized jobs, those people were much more efficient at it. Now, they're gone, while we're left doing their jobs on top of our own, and suffering a huge context-switching penalty on top of it.

I'm increasingly convinced that most of the savings software brought to office work is just an accounting trick. The secretaries, in-house graphics teams, etc. all took salaries, which were clearly visible on company balance sheets. In comes the software, out these people go, their responsibilities get distributed between all the remaining employees - suddenly, the salaries for those specialists disappear from the balance sheets, while the company... it feels like it experiences an unexplained, broad productivity drop. A great mystery. Is it because Feds are messing with interest rates? Is it because some "cost diseases"? Who knows? Doesn't matter - it looks like a global thing, so it doesn't show on the balance sheets.

If Large Language Models are going to automate away all those BS tasks we've been doing, what's really happening is that they're finally materializing the gains that regular office software promised to deliver, while it in fact made things worse.

(Exercise for the reader: based on the above, think about websites and apps enabling "self-service", and consider if, as individuals, we're really gaining much by being made to do for free the work that used to be someone else's job.)
I would estimate the chances of that sub not making it back to the surface at least 10%. The carbon fiber hull concept has me seriously worried, especially if the goal is repeated use of the same hull. Everybody seems to be focusing on the electronics and the UI, I don't see those as particularly problematic if the hull stays in one piece. But if it doesn't then none of the rest matters. Given the debris field the chances are better than even that the sub did implode.

Repeatedly cycling carbon fiber in compression is a bad idea, and a CEO that throws out the rulebook and shows a very cavalier attitude to safety is fine if it is just you on board but with paying passengers it is utterly irresponsible.
What are the differences? Who runs these instances? Is there any moderation, or is it just the messy wild west?
Hi, do you have SaaS version? Is it free and how can I start using it?
Wishful thinking, they were hoping for another Thai cave drama that would drive big engagement.
The title of the article should be "People with higher intelligence scores take longer to solve complex problems".

Let's say that I define being very intelligent as being able to rapidly solve hard problems. I think this is a reasonable definition of the word "intelligent". Indeed, I think that it is in many ways a more meaningful definition of "intelligence" than defining it as scoring well on intelligence tests.

Well, then the article title becomes self-contradictory.
All the CoC drama is at least as abrasive and much more insidious in its community divisions.
Brings up memories of trying to run the HoloLens 1 on job sites in the northeast during the summer. Standing in the shade, you could get an hour out of it. Step into direct sunlight, power's off in minutes until it can sit in the A/C.
"transpiration"; is this the perspiration one gets when trying to use the JavaScript toolchain to transpile code?
The main problem with steel is that it can only withstand such pressures if it's of spherical shape (i.e. a bathysphere). This usually only leaves enough room for two to three people (e.g. https://en.wikipedia.org/wiki/DSV_Alvin).

So it seems it's more a matter of cost and passenger space than just weight alone.
What can we learn?

Just because the CEO is on the firing line with you, doesn't make him right, just overly confident.

DO hire "50 year old" people with experience, not just kids from university.

Don't build your pressure vessel out of materials which are hard to monitor for wear and fatigue.

Listen to your experienced employees when they tell you that you've built a death-trap.

If you have $250,000 to spend on a short vacation, maybe pick one with better odds of getting home.

and finally...

...The media will always stretch out the agony of these stories for as long as it generates clicks.
> freedom money can buy as it relates to your work.

> power of money resides in its ability to provide a better life for our families.

I really hate this mentality, it sees money as power to buy freedom and eventually to "buy family".

For me the key is to minimize expenses to some reasonable minimum. It does not matter how much I make, it does not affect my lifestyle much. Maybe I would buy a nicer laptop. I gave up on being slave to money long time ago.

That includes being a slave to family! I am open to serious relationship, but most people think I am cheap bum. I have no reason to change their opinions!
Sub debris found: The tail cone of the submersible was found approximately 1,600 feet from the bow of the Titanic on the sea floor, the US Coast Guard said Thursday. Officials said it was consistent with a "catastrophic loss of the pressure chamber."
Of course they are...I'm sure you've seen the dozens of marketing videos of tesla detection cameras/sensors stopping short for a kid chasing a ball into the street.

now, like anything else, does test/staging translate to production? Not even remotely. Automomous vehicle manufacturers claim to be in a monitoring/production phase to compare to their internal testing/staging. And over time we'll normalize Autonomous driving and the associated risks.

We used to drive all the nails in the world with a hammer precariously aiming at your own hand.
Reddit in addition to unpaid wardens also has a god-emperor pushing for enshittification of the platform.

Not quite the same thing.
Based on the experience I had with their support (covered by a support contract), it must be 1.
Owner of the purposefully controversial opinion here :) Looks like its proven to be very controversial, which was the stated goal of the podcast segment :)

For context, I had just returned from KubeCon + CloudNativeCon EU in Amsterdam. I had a chance to talk to many of the great folks pushing the WASM ecosystem forward, and there certainly seemed to be a large amount of momentum behind using WASM in the server space and at the edge. I'd had a great time learning from the folks at various open-source projects / companies pushing WASM forward:

- https://bytecodealliance.org/ (shout out to Bailey)

- https://cosmonic.com/

- https://www.fermyon.com/

- https://wasmcloud.com/

At DevCycle we are using WASM to help share core Feature Flag decisioning code across our Cloudflare Worker APIs and our server SDKs for local decisioning. We've learned a bunch about compatibility / optimizing performance / limitations that I'm happy to chat about in more detail. But we are generally excited for the future of WASM, especially for the new features coming: Component Model / Threading / Garbage Collection changes / Networking.

If you are looking for how to use WASM Components to replace container-based runtimes, look at the companies linked above.
Wow, could be a Musk quote. Same vibes of 'break things fast'.

EDIT: "Hide yo kids, hide yo wife; the karma snatching Tesla fanbois are rife"
US Coast Guard: The pilot and 4 passengers of the Titan submersible are dead
shameless piggybacking
Svelte MPA now using Svelte 4
https://github.com/kokizzu/svelte-mpa
Corporate brain fucking up yet another formerly admired organization.

RIP Redhat. And fuck you, IBM.
What's not deliberate about marking a function as `async`, and marking calls that need to be awaited with `await`?

Callback hell? When was the last time you gave an honest effort into JavaScript?
Just thinking about that outcome yesterday caused my blood pressure to skyrocket. Dark, cold, cramped, fetid, hungry, thirsty, knowing oxygen is running out.
When you fire up a VM that runs a container that runs Windows in a VM
Interesting, do you know if this is limited to a specific endpoint?
In addition, note that despite losing contact while the sub was on its way down, they did not report it missing until it was overdue after the full mission length.

That indicates a certain blase, routine attitude to communication loss.
Carbon fiber composites are a wet noodle in compression. They're supposed to be used under tension.

Hopefully this is the last time anyone tries to make a negative pressure vessel out of carbon fiber.
> You're only committing perjury if you falsely assert that you're authorised to act on behalf of the owner of the allegedly infringed right.

The courts don't care about that either. In at least one of the cases against ISPs (cox I think) the RIAA sent a large number of DMCA notices for works they didn't even own the copyrights to. After years of work the ISP's lawyers found a bunch of them and told the court who did reduce the damages they were on the hook for to account for the invalid DMCA notices but the court took no action whatsoever against the RIAA for sending them.
> No idea why every single journalist kept forcing the "air remaining" theme.

To keep viewers engaged in the search I'd imagine
The entire rescue operation had to be premised on the concept of the thing possibly remaining intact.