Brave can make micro payments to content creators based on the number of views to the site, directly supporting content creators without ads or the need to join the patreon for each creator. It’s a fully optional system, off by default but prompted upon opening the browser for the first time. It’s a cool idea but they kind of spoiled it by making it be a crypto wallet with ads to earn the crypto.
Also, Brave doesn’t have a subscription…?
Honestly, despite the crypto, good on Brave browser for trying to subvert the advertising model by providing an actual monetization alternative
Yeah, never thought about this before, but how do blind users deal with captchas?
Have you used fish? The built-in fuzzy matching works pretty well for me. Wondering if there’s any reason to add atuin in. Sync seems like a negative to me more than a positive.
What do you have against the number 4?
That’s what decentraleyes does as well
This is a fantastic write-up, thanks for sharing!
FYI, Jenkins has an endpoint to validate the pipeline without running it, and there’s a VSCode extension to do this without leaving the editor: https://www.jenkins.io/blog/2018/11/07/Validate-Jenkinsfile/
The WinAmp maybe sorta open-sourcing is interesting. I’ve never used it (aside from downloading it to get MilkDrop working in Foobar2000).
I feel the same way. Designing good, opinionated APIs is HARD, but it also provides the best experience for both the author and the consumer.
Among other examples.
In a world where your IDE and maybe also compiler should warn you about using unicode literals in source code, that’s not much of a concern.
VSCode (and I’m sure other modern IDEs, but haven’t tested) will call out if you’re using a Unicode char that could be confused with a source code symbol (e.g. i and ℹ️, which renders in some fonts as a styled lowercase i without color). I’m sure it does the same on the long equals sign.
Any compiler will complain (usually these days with a decent error message) if someone somehow accidentally inserts an invalid Unicode character instead of typing ==.
These names are really fun! Good ones to add to my list…
Cool to see the Immich team going full time. I don’t use it personally but I hear great things
I have questions. Is this something in use today? Who is manufacturing them? Is this something you’re personally familiar with or just aware of?
You mean like git sparse-checkout? Admittedly experimental but useful
Do you mean admonitions? E.g. info, warning, etc? There’s precedent for that in commonly-used open source implementations, e.g. obsidian.md (which uses the same syntax, and started before). What semantics does it break? It’s designed to read well in plaintext and render nicely even if used in a renderer that doesn’t support admonitions, e.g.
[!NOTE] Information the user should notice even if skimming.
As opposed to other common markdownish implementations that use nonsensical plaintext which renders poorly in alternative renderers. Here’s a discussion on the topic in the CommonMark forums.
What do people have against the Mach kernel?
Actually I’m guessing this is a localization failure
My best recommendation is a good git GUI. I really like Gitkraken (proprietary & freemium unfortunately, but a pretty generous free plan). I’m now more advanced than many of my coworkers because it helped me form an intuitive understanding of git.