The filter is setup for filtering slurs, not swear words more broadly. So “fuck” and “shit” are no problem, but “b*tch”, “r*tard”, and similar are censored.
(he/him)
Terminally online insomniac code monkey from burgerland. Deeply unserious person.
The filter is setup for filtering slurs, not swear words more broadly. So “fuck” and “shit” are no problem, but “b*tch”, “r*tard”, and similar are censored.
“Must” as in it is the only moral course of action? Sure. “Must” as in there is something materially compelling them to do otherwise? Unfortunately, no.
This kind of reporting would be threatened – already is threatened – because of the charges against Assange.
This is intentional.
Yup! She grew up really fast.
She still acts like a puppy though.
@TranslatorBot@lemmygrad.ml English
Yeah. Even my comment is understating things.
Your comment made me think of this tweet:
Tankies, notorious for not wanting to destroy western civilization. /s
Rethuglicans having a normal one making the Demonrats sound based.
The title implies we haven’t been the most unequal society for the better part of a century.
We have a black friend indigenous Secretary of the Interior who says it’s not racist, so it’s fine.
I never knew the initial commit was on Valentine’s Day. Also, very based how the very first commit is just the AGPL-3 license.
Its small size is due to having few dependencies and not having a lot of code itself. It also helps that I use different dependencies depending on whether or not it is compiled to target WASM. The library I use for WASM, gloo-net, is a thin WASM wrapper around the browser’s fetch API, which should keep the binary smaller when sent to the browser.
It’s a coincidence that you mention that. One of my main motivations for making this was to have something that would be easy to use with the leptos UI.
If you try emacs again, try evil mode. It adds vi bindings.
I think this is a good idea. My main question is: how could this reading club work? With a reading club for a book, you can have participants read a certain number of pages or chapters and discuss those readings regularly over some time frame. There’s a sort of progress from beginning to end that keeps all the participants on the same page (pun unintended). How could that be adapted for reading source code and documentation?
I write rust on a meh computer alot and have never had compile times be that bad (at least not for debug). The target dir is massive though.
I wonder if this is underhanded retaliation for their workers organizing.
Does this mean docker compose files are bad?