ThisNameIsTaken

Thanks! Interesting to read the rationale behind it [0] which in short is, try not to use what is basically a terminal emulator within a terminal emulator, and window management should be done by the terminal emulator. I primarily use tmux for session persistence (in ssh sessions) anyhow, and still default to my muscle memory for new tabs/windows in the window manager. I haven't tried it yet. The proof of the pudding will be in eating it I suppose.

[0] https://bower.sh/you-might-not-need-tmux

Like Maildir? Many mail clients support that format already.

In a similar vain, I currently enjoy reading A Philosophy of Walking by Frederic Gros. Gros draws the musing of various philosophers on walking. To me, his description of the slow beat of the footstep that propels imagination resonates with how walking works for me. When I'm stuck on something and feel I need to keep pushing towards a solution, a short break, often the result of an obligatory walk/ride to the train station, already sets my mind in motion.

Crucial is that the walk is not an intentional break for the purpose of brainstorming, because then my thoughts stay stuck. Such walking is 'idle' in the sense that it is an almost automatic process. The whole point is that walking/idling should not be a productivity tool.

It seems those were drawn by Barbara Remington [1] who didn't have time to read the books before making her illustrations. Apparently, the Lord of the Rings was in public domain in the US for a short while, so the publisher (and Tolkien) had to rush for a new 'authorized' version.

[1] https://arrgle.com/emus-and-piracy-the-story-behind-the-lord...

That is on the main branch. Behind the scenes [1] they're working a a huge rewrite to use the Bevy engine. A big effort that seems to be moving at a quite constant pace. It seems they're doing it quite rigourously: I've seen some issues in the bevy tracker where they check what is specific to their project, or where bevy can use some work.

[1] https://github.com/nannou-org/nannou/tree/bevy-refactor

So far, my thumb has been worse of now that I'm back to the pattern swipe unlock.

You're right that I maybe phrased it too harsh, the repairability _is_ a great feature. And of course, they do more by checking supply chains for some of the parts. The thing is, if your part is not available, you're stuck with their repair service. It surprises me they don't offer all parts.

Great though, that they resolved yours within the scheduled time!

As Fairphone owner I have become somewhat sceptical of their repairability claim.

Mine fell on its side on some pebble stones. The power-button, unprotected by the case, got scratched. The button doubles as a fingerprint reader, which ceased working due to the scratch. At first, I thought "no worries, this phone is friendly to those who want to repair it."

It turns out, this part is not available for replacement. I think this is an oversight; just like the screen, it is an outward facing part, hence, bound to be damaged for some.

Then, I brought it to my local repair shop. The owner had to tell me that they cannot repair Fairphone's, and that, for him, it is one of the worst companies to deal with. They try to centralise all repairs in their own repair center. Which means sending the phone -- which I need -- away for 2 weeks; paying a fee for diagnosis, an unknown cost for repair, and the hassle of a flashed phone. I already know what's broken, I just want the part.

I feel this is a real shame, as I am fully supportive of the stated aims of the company, and I want the product to be good.

[Aside: suggestions on how to deal with a scratched fingerprint reader are most welcome. E.g. can the scatch be re-painted? The phone thinks the reader is there, but it doesn't register any touch. ]

This is a great project: the code is super neat and the write-up very clear. I like the sousveillance aspect of it!

For a project I needed a low-latency RTSP stream as well. When reading a video stream with OpenCV, the default video buffer is quite big, which, when filling up, makes the video lag behind a second or two. It then becomes impossible to perform any interaction on it.

I wasn't familiar with the setting you use to overcome this: setting cv2.CAP_PROP_BUFFERSIZE to 1 on the VideoCapture. I am not sure, but you might get even lower latency by turning to OpenCV's GStreamer support. For me the trick was:

  gst = f"rtspsrc location={video_url} latency=0 buffer-mode=auto ! decodebin ! videoconvert ! appsink max-buffers=1 drop=true"
  self.video = cv2.VideoCapture(gst, cv2.CAP_GSTREAMER)

Zed has built in REPL for several languages, which does have image preview [0]

It uses the Jupytext format [1], for Python at least. Which frankly, is much more friendly to VCS than notebooks.

I agree on the 'format on save' as undesirable default, but disabling that was as easy as flicking a switch.

[0] https://zed.dev/docs/repl [1]: https://jupytext.readthedocs.io/en/latest/

I've been doing this for some time now and it indeed makes editing text in vim easy. Just `dd` and `p`. And as the article mentions, diffing is much cleaner.

There's a caveat however, if you comment a line (to keep the thought, but see how it would work without) some Markdown parsers will interpret it as an empty line, and thus create a new paragraph. It then becomes necessary to remove one of the semantic newlines, which looks rather messy.

As a Colemak (DH) user for ~5 years, I share these experiences.

I did a monkeytype benchmark before switching, and I still barely hit the same numbers, so it's certainly not a magic fix for more typing speed. What is left then is the argument concerning ergonomics: which I am not sure is worth the trade-offs.

Every time I now sit at another's computer I am unable to type without glancing at the keyboard. Moreover, I am trying to switch to (n)vim, and am completely at a loss navigating, as the hjkl keys are now scattered across the keyboard -- beating their purpose.

While being an avid Debian user on both server and desktop, I had never heard of the Extrepo[0] package mentioned in the article. It would be great if the repositories included in there would suggest this way of adding their repo. While it cannot guarantee the safety of added packages, it at least add an extra layer of checks.

Another useful thing from the article for me was `apt modernize-sources` to update the existing sources.list to the new structure. Now I need to check if scripts like this run automatically on my auto-updating desktop from my parents.

[0] https://packages.debian.org/trixie/extrepo

Adding to the list of 'this is what I am using', I have switched both terminal and code editor to Maple Mono[1]. Which, looking at TFA, seems to be somewhat similar in spirit as Atkinson Hyperlegible, although I haven't used that.

Maple has many ligatures, I personally like the hypervisible [TODO]. Overall I find it very legible, even on small sizes, and pleasing also for writing e.g. in Markdown.

[1] https://font.subf.dev/en/ / https://github.com/subframe7536/maple-font

What is particularly striking about the scandal is the impact of the mini-series. From what I understand (as a foreigner to the UK) is that it was the mini-series that sparked national interest in the case. Without it, those involved would still be in a bureaucratic and legal nightmare, in which all institutions rejected their innocence claims, and hardly anyone would have been held accountable. See also the "Impact" section on the linked wiki page.

It leaves me wondering how the situation would have been if it would have been a (dramaturgically) 'bad' series. It might have left those involved even worse of.

Wow, that book sounds like a mix of Johan Harstad's footnote riddled Forsaken/The Red Handler (and who's Max, Mischa & Tetoffensiven even is about 'idling') and George Perec's An Attempt at Exhausting a Place in Paris[1]. As you say, the almost childlike fascination with the mundane is really valuable, it helps to guide my own eyes when wandering the city.

[1] https://en.wikipedia.org/wiki/An_Attempt_at_Exhausting_a_Pla...

Last week I looked into such simplification/decimation algorithms to simplify lines sent to a showlaser projector. Turns out there is a whole bunch of different algorithms for decimation, each with different trade-offs.

It might be interesting to see how the edge cases mentioned in the article are impacted by switching to, for example, Visvalingam-Whyatt [0].

[0]: For a Python implementation: https://github.com/urschrei/simplification

Not sure it's precise enough though. In 2018, many clocks in Europe were off because the frequency on the net had drifted due to (as I understood it) the network being out of sync across various countries. Some here might actually understand the details of this.

The Physical Rhythm Machine Boem Boem [1] is a performance/sound installation that actually comes quite close to being a physical equivalent of this idea. Not self adjustable of course, but the sound of the balls banging around is highly visceral.

[1] https://instrumentinventors.org/project/physical-rhythm-mach...

This map makes me think of the New Inquiry's White Collar Crime map [1]. That project creates a strong image which for me disrupts the stereotype of what crime looks like and where we can find it.

I realize it has a very different aim than safemap, but I frequently use it as an example of how the selection of data sources and its visualization is crucial in communicating a particular story. This communication already starts with the name: calling a map of reported crime a 'safemap' implicitly suggests that red colored places are 'unsafe' and should be avoided. (The about popover literally states: "Learn which parts of San Francisco are safest and which parts are best to avoid.") Which, as the discussion here suggests might be more complicated than that.

[1] https://whitecollar.thenewinquiry.com/

A similar story unfolded at my university? [1,2]. Initially deployed as "scanners" instead of cameras. Similar to this story at Northeastern the board argued they needed to be able to assess room occupancy. With the cameras now disabled they increased the counting done by humans, who now just walk into the classrooms (they used to avoid doing so). I suppose they can later argue the cameras are less annoying and a computer counting would actually be more privacy friendly than a human. Without evaluating the necessity of the counting in the first place. A question also raised in the article.

[1] https://www.mareonline.nl/en/news/report-on-cameragate-confi... [2] https://unseeusleiden.noblogs.org/

For those interested in playing around with something similar: it looks like a sort of large scale implementation of Sam Lavigne's Videogrep[1].

[1] http://antiboredom.github.io/videogrep/

I'll be starting a PhD soon and would love to use a pandoc-based workflow (with MD or another format) for the gross of my writing.

How did you all structure the commenting on your writing? I find converting to odt/doc before sending, managing all the exported versions with comments etc. becomes quite tedious. But I'm a bit reluctant to force my supervisors to use eg. git+criticmarkup[1]. I would love to hear you experiences!

[1] http://criticmarkup.com

Wait, is this a real company? What employment agency (sort of) promotes their service by showing how easy it is to ditch their workers and visualises that by shooting them down?! [1] If it is not a parody, macabre doesn't even capture it.

[1] https://anti-captcha.com/

Impressive visualisation. Seems to be an extrusion of the Kadaster (government) building data towards the maximum height of the structure.

Much more precise data is also also available: there are height maps of NL with a resolution of 5 points per square meter, IIRC (not my field). Eg [1], but perhaps more parties do similar work.

[1] https://ahn.arcgisonline.nl/Postcodetool/s2.html?app=Postcod...

And as mentioned elsewhere, they indeed misrepresent renovations & construction work as building dates.

To add to that, I guess the intent of the writers is explained by the following:

We expect that more research will appear in the coming years that has similar biases, oversights, and false claims to scientific objectivity in order to “launder” human prejudice and discrimination.

Historical theories are brought up (1) to show that they are resurfacing and (2) because sciences (and I'm inclined to say DL in particular) are susceptible for making similar mistakes. The hard part is that these biases are often not clear at all, as they are based on general preconceptions/stereotypes and the theories thus confirm something we think we know (confirmation bias).

For example, I have been examining emotion recognition software [1] with which, just as with physiognomy, the face is taken as a proxy for a person's mental state. Just as OP examines the terms "criminal" and "justice" one could inquiry into the concepts underlying the digitization of emotions, such as "anger" and "joy". Terms that seem very clear on a brief encounter, but when further examining them turn out to be heavily influenced by eg. culture. Though not as obviously poignant as incriminating an innocent person, one should still wonder then what it means to feel 34% angry.

Now, this is a single example, but I guess OP's use of historical theories allows for a critical look at more DL applications out there. And maybe helps convince laymen (policy makers that buy and employ such technology) that DL is not an easy answer to complex social/political problems, such as OP's example of Faception's classifiers for terrorists, paedophiles and white-collar offenders.

[1] http://networkcultures.org/longform/2017/01/25/choose-how-yo...