427 karma · joined September 28, 2019
This is what GitHub does. But incidents like this still happen: https://httpie.io/blog/stardust
> Due to an unfortunate sequence of events, I accidentally made the project’s repository private for a moment. And GitHub cascade-deleted our community that took 10 years to build.
> There’s a confirmation box. It’s designed to stop users in a situation like mine from doing something stupid. It tells you that “You will permanently lose all stars and watchers of this repository.”
If it happens to experienced developers, imagine the laymen. Humans are just fallible, I guess.
As for the other bacteria, what they used was not the "common soil bacteria" Bacillus subtilis, but Bacillus atrophaeus[2] which was known as Bacillus globigii at the time. I think this is the only clear factual mistake I can find in the article.
The article also claimed that Bacillus globigii is now considered a pathogen, but I can't find much information about it outside of the referenced book. I'll leave it to someone else to weigh in on this one.
[1]: https://en.wikipedia.org/wiki/Serratia_marcescens#Pathogenic...
Lost everything. Been using Bitwarden ever since.
There's also zk[2], a zettelkasten-based notetaking tool like Obsidian, but the functionalities are provided through a CLI and LSP server.
As shown by your example, arrays constructed the native way will start at 1. So you're going to need to make your own custom constructor which means additional overhead.
Also, all built-in functions that expects 1-based arrays will completely break:
for _, value in ipairs({[0]="foo", [1]="bar"}) do print(value) end
This will print "bar"And even if you still insist on pushing through all of this friction by handrolling your own stdlib, everything is out of the window once you interact with any external library that you don't control.
There's a very good reason why no one is using this trick. Anything other than 1-based indexing is just undefined behavior.
Other than that one response, this looks like a very constructive back-and-forth (which could've been way shorter if the asker presented his case accurately without exaggerating it), so I don't really see what's wrong with it.
What did they use before?
The first thing I found awkward about it is that prompt fields are always initiated in normal mode. So if you want to execute a command with : or interact with an element using f, you have to manually activate insert mode first before being able to enter text into the prompt.
I'm sure there's a way to change this since the entire thing is in Lisp, but it sure is an odd default.
That's really funny, because I've seen websites that tries to appeal to "hacker"/"minimalist" aesthetics doing the same thing.
An example: the file-hosting service https://0x0.st. When you try to visit a link to a non-existing file, it will crash with a trace message that exposes the offending code block from fhost.c.
Wow, so RAW and BRUTAL. It's even written in C, so hacker-ish! Until you find out that the error message is fake: https://git.0x0.st/mia/0x0/src/branch/master/templates/404.h...
The server is actually written in Python and it generates a randomized, fake C-looking trace message for its 404 page.
Also, will you also get rid of the *.generated.ahk stuff in the next release? It would be far more ergonomic if komorebi can just read and apply the yaml config directly.
What exactly does this mean?
Will the Flash Player projector still work after that date?
I still have some old files in my Flash archive that I would like to play occasionally, so I really hope that the projector does not have some kind of time bomb.
The only rate-limit issues I've faced is with Twitter, because the way I do it is that I feed gallery-dl a text file containing the profile URLs that I want to scrape. But gallery-dl doesn't add a timeout in-between each input URLs, so Twitter might force a temporary cooldown on you if your list is a bit long.
But you can easily avoid this by writing your own shell script with your own custom timeout.
It's so funny honestly.
Where did you think GPT learned it from? ;)
https://www.ruralmessenger.com/blogs/fair-thee-well-good-sir...
https://www.amazon.com/Fair-Thee-Well-Nathan-Jones/dp/069241...
https://www.amazon.com/Symphony-Fair-Thee-Well-Requiem/dp/B0...
[1] https://stallman.org/archives/2019-jul-oct.html#14_September...
It can also function as a client for Discord. A shame that it is closed-source though.
There is one minor feature from Workflowy that I miss though, which is is the ability to "zoom" into a headline. You can narrow subtrees, but its level won't be adjusted. I tried to use some horizontal scroll hackery but couldn't get it to play well when you're switching buffers. I'm not sure how to save those narrowed buffers across sessions either.
But in any case I definitely will stay with org-mode for quite a long time, it truly is a powerful piece of software.