I played around a bit with the Hp-16c JRPN emulator for hex calculations and usefulness was limited by max number size. Largest number I can input is 0xFFFF.

Does anyone know if the SwissMicro models support operating on larger numbers than 16 bits, ideally up to 64?

I guess this could be fun for people using shared VPN and proxy services

Heh, I never thought about that, but it's true.

Ushering in the Silk Road 2.0 haha

Let's hope this not end with me taken away in handcuffs, lol :)

Once upon a beginning I believe assbly actually had human authors and readers in mind.

LLVM IR is a better example.

https://en.wikipedia.org/wiki/Intermediate_representation#La...

Loads! Hardly a novel idea.

https://en.wikipedia.org/wiki/Intermediate_representation#La...

All user accounts are also customers. Some are paying with data and contributing to metrics going up.

That’s not how words work.

All users are stakeholders.

They’re emphatically not considered customers.

We can disagree with that, create legal protections for those people - but that doesn’t make them customers to OpenAI, Anthropic, et al.

If you have never experienced becoming once, try DMT or a large amount of acid on a quiet day.

ncdu

netsurf

And for but the price of a coffee per month you get both dark mode and markdown support!

> For Developers

Would you mind sharing the source code?

> Copy API keys

...yeah, I think that'd be a hard requirement. I don't think there is value in a cliboard-as-a-SaaS that is not self-hostable or even auditable.

I think you are putting the cart before the horse and putting your users at risk by integrating credit card payments before sorting out the basics.

> The important point is to be able to recognize that and not coerce users into using your project only how you envisioned it and only like that. Some projects are failure on that count having switched on dictatorial direction on that aspect.

There is certainly a balance there. If every function inside your code is now considered part of your API contract, almost anything is a breaking change and you can basically forget about ever meaningfully refactoring that codebase.

Many times making things private or marking them as internal-only is the right call.

I'm not really intimate enough with libsodium to judge if they made the right cut there or not in hindsight.

> and you can basically forget about ever meaningfully refactoring that codebase.

Ummm why? Breaking changes aren't the end of the world? Deprecate and communicate clearly and people are usually fine with them (if it's meaningful progress instead of churn).

They are. Every breaking change is a pain point for your users/customers. Every time they have to do something to work around your breaking change, it's an opportunity to reconsider whether they need you or whether using your product is worth the trouble.

Lol if you say so. I contribute to an OSS project with thousands of industry users and we break downstreams all the time - we literally have no stability guarantee. In the 2 years I've been a contributor I've seen exactly once when someone got upset about a breakage.