HN user

marklar423

281 karma

hn at nakmail.net

Posts3
Comments93
View on HN
Waymo Premier 1 month ago

I've always understood it as a perk the company knowingly allows its employees who need to travel.

Maybe I'm splitting hairs, but GP called it a copyright violation and my understanding is a "clean room" reverse engineering for interoperability was fair use and not a copyright violation.

Yes this does threaten Blizzard's business model so I understand why they'll go after Turtle, but that doesn't mean we have to care or let them prosecute Turtle for Contempt of Business Model.

Now, if Turtle used Blizzard's WoW trademarks to advertise and make money, I fully agree that violates their _trademarks_ and can be litigated as such. But if Turtle somehow didn't do that (and still sold access to their compatible WoW backend), I'd be interested to hear if that is somehow still a copyright violation.

In the discussion of the Triforce arcade compatibility, there's some discussion of "IC Card" support needing to be implemented, and doing so unlocking a lot of missing functionality.

I think this is referring to the Japanese rail payment cards? I know you can use them on things like vending machines, but from the article it seems like the Triforce cabinets let you save game progress on them too, which would be a great feature I've never seen in US arcades.

IIUC, if you have the source you can recompile said Windows app with LiteBox to statically link in the Windows OS kernel dependencies, so it'll run on any compatible processor regardless of OS (since it won't be making syscalls anymore). It's a unikernel basically.

That's the theory, but I don't know how far LiteBox is along to supporting that workflow.

iPhone dumbphone 11 months ago

Yes it's exactly the one-off situations like that, which aren't super often but occur enough to greatly inconvenience someone without a pocket browser.

iPhone dumbphone 11 months ago

I've been trying to do this too - paring down distracting apps, leaving only essentials like communication, maps, uber, etc. But my problem is what to do about the browser? I feel it's too essential to the "long tail" of uses (as the author put it), but also among the most distracting apps on my phone.

If anybody has any ideas I'd love to hear them.

Here's how I think about it:

- Money (the concept) is useful to society as a store of value, so you don't have to waste effort bartering for things.

- Adding on to that, credit is useful to society since it lets humanity even more efficiently allocate its good and labor (stored as money).

- Finally, stocks, insurance, and other financial instruments are additional advanced developments on top of credit, where groups of humans (companies) can take on even more risky endeavors supported by investors or insurers.

So my view is companies like Jane Street facilitate these complicated value transfers, to let (e.g.) a spaceship company draw on resources generated by growing crops, selling shoes, giving haircuts, etc via a convoluted path through stocks, ETFs, whatever.

I think Git was initially more popular and that had compounding effects that made it eclipse Mercurial.

In 2010 or so we tried to adopt Mercurial at the small company I worked at, but the support for Git was just so much better - even back then. Git's popularity meant that tooling, documentation, and general ease of finding people to ask questions was 100x easier with Git, so we switched. I'd imagine the same thing played out many times over.

A few FAANGs did and still use Mercurial, but they're on their own islands and don't really affect the wider tech ecosystem.

I'm self hosting Readeck (https://readeck.org/en/) and I really like it. It's nicer than Pocket was, the website extraction seems to work better, and it can't ever be shut down.

For my Kobo, I wrote a mod that lets me redirect Pocket API requests, and a small proxy server that translates Pocket API calls into Readeck calls.

So far it's working flawlessly and my Kobo is using its built in Pocket viewer for Readeck instead. I'm hoping to open source it soon so others can use it.

My company moved EiBs of data off of tape a few years ago. It was reliable and durable, but the problem was read speed.

It took so long to move tapes around and read the sequentially (no random access!), and as the data corpus grew it got harder to have a practical backup, even though the data was still theoretically extant.

It's funny, I noticed I happening and thought it was proof of the opposite - that there had to be some artificial cause for the supernovae (including the Sun), because a real supernova takes many years to progress, not 20 minutes.

Even after visiting the Sun Station I didn't believe it and thought it was a narrative red herring....so the ending was a surprise to me. Somehow.

Bad at Computers 1 year ago

Good article, I think this succinctly says what I've struggled to explain to my own relatives:

The vast majority of people do not know what a Kubernetes is; 99% my skills and knowledge are completely unnecessary to be Good At Computers. Turn it off and on, click suspicious UI button, plug in cable, open Google – these are the only requirements of the job.

However, the bits about Tensorflow and nmap makes me lean a tad towards https://xkcd.com/2501/. I think it's hard to tell exactly where the line between Good and Bad At Computers is.

Kobo is definitely superior to Kindle in my book. The hardware is great and it's completely open to sideloading and even modding (it runs Linux under the hood).

I can't speak to their digital bookstore but they integrate with Overdrive for library borrowing.

I worked on a large makeup website for a while, and it was common for us to place test orders and subsequently cancel them. The dev doing it usually put their name and the office address as the shipping address.

One day, we got a big box of makeup at the office - turns out their warehouse had gotten so fast that in the time it took us to cancel the order they had already picked & shipped it.

After that we put "TEST DO NOT SHIP TEST DO NOT SHIP" as the shipping name and "123 Fake St" as the address to try and avert this scenario, which seemed to work until we could modify the system to hide those orders from the warehouse entirely.