Either go the QEMU route or just add a new tag `Generated-by` and let reviewers flag oddities. At least for now that gives plenty clarity for such important changes.
Well, one is enterprise and the other is community version. Is it still the same if you compare same editions? How does it look now on the enterprise edition? Did they move functionality from the community edition to the enterprise edition?
This makes me appreciate my newly discovered "Remove YouTube Suggestions"[0]-extension a lot more. My homepage looks like this[1] and I absolutely do not get the feeling I'm "missing out" on any content. I just go to my subscriptions page, look at some videos and then close YT :)
I also discovered Ciphey. Neat little tool indeed, but I just found out it's being deprecated. It's mentioned in this issue[1] and being replaced with Ares[2]. Neither could decipher this strange encryption[3] I used it on unfortunately.
It blocks sponsored content using SponsorBlock[0], which uses crowdsourced data to detect segments in video's and skips them (basically fast forwards over the content).
I imagine this will only work (and only index) threads. So the context can be gathered from the thread title/body and underlying messages reflect the discussion.
Some communities I'm in have #support channels which only support threads. So you create a thread, add a title and a body message and people can reply to your thread by clicking on it. There's no way to post individual messages; only comments in threads.
This solves your context problem. Still not sure if this is the right direction we want to go in. This just proves to me that Discord is not right tool for the problem at hand.
If a word begins with an unquoted ‘=’ and the EQUALS option is set, the remainder of the word is taken as the name of a command. If a command exists by that name, the word is replaced by the full pathname of the command.
