Bitcoin is more widely seen as a vehicle for speculation rather than a decentralized currency. Unlucky.
Bitcoin is more widely seen as a vehicle for speculation rather than a decentralized currency. Unlucky.
What you have described is technology beyond the imagination of the men of my time
What century is it
Before I blocked the instance I had nothing but miserable interactions with Hexbear users, and it had nothing to do with political opinions.
Mesa is usually pretty quick to update, it’s just that stable distros won’t update mesa all that quickly. I assume most of them have some way to install a newer mesa from a community repo or something.
That would make it impure
Docker is lighter and easier to manage than a VM. I run a collection of services as docker compose services inside a NixOS host VM. It’s easy to start, stop, monitor, update etc. even from a different computer (via ssh or docker contexts). It’s great.
deleted by creator
It’s just as easy to run in a Docker container and I would recommend this anyway.
The compositor will have to implement a CLI. Sway has an IPC socket and CLI just like i3 and I can use this to hide windows.
What’s wrong with mssql besides licensing? It’s fast
It’s what happens when content is url encoded and not decoded again later. It’s easy to do by accident because you can’t tell if a string is already url encoded in any general way, so the processes responsible for sending and receiving need to agree on how/when to encode and decode (i.e. they both have the power to break it for the other)
I do not know what that means
If only we were still having the conversation.
That’s… not the point either. The point is that “reporting false positives isn’t a bad thing” is only true up to a point. The discussion is then “is this before or after that point.” Which, given the context of the bug, isn’t really a given. But I don’t want to have that discussion with you anymore because you’re annoying.
“What if the boy who cried wolf got lucky and didn’t get eaten in the end”? Seems to have missed the point of the parable a bit.
I didn’t say the CVE was valid. I explained why it was a mistake. I didn’t say “disclosing security bugs” is, in general, a bad thing, I said raising undue alarm about a specific class of bugs is bad. It’s not a matter of “less or more information,” because as I said, a CVE is not a bug report. It is not simply “acknowledgment of information.” If you think my argument has no merit and there is no reason why “more information” could be worse, you’re free to talk to someone who gives a shit.
Uh, no. But thanks for guessing. It’s frivolous because it violates several principles of responsible disclosure. Yes, the scope of impact is relevant; the availability of methods of remediation is relevant; and the development/patch lifecycle is relevant. The feature being off-by-default and labeled experimental are indirect references to the scope of impact and availability of remediation, and the latter is an indirect reference to the state of development lifecycle. Per the developer(s)’ words, this is a bug that had limited risk and was scheduled to be fixed as part of the normal development schedule. Escalating every such bug, of which the vast majority go without a CVE, would quickly drown out notices that people actually care about. A CVE is not a bug report.
Eddie Bauer and Carhartt are my go-tos. Both carry tons of tall sizes. Wrangler has some too and may be cheaper.