491 karma · joined October 10, 2014
You literally can't. It's proprietary software that you have a limited license to. This isn't like a deprecated Linux distro that you can always jump in and patch the security issues yourself.
Hell I'm sure if these tractors ran on free software, there'd be a business out there competing against the manufacturer by fixing old tractor software if it meant pulling in consulting fees from the farmers. But they can't, because we live in a world where you don't own software, you lease it.
In reality, when you send a letter, you are placing it into the care of the postal service. Your letter is only handled by postal employees, and mailbox privacy is codified in federal law. There's clearly an expectation that the postal service is not releasing your information to third parties without your consent. The information on the outside of the envelope is not meant for, nor is it needed by, anyone other than the postal service
I'll admit that gratuity is annoying, but that's a cultural problem with the US, not something specific to hotels. We just happen to live in a country where every person who serves you is expecting a tip. And to be fair, if I was staying at an AirBnB that for whatever reason had housecleaning or other service, I'd probably have to leave a tip there too.
The only advantage you get from an AirBnB is a unique facade, paired with having to clean up after yourself and possible fire and health code violations.
And as I said before, she thought she had permission. The government was literally funding and endorsing the project. It's just that not the right part of the government was involved, which is the classic example of excessive red tape.
> 3. A popular enough feature to possibly gate the entire calculus for users to switch services.
I'd say GitLab's CI/CD system is a lot more useful of a feature. At the very least you can use the actual git blame or another git UI as a workaround. Good luck setting up a replacement CI/CD system.
> 4. Obviously useful feature, as evidenced by the gitlab triage engineer being convinced to add an issue with a single paragraph plea.
That's not how triage works. Just because a bug is filed doesn't mean it's "obviously useful". If the employee had immediately given it a high importance, a release date, and assigned it to somebody, that'd be a different story.
> 5. Gitlab is seemingly unaware of this publicly available information, to the trivially rectified detriment of their own bottom line.
Well, since there is another bug already filed for this feature more than six months ago, [0] I'd say they are quite aware, they just don't consider it as important as you do. The particular person that replied to you just didn't know about it (not surprising when they have more than 10k bugs open).
Isn't this what eminent domain was created for? Shouldn't California state have the ability to make things happen for its own rail projects?