3,336 karma · joined April 3, 2010
Someone should remind Github.
From their "permissive" trademark policy [1]
> You may also use the “OpenSearch” word mark to make accurate statements about compatibility and interoperability using relational phrases such as “works with,” “runs on,” “compatible with,” and the like (e.g., “Foocorp Software powered by OpenSearch” or “Foocorp Software for OpenSearch” or “Foocorp Software with OpenSearch compatibility”).
I just find it weird personally.
I would disagree with the meaning of "abuse" the author is intending here. I think it's more harmful to prevent opposing (even potentially incorrect) point of views from reaching either side. That's the point here. It's just speech. Why can't people who find it reprehensible just skip it?
But the level of irresponsibility with customers' most private data from a company who's MAIN JOB is to protect it is absolutely shocking. Yes, it's the freaking pixel that does the tracking, BUT IT'S THEIR RESPONSIBILITY TO KNOW WHAT THE HECK IS HAPPENING ON THEIR WEBSITE. Don't they have any sort of vulnerability assessment or security code review? Their reply tweet is almost as infuriating as how something like that could even happen to begin with. Like yeah, sorry, ain't our fault! It's astounding.
I considered using backblaze a couple of times and now I'm very happy that I eventually didn't.
I'm very happy to see this post. This whole stupidity is so extremely frustrating to me. It's a perfect example of how little thinking the mainstream wants to put into important issues, how toxic American-liberalism is, and how easy it is for the masses to follow any seemingly-positive action just to avoid seeming negative.
If you're serious about your ecom and you're in it for the long run, it's worth it to pay for a custom solution. Control your code and your customers data.
With that being said, I don't see a problem in requiring their users to use a specific PSP that makes more business sense for them. But yes, like other have pointed out, it's way up there on the hypocrisy chart to do this while complaining about Apple. Apple's 30% cut is not unfair, neither is theirs.
- Easy stuff, the kind the some proper digging within the docs or the logs would give the answer. This always seemed like the majority, even more within the last few years. I don't think I should spend my time answering those. I used to ask questions on forums before and got schooled a couple of times from people telling me to look it up in the docs or from other questions, it was more valuable than a direct answer itself.
- Stuff that require digging, like 1-hour or more. Those are interesting, but again, I have my own issues that require 1+ hour research that I could spend my time on. I know not everyone is doing it for the points, but I didn't feel like the transaction is worth it. The knowledge I'd gain from researching a topic I don't currently care about to answer a random question might seem valuable (and it may be), but I think it's somewhat similar to the value of watching those short "educational" youtube videos, you feel like you learned something, but 2 days later you basically forget the whole thing. Maybe it's just me.
- Stuff that you're the/a authority on, like if it's your language/library/framework/toolkit. I'm not either of those, but if I was, I don't think I'd be able to spend time answering random questions on a site I don't control. I'd probably feel much more compelled to give lengthy answers on the tracker/forum/qa site of the project itself.
Imho tho, one super important thing that Jam needs is federation. The best thing about Clubhouse is the discoverability of other people public rooms and being able to dip in and out of random conversations. The combination of self-hosting, open-source, and federation would be a great alternative.
This style of argumentation is as bad (if not worse) than baseless rejection of Wayland because of "vague" criticism.
If I try to read between the lines, the author is worried that if more people don't jump ship and switch to Wayland, suffering through whatever trouble they might face, Wayland won't get better faster. Which although true, is a very selfish argument that does not see beyond the author's own use case.
I'd like to try Wayland sometime, so far I haven't. I don't think there will be a lot of issues that I'll have to get around, but honestly I'm not looking to find out right now. I use Xorg and I'm happy. At some point, I'll try Wayland.