I sell construction work. Sometimes my customers will have me price up something that someone else priced to them and they will send me a competitor’s redacted scope letter with the pricing blanked out so I can bid ‘apples to apples’ aka the same scope of work.
I’ve unredacted proposals using the ‘unflatten’ command in Bluebeam Revu (which is by far the best PDF editor) which allowed me to underbid my competitor and win the job (and at a higher price than I would’ve submitted).
Definitely an ethical grey area, but an edge is an edge ;)
I really don't think this is grey, I think these cases have clear legal implications, though I'm not a lawyer. You are circumventing redaction, regardless of how boneheaded it is, the intent was clear.
The information was in the document they sent me, they should’ve removed it completely if they didn’t want me to see it. The situation is identical to them mailing me a paper copy with a black piece of paper scotch taped over the price.
There are zero legal implications, it was a private contract. My customers regularly tell me the exact price that my competitors have submitted to them and that isn’t illegal.
Probably there are legal implications for attorneys circumventing redaction in legal documents but construction proposal letters have no protections against unredaction.
Legally, I can't see what's wrong with using information that you have, even if the other party didn't intend for you to have it. Lawyers themselves will use information in court that was accidentally sent to them by a counter-party, and that the other lawyer never intended them to have.
I would be really surprised if there was a law against this, and even if there was who really cares? As long as you don't make it super obvious (like consistently bid 1p under the competition) nobody will know.
Whether one cares depends very strongly on what "retaliation" means. If they ban your account, not a big deal - you were getting bad service and didn't want to do business with them anyway. If they send an armed hit squad to kill you, that would be worth being concerned about though.
I "purchased" a digital game once on the PlayStation Store. It wasn't clear from the description that it was completely useless without an active subscription to PSN, so I tried to return it. They said no way, sales are final and you've already launched the game. I did a chargeback, and they basically locked down my account until I filed a support ticket and had to lie, saying someone else made a purchase on my account.
That keyboard was such a POS that a Wall Street Journal writer did a feature story on it without correcting any of the mistakes the keyboard introduced. It was essentially illegible. Then the Web site had buttons that you could push to remove each kind of error and make it legible: https://www.wsj.com/graphics/apple-still-hasnt-fixed-its-mac...
I love org-mode, but if I were king, it would accept freakin' back-quotes for monospaced text. Instead, it takes ~tilde~ or =equals=, and I will never remember the difference no matter how many times I look it up.
But for the life of me, there are so many things I hate about Markdown:
- Alternative syntax for _italic_ *italic* and __bold__ **bold** (why?)
- versus using /italic/ and *bold*. It just feels so right
- You need to use HTML tags <u>to underline</u>, or <s>strikethrough</s>, or just about anything in Markdown (including line breaks! You need to use the <br> tag)
- +strikethrough+ is alright, but _underline_ just makes sense
- Lack of a unified Markdown standard:
- Diminishes portability (e.g. varying approaches for file meta tags like in Obsidian)
- Causes different renderings of the same document (e.g. Obsidian vs GitHub)
- There was a serious standardization effort in 'Standard Markdown', only for the original creator to be a knob about it: https://blog.codinghorror.com/standard-markdown-is-now-common-markdown/
It's a shame too because despite Orgmode being superior to Markdown in just about every way, its adoption is nowhere near as close (editing is hard on iOS, and needing Emacs is a barrier for the general public).
I switch between Markdown and Org Mode a lot, the syntactic differences don't bother me too much, but I guess I like Markdown's a bit more. But what I really miss in Markdown:
6. Inline LaTeX and document generation in general.
Now 1 is just an editor feature, and some of these others could be, too. But I wish Markdown was more powerful, extensible, or less ubiquitous.
What bothers me most about Org Mode is that support is pretty limited outside Emacs. We use it as a wiki replacement at my company, for that integrations into other editors are kinda good enough. But there's some areas like reporting only Emacs users can realistically work on. GitLab (and Forgejo, which we recently switched to) render Org pretty nicely, so it's easy to consume in a browser. But editing is a different story.
So I guess I wish for either a less complex (and thus easier to support) Org, or a more powerful Markdown.
I’ve seen a lot of apps extend markdown to support various additional features. Obsidian, for example, has an extensive number of community plugins which offer a ton of features.
This of course ends up being editor specific, but if org has the same limitation, by being tied to emacs, is it really any different? I think what emacs has going for it in this case is that it’s been around for decades, and we can assume it will continue to be around for decades into the future. The markdown editor de jour may not be.
This is also the primary hangup that's kept me from adopting org-mode for notes, and I instead keep everything in MarkDown, and miss out on all the org-mode organization effects. The differences in link syntax are hard too, but I've got 5-10 years of DokuWiki in my history that make the link syntax more palatable. However, I still prefer MarkDown syntax for links too...
I just "lustrated" [0] my Debian Stable machine onto NixOS on Friday, and it's gone surprisingly well! It sounds silly, but I installed this way because I didn't want to figure out how to mount my LVM + LUKS encrypted partition on the live USB.
What is lustrating? Basically, you run the NixOS installation tools on an existing Linux installation (install the tools with the Nix package manager). The installer wipes out anything on / that doesn't belong, with a few exceptions, including /home and anything listed in /etc/NIXOS_LUSTRATE, a file you create as part of the installation steps.
Go has surprisingly good "UX", which I don't hear people talk about much. It compiles very quickly and gets out of your way. I've found it useful for a few reasons:
1. The standard library has a real HTTP/2 implementation (unlike Python).
2. The Go compiler creates statically-linked binaries and cross-compiling is painless.
3. Channels and goroutines make it relatively easy to write parallel code. There are certainly sharp edges, like every language.
You've certainly piqued my curiosity. Can you say any more?