skysight-inc/HackerNews huggingface dataset:
I use an app called WaterMinder (it’s free, with a tipping option) that’s available for iPhone and Apple Watch. Whenever I drink some water (or water containing beverage), I just tap the app complication on the watch face and the appropriate water intake icon. You can configure different buttons/water volumes for a single-tap ease of use. Or you can tap on “Other” and then choose the kind of beverage and volume.

The app also has some adjustments on hydration percentages for different beverages (for example, if you drink black coffee, it will take 90% of the volume as water intake). You can even edit those values if you wish.

I track only the water I consume in beverages (including plain water), and don’t try to estimate the water contained in solid or cooked foods.
correct me if I'm wrong, but isn't the "P" in IP "property"?
It's great that you can do this, but why stuff this functionality into ssh-keygen? A command called ssh-keygen should only do one thing: generate keys. The command for using an ssh key to sign something should be ssh-sign, especially since one of the ostensible design goals here is to get away from PGP's horrible UI.
> SSH public keys are one line strings that are easy to copy around. You don't need to use the Web of Trust

PGP public keys you can also just copy around? Nobody is forcing you to use the web of trust with PGP either, if you don't want it. But if you do use keys extensively, it actually helps you: if your boss already verified a customer key, you don't have to re-do the work and meet up in person or ask your boss to send it over before you can use it. Now extend that to a whole network of colleagues, where you configure per-colleague whether you think they properly verify other people's keys, and this whole key distribution problem becomes a lot easier without having to rely on third parties (CA system like with https).

Just a small note, this obviously doesn't invalidate the rest of the article!
Is the USA a good example of good building practice? Wow frames, little foundations. Perhaps they could look externally. In fault zones across Europe there are already building regulations run place.
Nobody talks about undying loyalty. Government should not have any busuness regulating sending messages. Whoever is not happy with his work can just quit, it's not like someone is chained to his workplace these days in western countries. It's generally much harder to find qualified personnel than to find a good job.
How so? Obviously you can build an unsafe IPC mechanism with concurrent access, label it "safe" when it isn't, and then say "Look at this horrible mess, I blame Rust" but it seems like it'd be faster to just implement std::ops::Index unsafely and then blame Rust because thing[len+1] blew up even though Rust has "memory safety".

Now I'm going to write an amusing aside. One way you could get into this trouble is if your hardware allows arbitrary foreign memory writes as "IPC". The BBC microcomputer allowed this over the network! You could send a bunch of bytes over Econet (a 1980s network from Acorn Computers available for the BBC, Electron and Archimedes computers), addressed to another BBC micro on the network, asking they be written to a RAM buffer, and the remote hardware would do so. We used this to run a Multi-user Dungeon at school in about 1989 or so. A "server" ran the actual MUD software, and individual users signed in from a computer on the network around the school to play, when they typed a command their command buffer was transmitted over Econet, and then the server wrote remotely to their display RAM to show the result on their screen.

Fortunately your computer is not a BBC Microcomputer, and foreign processes do not (on the whole) get to scribble on your program's memory. So this should not be a problem unless you specifically make this unsafe decision in your Rust program.
Because that's the way a lot of people want it just in case they become less embarrassed millionaires some day. You can never be sure!

Silicon Valley is a nexus for this kind of thinking but at least there's a decent chance of doing that if you're not stupid about it and just spend a decade or two here jumping from one failed startup to another until one sticks. But be very careful, the virtue police here claim they don't like job hoppers (as they themselves jump from one position to another).

As long as you're an at-will employee you owe nothing more than at-will loyalty. Don't let anyone convince you otherwise unless they pony up the cash upfront.
It's still USB 2 speed!

"Lightning operates at the USB 2.0 speed of 480mbps, whilst USB-C works at 5gbps. Not only this, but USB-C is now used by a wide variety of devices, making charging much easier and more convenient."
Neutron transmission is not useful in any of these scenarios. Not in a fusion reactor because a fusion reactor produces a ton of neutrons itself, many orders of magnitude higher than any transmission you'd be able to make so it'd be drowned out (most neutron generators use fusion to produce neutrons too so they're probably also at similar energies to what the reactor makes). Plus the problem with the inside of a tokamak vessel is that it's a super extreme environment and not much can survive in there and like I said in another comment you still have to power your neutron generator.

Neutrons are also relatively short ranged and more-or-less isotropic in emission (not able to be focused effectively), meaning you need really high fluence (=dangerous) to transmit more than a few meters. For submarines, water actually attenuates neutrons extremely quickly making it completely useless there. And also let's not forget that neutrons activate materials and make them radioactive for long periods even after you stop with the neutrons. For totally sealed rooms there are better solutions (e.g an acoustic transducer). On top of all this, the physics of neutrons mean this will always be very low bandwidth.

None of the applications mentioned in the article are remotely credible, IMO, and this is my area of expertise. Perhaps there is some application where this is the best solution. My point is that at best it's extremely niche; the article makes it out like this is revolutionary but it is definitely not nor is it even particularly interesting. This is not military research with an intended application, this is someone slowly moving a block of plastic back and forth in front of a californium source in a university lab and a press release declaring victory. The actual article published by the scientists in NIM is much more reasonable, but the one linked here is greatly playing up the utility.

A fairly reasonable analogy that captures some of the downsides of using neutrons for this is that you could also transmit information by shooting at a metal plate with a pellet gun and having someone listen for the pinging sound. Sure it's possible, but the list of drawbacks is pretty long.
Zuckerberg does not belong in the same complimentary sentence as Newton. Newton pushed humanity forward, Zuckerberg is ripping society apart for money.
I honestly don't think Microsoft can compete in this market, which is a shame.

First, what would MS do? Follow the Google approach and make a platform or follow the Apple approach and make a full phone?

Google makes a platform, leaving the major handset makers to provide the hardware, UI, and support. Google is not really making a lot of money on that platform, it only makes money from the playstore - say $10 Billion/year. That's nothing to MS. One can argue that the Google apps installed in android phones make some more money (e.g. maps, search), but those apps are also installed on iPhones.

The amount of money involved in the platform game is not really worth it to Microsoft given the engineering required, and android is a market leader -- MS would make a small fraction of that.

Of course MS could try to charge a lot for its platform, but with android being (effectively) free, it's not clear how this would work.

So then MS could get into the phone business and be a real hardware company. Here, I just don't see them beating Apple. They don't design their own chips. They don't innovate as quickly. Job's famous quip that MS "has no taste" is still true, IMO. There was a reason they exited this market, and it was that they couldn't compete in it. Not sure which of their most recent moves into cloud would suggest that this has changed.
If you spent a few years of your life coming up with a new way of doing something, and a company saw the details of your idea and got to market before you and never acknowledged you or your work, leaving you with no way to earn a living from your idea, what would you call that? Should that be illegal?
Is there any actual data to makes this more valid?

Especially when currently Apple uses USB-C for their entire lineup with exception of iPhones and iPad 9th gen.
In this context we can exclude `trademark`. Also `copyright` is quite unlikely, too.

So it's probably mostly patent impingement.

And I think we all know how:

- large cooperation infringe on patents of
smaller ones without relevant consequences
all the time

- there is an endless number of complete absurd
patents wrt. software. The patent system in
context of software is fundamentally broken.

- due to the US patent system being even more broken
then the German one (was at the time the article
refers to) the infringed patent might not even have
been a valid patent.

But what of this points apply to this specific case I don't know.
Right; which is why the exit strategy in the enterprise software space is to get acquired by Oracle / SAP / Microsoft / Salesforce.
If someone owns 50% + 1, can they vote to have it displayed solely on their private property? If so, how exactly does this solve your goal of making it public? If not, what exactly does ownership mean?
> Index funds reduce the need to know about stocks.

And for that vast majority of people, whether they are expert or not, the index fund will outperform their personal stock picks anyway.

99% of the population only needs to know 'put it all in a vanguard S&P 500 fund' as their long-term investment advice, at least until they're old enough to see retirement on the horizon.
Intellectual Property is a dumb idea, a legacy of thousands of years of exclusive (physically unique) markets of goods (i.e. making copies is expensive).

Digital artifacts require a new non-exclusive property market scheme (to be determined; it's a difficult problem). Enforcing the older paradigm with laws and coercion is not a long term solution.
I wonder if, similar to automatically choosing alternate synonyms, small spelling errors throw off naive spam detectors while remaining perfectly readable?
More details here: https://constitutiondao.com/
Kopia supports compression:
https://kopia.io/
What does any NFT “ownership” mean?
I live in a city (Münster, Germany) that has extensive bike path infrastructure, but as far as I can tell, there is no established system for pedestrian crossings on bike paths other than "take care".

I would think that at a traffic light, bicycles should act the same as cars, but this just doesn‘t happen at all. I‘m lucky if bicyclists don‘t blast straight through a zebra crossing. It feels especially cruel for traffic lights that are placed between the bike path and street yet require a button press.

So it‘s two things: inconsiderate cyclists and and no common pedestrian crossing system on bike paths (or clarity on rules at existing street crossings).
The's a web speech standard so you can use tts in the browser without these services but Apple of course decided not to implement TTS for safari.
Yeah I read this and was like, "maybe say ZeniMax". I feel like they know what they're doing though.
There was recently an article/discussion on async in ruby:

https://news.ycombinator.com/item?id=29049881

And I think the example is a good one for how doing parallell io can be simple with async tasks/promises:

require "async"
require "open-uri"

Async do |task|
task.async do
URI.open("https://httpbin.org/delay/1.6")
end

task.async do
URI.open("https://httpbin.org/delay/1.6")
end
end

(completes in ~time of slowest request, not sum of requests).

Sure, one could use threads/processes/green threads etc.
And I'd be shocked if being a good academic had nothing to do with heritable traits.
Way before QNX went shared/open source, they were as they are now. But they had just released Neutrino a major update which basically took their QNX4 microkernel and mated it with a POSIX/GNU/UNIX-like userland. And it was for a while, free as in beer, for R&D type use.

So that all sounded great and we tried it, this was around 20 years ago. It was a disaster.

The same kind of shoddy work, race-condition, type bugs all over the place.

- malloc broken under heavy multi-threaded load. Replaced with dl-malloc.

- serial driver (16550) broke under heavy load. Wrote our own replacement.

- ethernet driver broke under heavy load. Had to replace intel cards with 3-com (or vice-versa) to use a different driver.

- had to write/rewrite several other drivers. Interestingly the only think I liked about QNX is that user mode drivers are very nice and easy to write.

- compiler, QNX bespoke port of GCC, crashed and broke on large codebases (could be because of malloc). Had to re-port GCC (which was easy) and build our own toolchains.

When we got done trying it our adamant report was GARBAGE NEVER USE. Got overrode by management. because we succeeded in making it work. Sigh. Started using it for products, so we bought commercial not-free license AND support. Reported all of the above bugs and 20 more, with reproducible test cases. QNX "promised to fix them in the next release". This was 20 years ago. Finally after many years we completed excising QNX from our products.

We never had a problem with ps, but it was probably broken. This company was producing garbage in the late nineties and didn't care. They produce garbage now. They didn't have enough or experienced enough developers to be trying to pull together a whole OS, so it was about how you'd expect a university or hobby project.

The only place this author got it wrong is that on QNX, if you assume the OS or compiler is at fault, you are probably right.
> Would you say the same thing about a password?

Passwords are secrets. Public keys are not. So the comparison doesn’t work.

> Would you make the same comment about a conversation over a messaging service?

If it was a public messaging service like HN, or public comments on Twitter or Facebook, then yes.

> This is a configuration detail of an account setting -- not a blog post.

We could be here all day and night saying what this is or isn’t but it doesn’t address the point I was making. The moment you create a GitHub account you start leaking far more sensitive data than your public keys. Data that is far harder to create anonymously (unlike your SSH keys). Thus if privacy is a concern then you shouldn’t be using GitHub in the first place. Even git version control itself leaks information about you.

> Privacy is not binary; there are many shades of grey.

Ironic you state that when you’re the one applying privacy in a binary way. I’m saying the SSH public keys are a lower risk than other details you share in GitHub. Not that it’s a zero or 100% bad thing, which is the only pidgin holes you’re allowing for this discussion.

> It is surprising that this is made public and while it is not necessarily wrong to provide this service (I'm fine with it; I see the utility) it is also reasonable to ask for a way to opt out.

That’s literally the point I’ve been making.
...I'll concede that one.
Yes, dedup of blocks :)
Did you win your case? I’m going through something similar and was about to give up hope based on advice from my lawyer, because he convinced me the company I’m up against would continue to appeal, easily justifying the legal expense to shareholders about “protecting the brand”. I’m willing to put in some time and effort to win, so maybe I should take my shot.
I know it's accurate, I had another domain on my machine that was sending email through my account, on accident, and Mailgun did nothing to stop it.
It used to be that way. Old data warehouses (built on relational dbs) couldn't handle large scale data, and old data lakes used to be hard to use (write a map-reduce job to query data).

It is barely true nowadays.
CW is "continuous waveform" not "code word" at least in the context of radio and is probably the only way this can work. You can't really modulate neutron energy/frequency with any sort of fine control, so most of the fancy techniques with radio waves are out. CDMA is sorta possible, but bandwidth is always gonna be low.
Breaking down the 'payment for order flow' debate
Well as a former cobol programmer, I would argue that it is no less verbose than pretty much any language.
No offense to your sister but the "first USB-C iPhone" might have a bit more novelty to it than her and tech collectors do like their novelty products.
I have a Makefile to invoke restic on just about every Linux machine I have (even Raspberry Pis), usually to do incremental backups to Azure blob storage. It is a great, no-fuss, “forever” tool I’ve relied upon for years, and has made it trivial to clone or restore some pretty weird setups.

Just mind you exclude node_modules and the like from it :)
So you agree with the court's assessment that the mandate's purpose was to "ramp up vaccine uptake by any means"?
Bitcoin Creator Satoshi Nakamoto Could Be Unmasked at 64B Florida Trial
For me, when learning a new language, there's a war in my brain between learning the thing and being productive. If I'm not productive long enough, I jet. It took me a couple of tries of bouncing off of Rust before it started clicking. I've written a few personal web projects in Rust and I'm still on the fence using it for those. My comparable Go web apps run just as fast with a little more memory usage, but are significantly faster to iterate on (compiler speed) and write, and also to read/understand later. The thing that has been tripping me up the most as an intermediate Rust programmer is that some library authors tend to get Architect Astronaut-y with the type system. It gives me the SimpleBeanFactoryAwareAspectInstanceFactory Java vibes.
It is nowhere near as simple as you make it out to be.

Yes, the freedesktop runtimes ship extensions with newer versions of Mesa and its dependencies. This doesn't entirely solve the problem. For one thing, libstdc++ before GCC 5 did not maintain a backwards-compatible ABI, so if the app was compiled too long ago it won't work with a new libstdc++. Steam is now working around this problem by using dlmopen() namespaces to load different version of libstdc++ into the same process. Flatpak is not there yet.

For another, NVidia drivers complicate this even more. The NVidia client-side library must exactly match the version of the loaded kernel module which Flatpak can't control. So NVidia drivers are broken out into yet another runtime extension, and it can't package these drivers due to licensing issues so it will dynamically download NVidia drivers to generate an extension on the fly. NVidia drivers also depend on libstdc++ by the way, another reason why static linking doesn't magically solve the problem.

On top of all this is just the massive complexity and maintenance burden of keeping all this working. All these runtimes with all their extensions, somebody has to keep updating these, and when a runtime is deprecated all of the software that was built for it is defunct. All of this can be solved just by keeping libraries backwards compatible and building for native Linux, not Flatpak or anything else.
konse bhasa mein likhe hai ye article?
Untersuchen sounds more like examining the details of how the software works (up to reverse engineering) to me, not market research.
Hacker News group-think is strong these days. Instead of bothering to stop and post a counter-reply, many just downvote like it's Reddit, and move on.

I've been a few times recently, whereas in the past my counter opinions would have kicked off interesting debate.
The house looks like it would survive, but the contents would be carbonized.

Most of the fire safety is probably just that they cut down the nearby trees.
Trouble is the NBBO is not really the best price you could get.
The irony of this statement is that from the immigrant's perspective, they are the ones whose salaries are being kept artificially low by restricting immigration.
Its no surprise that a core with a register file sized at 300+ would outperform a core with a register file of size 180. Significantly more parallelism can be found.

Apple's main risk was deciding that such large register files were in fact useful to somebody.
> its really strange that there are two languages running around together.

Mmh, I'm not sure I would agree with that. I've been using Arc & Rc for both async and non-async code, and even in single-threaded code. It's less about what flavor of concurrency you're using, than what program you're writing.

Arcs and references can coexist and are useful for different reasons. It would be a tragic loss for me if the language was (re-)adopting garbage collection or reference counting globally -even optionally. They are made to go along one another.

Edit: for example, tree-like or graph-like structures can use Arc and Weak [see arc documentation] in single-threaded code to enjoy reference-counted, cyclic, heap allocations in order to store a reference to a parent or sibling node.

You can do that with boxes, but Arcs have benefits if you want your code to work in a multithreaded environment.
Why is this called "higher math"? It mostly covers high-school calculus and physics. And how would you call more advanced math?
I've used restic for over four years. It's been rock solid on all platforms (mac/windows/linux). I've set it up on everything from beefy linux servers to 10 year old Windows machines (scheduled job running for 3+ years, pruning on a separate machine, never had any problems). The support for B2 and S3 compatible backends as well as rclone makes it a breeze to set up. The community and maintainers are also very friendly and helpful. Highly recommended!
> Think, charging on a red eye flight.

https://www.cntraveler.com/story/jetblue-mint-suite-business...

https://www.businessinsider.com/inside-qatar-airways-busines...

https://www.astronics.com/aircraft-in-seat-power/wireless-ch...

A matter of time before this becomes super common. It's a low-cost perk that provides a service previously not available: a free charger while on the plane. And in the meanwhile, see below.

> Using a power bank for a long hike/camping.

Plenty of power banks with wireless chargers. I use Anker's own myself, works well. Also can be used as a regular charging pod when simultaneously connected to a power source.

> Quick charge in the morning when you forgot to charge the previous night, etc.

Fast wireless charging is already a thing. Besides, if you drive, you can charge it while driving, too.

The minute public space, business offices, car and regular furniture with wireless chargers built-in become common, it will be a non-issue all of the sudden.

However, I reckon it's still a matter of 5 more years, and doubt Apple can hold-off having to switch iPhone to USB-C until then.
I use rsync to backup my desktop (which is mostly used for development) pretty much just rsync /home to a big enough external LUKS drive.

Has saved my bacon a few times, I don't care about incremental snapshots or delta's (though I've used both rsnapshot and rdiff successfully in the past), I'm covering the "if the SSD blows up, how long to chuck a new one in and be back up" case not the "I might need that file from 6mths ago".

I also have syncthing setup via /home/<user>/Shared/{Personal,Work}/ on every machine and important stuff I just chuck in Shared/ and forget about/it's available wherever I need it at any point.

I've had really ornate bulletproof snapshot based backups but honestly for my particular use case they where more hassle than they were worth, rsync does what I want every time and has never let me down.
I think DeWitt Clause is good for the users