Hacker Newsnew | past | comments | ask | show | jobs | submit | xnzakg's commentslogin

> they are all reactive such that they must be given a task before they will do anything.

Isn't that just because that's what they're being trained on though?

Wonder what you would get if the training data, instead of being task based, would consist of "wanting" to do something "on someone's own initiative".

Of course then one could argue it's just following a task of "doing things on its own initiative"...


Neither this nor the blog post explains what this feature is actually supposed to do?


Also interested in this, but haven't tried it myself. Apparently NSF (Nano Silver Fluoride) is more commonly in non-western countries.

They have a video with some more info here: https://pt.fourthievesvinegar.org/w/9aa66b49-2ec5-497f-9f49-...

And apparently the use of NSF does have a bunch of research papers written about it: https://www.researchgate.net/profile/Amol-Patil-43/publicati...



...or you can just give someone a "smart" device that requires then to install an app with lots of unnecessary permissions to use it.


> Tastes like bullshit to me.

Does it really? In my opinion, if it stops working and it's under warranty, why not send it out for repair? They did no changes to the actual device, and apparently it was working fine for a few days without network connection, so if it suddenly stops working and it's under warranty that's the manufacturer's/store's problem, not theirs. Trying to fix it/reverse engineer it takes time, and I can see someone with these kinds of skills wanting to spend it on something else than trying to figure out how the manufacturer bricked their vacuum.

In addition, _someone_ is paying for the repairs under warranty, so if enough people were to do it, hopefully it would disincentivize completely blocking devices just because they can't reach a server.


Author here: I did send it send the device for repair repeatedly like 4 times until the warranty ended and the company charged me huge. So decided to spend time on it. I am usually interested in knowing how my devices work so I couldn't resist. Leaving a bricked device at home was one option, learn from it was another, so I picked the second.


You can always put some extra protection on the external interfaces. Won't make it impossible to fry if you really do something stupid but would reduce the risk significantly.


Hasn't stopped a lot of companies from selling out and then being ran into the ground by their new owners.


Seedboxes often have TBs of storage for relatively cheap.


Roon seems great but the pricing is really steep in my opinion... Costs practically as much as a streaming service, but you still need to get your own music.

At least they have a lifetime purchase option, though it costs $830!


It is not cheap, but it is clearly made by people who care about music. In those days where "slop" is so common, for people who can afford it, it is a nice refresher.

Another minor inconvenience is that it is memory hungry for large libraries. In my case, for ~1 TB of flac, the docker takes 5-6 GB RAM on my debian NAS. Limiting it at 4 GB definitely crashed w/ OOM, at 8Gb never had issue.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: