throwaway_ocr

Pretty frustrating when you find a word, but it's not THE word. Pretty fun otherwise.

In 95 localization was scarce. Also, the partial "inst" would have matched "install" translated to several languages (about 15 by my quick count, could be more).

X.400 is still in use today for things like sending invoices and orders through EDI.

Yes, it is a pain to manage. Yes, it is all still mostly running on 20+-year-old hardware and software.

It is slightly ironic that the main way we communicate X.400 addresses between parties is through modern email.

In addition to all the sensible reasons others have pointed out, if you crash at a high enough speed without a seatbelt you become a projectile. If you are in the back seat when this happens, you are most certainly a danger to those in the front seats.

If the seatbelt saves your life from an accident in which you were at fault, it is easier to prosecute and extract compensation from the living than from the dead.

Atheism would fit the definition of absence of a belief system.

In the incident case, it's a post-mortem on the incident. The incident itself is (hopefully) resolved and can now be dissected to learn about what went wrong and how things can improve in the future.

That's what a post-mortem implies to me in the tech industry. A thing happened, it's over now, here are the lessons we learned to take into the future.

Sorry, what do you mean by this? Back button seems to work normally for me.

Wouldn't the obvious solution to this problem to stop using agents that don't respect your usage limits instead of trying to build sketchy containers around misbehaving software?

The downside to doing this is that you'll sound like an LLM. LLM-generated text is very obvious to anyone with basic reading comprehension and once detected will cause some people to summarily dismiss the sender as a bot.

I tried "show me Portugal" and it showed me Madeira, which is an island that is indeed part of Portugal, but I was expecting it to go for the mainland.

Repeating the prompt alternates between Madeira and Açores which is again, technically correct, but in this case not the best kind of correct.

The thing I don't understand is the concept "majority" in the crypto space. There is no way to prove that one person doesn't control the majority of the voting power. If I own a large portion of the supply split across several hundred wallets and I vote one way, smaller owners may be influenced by the appearance of hundreds of votes being cast one way vs the other. We see this in the real world, where some people are willing to just vote for what they think is the majority sentiment when they don't have strong opinions on a matter.

I've heard arguments along the lines of "those with more invested into the project should have more voting power" but that to me just sounds like an incentive to centralize.

If I'm a small player, I either go with the majority or see my investment become worthless, or in a fantasy world where crypto is used for anything other than wild speculation, I see my utility greatly diminished as I'm no longer able to interact with the "majority". Sure, I might still be able to interact with those left behind, but the pressure to move over to the majority fork is going to pull more and more people towards that.

I see federation of content as a much more approachable means to re-decentralization of the internet.

We still rely on centralized DNS. As we still rely on ISPs to make sure our packets can leave our local networks, and on international treaties to make sure we can communicate with networks in other countries, but unless you want everyone to start developing and maintaining a decentralized physical computer network for free, we'll always need to trust a number of institutions to do this thing where we can communicate with someone on the other side of the world within a few milliseconds.

The whole argument falls apart for me when it's acceptable to 404 when an api version isn't found, while it's not acceptable to 404 when an employee isn't found.

Why would we handle not finding an employee differently from not finding an API version?

If we're saying employees/100 should return 200 because it "could" exist, but doesn't at the moment, then why would we ever return anything other than 200? Any route "could" come to exist at a future point.

Instead of regulating whatever social media platform happens to be trendy at the time, your anecdote suggests we should regulate companies so that they offer direct support through conventional means, rather than exclusively through third parties.

When you're unable to "just eat less", it's important to figure out what to eat. One trick I've learned is to substitute all of your snacking with Lupin beans. Every time I get those stomach growls between meals, I just eat a handful of them. They're basically just fiber and protein.

They're also delicious. They're usually sold in a brine, which you'll want to switch out for fresh water at least once to lower the salt content.

Same thing I've always used it for, talking to people I play games with.

Teamspeak never stopped working so there was never a reason to switch to anything else.

A multi-select box for this would be nice. Select2 should be easy enough to implement, as you're already using jquery.

I tested this by taking a screenshot of the introduction blurb. This is what it came up with:

  Tesseract s is 2 pure Javascript port of the popular Tesseract OCR engine.

  This library supports more than 100 languages, automatic text orientation and script detection, a simple interface for reading paragraph, word, and character bounding boxes. Tesseract s can run either in 2 browser znd on & server with NodeJS.

Not bad, but far from useful.