codesections @codesections@fosstodon.org

I want to be able to tell my friends why #mastodon is better than the birdsite, so I wrote a thing: "Mastodon Is Better than Twitter: Elevator Pitch"
https://www.codesections.com/blog/mastodon-elevator-pitch/

I want this to be as persuasive as possible to outsiders, so I'd appreciate as much feedback as possible from Mastodon users

Can any of you help me track down a Japanese translation?

I'm looking for a translation of "楽" ("raku"). Specifically, I'd like a source that translates it as "enjoyment and ease".

The online dictionaries I've found have provided "comfort and ease", which is _basically_ right, but not quite it. And I don't have access to print dictionaries at the moment.

I know at least a few of you are much more familiar with translation resources than I am – can anybody help me out?

#raku

#FOSS etiquette question

I run into this situation pretty often: I encounter a bug in a FOSS project that has a codebase I don't know well, but I find a workaround that solves my particular use case. I'd like to be helpful and report the bug, but getting it fixed won't really benefit me and I'm not willing to submit a PR.

So here's the question: is there a concise way to report the bug as a FYI for the maintainer, while making it clear that I'm not asking them to do anything for my benefit?

> just posted part 3 of my #raku manifesto blog series – this one about how important it is to build programming languages that are optimized for individual/small group productivity. I also argue that doing so helps #FOSS projects outcompete big tech.

> I list @sir, @Gargron, @the_compiler as my go-to examples of how small FOSS teams can run circles around proprietary projects with thousands of employees

oops, it'd help if I included the link, wouldn't it: https://www.codesections.com/blog/raku-manifesto-3/

*facepalm*

just posted part 3 of my #raku manifesto blog series – this one is about how important it is to build programming languages that are optimized for individual/small group productivity. I also argue that doing so helps #FOSS projects outcompete big tech.

@sir, @Gargron, @the_compiler: I list the three of you as my go-to examples of how small FOSS teams can run circles around proprietary projects with thousands of employees

wow: #curl is moving to a RustTLS backend – initially opt-in, but the plan is to make it the default eventually. https://www.abetterinternet.org/post/memory-safe-curl/

I did *not* see that coming. I thought we might one day get a #rust alternative to curl, but curl itself embracing Rust is quite the vote of confidence.

(imo, more meaningful that FAANG's recent/continuing rust love)

This is genuienly one of the best error messages I've ever seen. What makes it so great?

1. Starts with a clear, non-technical description of the problem.

2. Follows that with a clear _technical_ description of the problem.

3. Suggests a solution to the problem and offers to automatically implement it

4. When that fails, provides another clear technical explanation (no non-technical one this time; that's fine because we're now into issues only triggered in advanced use cases)

Fantastic!

One advantage of my current work-from-home setup is that I don't need to unplug my yubikey nearly as often, saving me the trouble of typing in my PIN.

One *disadvantage* is that I've apparently totally forgotten that PIN, locking myself out of, oh, basically _everything_.

To the backups!

My measure of how much better #duckduckgo's search results have gotten is that I will sometimes think “oh, these results aren't very good” and add a `!g`

…only to realize I'm using a different browser than normal and was _already_ searching with google