133 karma · joined May 8, 2017
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.
[1]: https://arrgle.com/emus-and-piracy-the-story-behind-the-lord...
[1]: https://github.com/nannou-org/nannou/tree/bevy-refactor
Great though, that they resolved yours within the scheduled time!
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. ]
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)
When testing, I also found out that the codec and image settings of the camera matter. With a h264 stream, the images came in batches of a number of frames, whereas MJPEG provided a more constant image stream with lower latency. Lastly, disabling 3D noise reduction also removed some delay.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/
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.
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.
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.
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
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.
[1]: https://en.wikipedia.org/wiki/An_Attempt_at_Exhausting_a_Pla...
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
[1]: https://instrumentinventors.org/project/physical-rhythm-mach...
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://www.mareonline.nl/en/news/report-on-cameragate-confi... [2] https://unseeusleiden.noblogs.org/
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!
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.
> 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...