baobun

Is this ironic?

> Three common and well-known tells in AI writing — sometimes genuinely deployed by humans but nowhere their profligate use by AI — are the regularity of em-dashes, the high frequency of specific words like “genuinely”, and the tendency to repeatedly invoke tricolons.

Clickbait.

    Uh-oh
    For a moment there it seemed that you were trying to peek into this Monero address: 47xmhbRuYpSYSrVZx2RsPBhaAQByZq3ucAT6ULxHvDAu8c853ErpLHqBdDmpVzcmWFdZFCWrfZYwp3rqs14zxXx95S7Fyv2
    No?
    Hmmm... it really looks like you were, like, trying to check out this dude's balance.
    Well, Monero says 'No'!

Wow.

Security or trust not even making the list.

You're grasping for a reliable unsupervised truth machine. That's a fundamentally intractable problem until you limit it down to a wolframalpha clone. And not even that by LLMs.

All it takes to become world champion is a blog.

https://www.bbc.com/future/article/20260218-i-hacked-chatgpt...

Should have known better than asking the monkey paw for more decentralized compute.

The breaches will continue until morale improves.

For real. Trying to find a specific video on youtube is a very similar experience to searching for legit cables and adapters on Amazon.

> For what it’s worth, I’ve been moving all my machines to lxde.

Any gotchas or regrets?

Haven't used it in many years and now considering going all in on making it (scaffolding of) next DE. So looking at the same move.

Better yet: Don't use LastPass.

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

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.

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.

> Modern versions of Chrom{e|ium} & Firefox (and other browsers based on them) have defaulted to HTTPS when the protocol is not specified.

This is not true but it would be nice if it was.

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

Why are you saying lies?

I just installed fresh chromium and firefox in a clean Linux VM and typed "google.com" (and a few others) in the URL bar with tcpdump running and they both initiated with TCP port 80. Can confirm that the https-only setting is disabled for both when looking in settings/preferences.

> HTTP is only used as a fallback.

Separately, using HTTP as fallback makes the whole thing mostly pointless security-wise. If an attacker can MitM port 80 it is very likely that they can also interfere with 443 to silently force a protocol downgrade. STRIPTLS.

SMTP STARTTLS has the same problem. ISPs and authorities have been known to harvest email traffic by the same technique.

We don't really need HSTS to address most scenarios. Just have browser not attempt http:// for addresses in the address bar unless explicitly specified. Have it try https:// without falling back to http://.

HTTPS-by-default with fallback is not a good default setting since it's vulnerable to the above attack. Strict HTTPS-only is not a good default setting since it prevents legitimate http traffic on internal networks. HSTS adds problematic edge-cases. It's hard to fathom that none of the major browser vendors seem to have figured out the obvious solution to just stop inferring http:// unless asked for.

For the sake of argument, let's say you have a check that caps the number of lines per file and that both you and main added lines in the same file. It's not too weird if that check fails only after merge, right?

One benign example of something that can break after merge even if each branch is individually passing pre-merge. In less benign cases it will your branch merged to main and actual bugs in the code.

One reason to not allow "unclean merges" and enforced incoming branches to be rebased up-to-date to be mergable to the main branch.

You probably want to run the checks on each commit to main in CI and not rely on them being consistently run by contributors.

You do you but I find rebasing my branch on main instead of merging makes me scratch mybhead way less.

Same for Android phones and laptops.

I lke it. It would be wonderful if the cap was gradually reduced to 0.

Title reminded me of something completely unrelated:

FFI overhead is not to be neglected sometimes. I've seen cases where replacing a python or js lib with an in isolation much faster native Rust or C lib with bindings had the end result being a decrease in real-world performance due to it being in a hot path or loop and the overhead being more significant than the savings were. There is no substitute for real-world benchmarks.

> The original code defined a struct with two bools that were not initialized. Therefore, when you instantiate one, the initial values of the two bools could be anything. In particular, they could be both true.

Then reading from that struct like in OP constitutes UB.

Don't ask don't tell.

Could you be more specific in your feedback please.

I don't how an init container would help?

Unless you inject them into your own images I think the most straightforward is to just mount the CA cert or bundle as a read-only volume.