Isn’t it one of the points of content type hint ? (https://wayland.app/protocols/content-type-v1)
416 karma · joined April 30, 2018
Isn’t it one of the points of content type hint ? (https://wayland.app/protocols/content-type-v1)
It’s literally the first point held. "Here, as the Government concedes, the Secretary’s plan would cost MOHELA, a nonprofit government corporation created by Missouri to participate in the student loan market, an estimated $44 million a year in fees".
Which is even worse ? Why the hell I have no right to know my own DNA ?
I can discover interesting subreddits by pure chance by following a google search on a question I have. Or following a link on a blog
There’s no chance of that happening on Usenet. For most users, search/discovery is a web thing (web search, links) and there’s no link from the web to usenet. Therefore if you don't know anything interesting on usenet you can't easily discover it. Any interesting post/discussion cannot be simply linked on a tweet (or, for that matters, on IRC). Usenet is completely insular. A web forum is not.
Were I a Usenet enthusiast, that would be my 1st priority. Public archives of most important hierarchies (comp.* for example), indexed on Google, easily linkable.
(I’m not affiliated with them)
Ansible only needs Python to be installed on the host (and SSH access), I don’t think it’s an unreasonable requirement.
1. Where does this "use" comes from ? It is not present in the official React API reference : https://reactjs.org/docs/react-api.html
2. It says that the value is not serialized, but what if Page is rendered client side and I want getData to always be executed server side (for example, it may contains secret API key, or make a database call) ?
3. getData is async, so what happens to name if the promise is not yet resolved ?
Security by obfuscation has the potential to confuse some (mostly dumb) attackers, but it has also the potential to confuse your future self, for VERY minor benefits (since everyone agrees but most of your security should not come from security-through obfuscation anyway).
Hence, avoid.
However, if we look at the authors of the original article, there is no mention of her : https://www.semanticscholar.org/paper/Synthesis-of-a-new-ele.... Of the 30 authors of the article, only two have a wikipedia entry (https://en.wikipedia.org/wiki/Yuri_Oganessian and https://en.wikipedia.org/wiki/Joseph_H._Hamilton).
Nobody argues for that. Especially since we’re comparing timestamps (floats), not datetimes (objects). Let’s go line by line :
> ts = 1571595618.0
This is 2019-10-20 18:20:18.000 UTC
> x = datetime.utcfromtimestamp(ts)
I would therefore expect x to be 2019-10-20 18:20:18.000 UTC
> x_ts = x.timestamp()
I would therefore expect x_ts to be 1571595618.0. Which is surprisingly not.
Nowhere the equality operator was involved in the surprise.
No, they don’t store directly the actual password, they store it encrypted by a encryption key derived from your master password. A leak of the database won’t reveal any password, as long as your master password stays secure (aka is not "hunter3")
Hard disagree on that. Maintaining (bug triage, pull requests review, bug fixes…) is actually the hard work and the part that deserve the reward IMO.
When I contribute to an open source software to fix a bug/add a feature, my reward is that the software I use has an annoying bug gone/the feature I want. I don’t need any reward. On the other hand, the thankless maintainer deserve it.
> Consider something as basic as running an SSH server on the Linux kernel. In the mix you would have at least 10 vendors (assuming a minimal Alpine Linux system in its default configuration), which means that there are at least 10 separate organizations that still have bills to pay with actual money dollars regardless of the number of users of the software they are giving away for free.
And your judgment 2 ? :
> If log4j2 is responsible for your company's success, you have a moral obligation to donate to the person who creates this library thanklessly.
Let’s say that you convince me of 2. I have 603 packages on my production server, with no obvious way to know how much distinct maintainers this is, or how they accept funding. One node application on it developed by my company has 991 dependencies, 129 of those "are looking for funding", according to npm.
How do I even start to fulfill that responsibility in a fair way ? Just picking the 5 (or, hell, even 10) most "visible" or "obvious" projects would be a significant burden, and I don’t see how prioritizing by visibility is fair or fixes anything about "that obscure but important library maintained by that guy in nebraska".
Human Rights are a kind of schelling points where we agree that "those roles are so Universal that as soon as we recognize a violation of them, we instantly recognize who is the Bad Guy (the one who is violating them) and who is the Good Guy and (the one who is denied his basic human rights) and EVERYTHING GOES to fix the situation". If you have to put a bullet in the head of the Bad Guy, so be it. If you say that "Housing is a Human Right", you are instantly obligated to donate all of your disposable income as soon as you encounter one homeless. If you don’t, well, any bystander is justified in taking it from you, by force if necessary.
By putting everything that sounds nice in "Human Rights", you cheapen the term. Let’s say that in 20 years Human Rights really means exactly that : housing, basic income, internet access, and so on. In the mind of everyone, Human Right violation is no big deal, like someone not having internet access. Then how do you communicate the horrors of innocent citizens getting arrested, tortured and murdered ? Are you really going to put those two realities in the same term, "Human Rights Violation" ?