From my understanding, Discord Search API is heavily rate-limited. If you have a lot lot of messages (say, removing ALL of your message history in ALL servers) then this would theoretically be faster.
Finally it's official. I think it's a good move to make it an archived repository, so everyone knows for a fact this is not developed anymore. That means bugs or security issues are no longer actively searched and corrected. I wonder if this program will be taken out from distribution repositories now. My personal alternative is fastfetch .
First edit 3 years ago: Away till the New Year. Merry Christmas.
Then next edit 10 month ago replacing that line with: On hiatus.
Then next edit 4 days ago replacing that line with: Have taken up farming.
English is not my native language, and I don't understand what "Have taken up farming.", but I have my guesses. means. Normally I don't interpret such a situation, but it doesn't look good. Most contributions of the software is 3 years old, and only a few readme and link updates recently are made alongside making everything archived.
there should be some kind of notification system whenever something goes unmaintained. ive used unmaintained software for way too long before finding out theres some fork.
https://crates.io/search?q=neofetch brings up 21 versions to choose from (21 are actual neofetch clones). There is also a library to help you write even more of them.
I don't understand the fascination with a program that tells you what kind of system you're using. I'm not trolling. Can someone enlighten me on its usefulness beyond "yep, that's what my system looks like"?
I install it on servers and put it in my bash profile so it runs when I SSH in or open a new terminal tab. Mostly just as a safety thing. It’s basically a reminder to double check I’m on the correct machine/tab before I run any commands.
It doesn’t have to be neofetch but even in my containers and docker stuff, I try to put a little message so I don’t fuck up something.
Running through a checklist is important. I learned that from a helicopter pilot at a bar but I do think it’s true in our field. It’s not life or death on a server but training yourself to go through a simple checklist (even if it’s just “make sure this is the right terminal tab”) is good advice.
github.com
Oldest