63 karma · joined February 12, 2018
To me the reasons for this pressure seemed quite obvious: to ensure that I was fully enrolled in the data collection.
There is. I'm trying to hire more of it as we speak.
To be fair, my own distaste for clickbait is palpable here. But I think I can suspend it in light of the importance of this article's bigger point.
I've always thought this sounded like a good idea, and to see it actually happening is pretty amazing. Here's hoping it catches on.
The opt-in is limited to per video shared, as far as I've been led to believe and in my experience. I'd be quite alarmed to learn anyone could access anything I haven't designated without that specific sharing step on my part.
[1] https://www.sciencemag.org/news/2012/06/once-again-physicist...
It's a little less dramatic than it might have been, since his artwork as the catalyst had nothing particularly to do with the case. But certainly the magazine's participation here was constructive to the right outcome.
The local news station, on the other hand, was perhaps a bit less helpful.
For trademarks, for me at least, that seems to center on preventing various harms resulting from consumer confusion, deliberate or otherwise. Indeed, merely "protecting established revenue streams" is explicitly not a reason I'd endorse.
In that context, I'm not sure the consumer is meaningfully confused or harmed by any possible (otherwise legal) use of the trapezoidal four-finger shape by a non-KitKat product. So I'd be inclined to say "no" to trademark protection for it.
Contrary opinions invited, particularly consumer harms I might be overlooking.
This. I go to a lot of trouble to follow all relevant RFCs, SPF, DKIM, DMARC, and TLS. My intent is to help other servers know I'm transmitting in good faith, I'm hopes I'll get the same fair shake.
If it's still not good enough for you, please at least let me know that fact, with a message I can investigate. At the very least, don't outright lie, which is what I take a bogus 250 to be doing.
For code, wiki, and issues, it's self hosted Gitea. It's a dream to fire up thanks to Go and SQLite, and users forget you're not at GitHub.
Nothing more than those two plus email needed here, yet anyway.