HN user

liversage

259 karma
Posts1
Comments79
View on HN

My understanding is that there are three mobile networks in North Korea: the normal one used by the citizens (they have smartphones made specifically for North Korea), one used by the government/military and one for tourists (requires a local SIM card only available in a specific hotel in Pyongyang).

The last one is connected to the internet and this is why you can see (or at least before the pandemic could see) Instagram posts from North Korea.

I have no idea if this information is still or ever was completely true though.

There's a somewhat dated but very interesting AMA on Reddit by an American teaching computer science in Pyongyang:

https://www.reddit.com/r/IAmA/comments/1ucl11/iama_american_...

Reading about the internet knowledge possessed by North Korean students, I'm always surprised how they supposedly also manage to be some of the most cunning and evil actors when it comes to hacking.

One of many useful features of LINQPad is the output visualizer ("Dump"). Granted, there are now NuGet packages (very likely inspired by LINQPad) that can do something similar in a console app but LINQPad is interactive, allows drill-down and can export to formats like Excel. It's such a productivity boost.

The database integration is also great and allows me to write ad-hoc SQL queries using LINQ.

The brand name 'The North Face' is inspired by mountaineering where the north face of a mountain often is the most interesting but also difficult side as it's always in the shade (in the northern hemisphere). E.g., the Alps have the famous classical north faces of Eiger, Matterhorn and Grandes Jorasses which are climbed by only the most accomplished mountaineers.

There are early finds of Homo in China but these do not predate the finds in Africa.

Neanderthals and Homo floresiensis are not early ancestors and they lived at the same time as modern humans emerged. I believe that Neanderthals are a subspecies of Homo sapiens so they were able to interbreed with modern humans.

Previous year (presumably the second consecutive La Niña event) the winter was exceptionally dry in the Alps leading to the current unprecedented snow and ice situation in that area so at least that year the snowfall was very limited.

The article states that the predictions should't be regarded as forecasts so obviously some years might not have the expected changes, but in addition the only expected effect of La Niña in Europe seems to be a drier autumn on the Iberian peninsula so I'm not sure how you arrived at your statements.

A famous case of this is the Danish man Victor Cornelins that was born in St. Croix but at the age of seven was brought to Denmark to become part of a human exhibition as a "negro kid" to attract visitors. His birth name was Cornelius which is not unusual in Danish so Cornelins must have been a simple writing mistake. However, this lapse is negligible compared to the racism he was subjected to.

https://en.wikipedia.org/wiki/Victor_Cornelins

Or 128 bits. FORTRAN has a REAL*16 type (quadruple precision floating point number). I encountered this at university in a physics department that studied non- linear systems also known as chaos theory. Rounding errors can quickly become a problem in these systems.

You have a timestamp in the future for example the time when a session at a conference starts. If to want to store this as UTC you will have to convert it from the local timezone of the conference location. You can always go back from the UTC timestamp to the local timestamp by performing the reverse conversion EXCEPT if the conversion involves daylight savings and the rule changes between now and the event in the future. While rare, daylight savings rules sometimes do change. I guess even local timezone offsets might change once in a while. When this happens the conversion back from UTC to the local time will be wrong unless you keep track of more than the UTC timestamp.

Thanks for this tip. I usually resolve this by opening Teams in the browser and find the image I need to see. It's very disruptive that an important UI feature randomly (or perhaps reliably) fails.

I agree that downloading symbols can be oddly slow but you can just turn it off, or only turn it on for specific modules. It can be helpful to have symbols for library code to troubleshoot bugs but typically you only need your own symbols and they are already on your computer with your binaries.

I don't have an iPhone but I've always been shooting RAW on my phones and then processed the photos in LightRoom. As soon as I use one of the "lenses" on my phone (like "night shot" or "panorama" or even "wide angle"/"tele") I only get a JPG. The RAW file is only created when I shoot using the basic camera. This is the case for my current OnePlus but also previous phones (Google, Nokia).

Cases 5 and 10 in the article are actually ambiguous. In each case there are two ways to draw lines to separate the high and low points and a naïve algorithm will just hardcode one of each like it's done in the article. This isn't a serious problem in the two dimensional marching squares algorithm but the same problem can lead to holes in the surface generated by the three dimensional marching cubes algorithm.

During a visit to Washington University I had the opportunity to work with this flaw in the algorithm and I ended up publishing a scientific paper about the subject. I then went on to write my thesis (in Danish) where I worked more rigorously on how to deal with this. It's so long ago that I almost forgot so reading about marching squares again was a nice trip down memory lane.

https://martinliversage.blob.core.windows.net/publications/1...

https://martinliversage.blob.core.windows.net/publications/1...