codesections @codesections@fosstodon.org

I knew reality had gotten pretty cyberpunk, but this image really illustrates it powerfully. (source: https://thedorkweb.substack.com/p/tales-from-the-dork-web-4 )

Did you know that #firefox usage has almost passed Chrome usage on one contenent?

… that contenent is Antarctica.

(Source: https://www.lambdatest.com/blog/which-browsers-are-important-for-your-cross-browser-testing/
h/t: @abhayit2000)

Today's #xkcd hits a little too close to home—especially for anyone who has browsed the Internet with Tor. https://m.xkcd.com/2228/

Non Euclidean criminality:

@hackerman your name reminds me of this comic:

One of the all-time-best rejection letters is this one sent to an applicant to Princeton Law School:

In preparation for #rustBeltRust tomorrow, I've been giving the #ion shell (built in #rust) another look.

And, I've got to say… *WOW*

Last time I checked it out, I liked it in general, but was put off by its startup time. On my machine, it was ~100ms (about like Python or Ruby—not terrible, but definitely noticeable)

But its startup time is now *under a millisecond*—notably faster than #bash and getting pretty close to #dash.

I think I have a new scripting language for utility scripts!

A good thing to remember, perhaps especially these days:

#smbc https://www.smbc-comics.com/comic/2013-04-07

This article (http://www.bbc.com/future/story/20190919-the-maze-puzzle-hidden-within-an-early-video-game?utm_source=pocket-newtab) on a previously unknown (and still not understood) maze-generating algorithm burred in an 1982 Atari game is a perfect example of the Academia vs Business #xkcd in action:

Don't get confused:

#smbc

Clicking the "random" button on smbc got me this gem:

Have any of you heard of or tried #browsh? It's a full, mouse driven GUI browser---in a terminal!

The tech is pretty cool too: it renders the page in a headless version of Firefox and converts the rendered page to text. The upshot is that you can run it on a VPS, SSH in from a laptop, and get a GUI browser without paying the privacy/bandwidth/battery costs of running someone else's JS on your personal computer.

Here's a screenshot:

I just got back into town after traveling a lot earlier in the month and so *finally* got my hands on the #Fosstodon stickers! Proud to be a supporter of our great instance :D

Related question: how well do laptop stickers work as bumper stickers for a car?

I've *basically* turned #protonMail's web client into a webapp version of #mutt. I've got all the UI hidden and use it 99% with keyboard commands.

It's not for everyone, but I'm really enjoying it—and I love that their custom CSS is flexible enough to let me do so.

Anyone else both use Proton Mail and crazy enough to want this? I'm trying to decide if I should throw it up on Git.

#sundayScreenshot (or is it #screenshotSunday?)

I recently switched up my window manager and default color scheme—and I'm pretty happy with how minimalist it turned out.

You can also check out my blog post with more screenshots, including an example of how I use this setup to toot from #vim.

https://www.codesections.com/blog/sunday-screenshot-feb-2019/

I've been messing around with #stumpwm more (https://stumpwm.github.io/) and really like it.

I've got to say, this is the first time I've genuinely had the "read the source, Luke" feeling. Maybe it's a sign of the documentation having a few holes, but the source code is so clean and readable that I'm ending up understanding how it works from the code more than the docs. Cf. https://blog.codinghorror.com/learn-to-read-the-source-luke/

(And that's even true comparing it to dwm/other Suckless projects, which have very clean code)

Which of these is a "horizontal split" and which is a "vertical split"? And why?

(I've noticed that different programs flip the terminology—what do *you* think?)

Am I doing this right?

Does anyone else find themselves needing to take timestamped notes in #vim? I wrote a quick bit of vimscript to make it easier/automatic to do so and I'm happy to throw it up in a gist or something if there's any interest. Here's what it looks like:

Turns out, all this time I was supposed to be getting colored output from #rust's `cargo test` command—but I wasn't because I had my $TERM set to the wrong value. Oops!