chris_overseas

You can (hopefully) root your TV: https://e.nya.je/getroot/ and then follow a guide like this to disable all the snooping: https://forum.level1techs.com/t/lg-tv-block-mini-how-to/2551...

Disclaimer: I haven't tried any of this myself, I've just been looking into it as I am/was considering buying an LG TV.

A link to the press release https://yasa.com/news/yasa-smashes-own-unofficial-power-dens...

There's a lot more detail describing the project in a couple of forum posts here: https://forum.pjrc.com/index.php?threads/sarcasm-an-over-eng...

There's some backstory to the CoMaps fork that is detailed here: https://openletter.earth/open-letter-to-organic-maps-shareho...

Disclaimer: I don't know anything about this other than having seen the above link mentioned in a comment elsewhere as to why people should switch to CoMaps.

Looks great but I'm watching this while sitting on a tube right now. What I assumed was my train was lagging by quite a bit and then disappeared!

Not entirely true - e.g. Kotlin has null safety built into its type system, and I find it much nicer than the option/optional approaches used in various other languages.

https://kotlinlang.org/docs/null-safety.html

Not quite what you're asking for, but there was this discussion and website that you'll hopefully find relevant:

https://news.ycombinator.com/item?id=42660255

Agreed, and the small stdlib is one of the main reasons for this problem. I understand the reasoning why it's small, but I wish more people would acknowledge the (IMHO at least) rather large downside this brings, rather than just painting it as a strictly positive thing. The pain of dealing with a huge tree of dependencies, all of different qualities and moving at different trajectories, is very real. I've spent a large part of the last couple of days fighting exactly this in a Rust codebase, which is hugely frustrating.

A lot of people here are recommending WLED for the controller, but I would suggest you look at the Pixelblaze [1] instead. I've used both in a bunch of different projects and strongly prefer Pixelblaze over WLED.

Some reasons why: - It has a much more intuitive user interface - It's far easier to program new patterns. Programming is done in-browser with a language that's a subset of Javascript, with code changes being applied in realtime. - Due to the way its rendering engine works, the patterns it produces are generally far more 'organic' looking and smoother than most of the WLED ones. - It's possible to map LEDs in arbitrary 2D or 3D configurations (think lights strewn all over a Christmas tree), which WLED can't really do at all. - If you have multiple Pixelblazes you can get them to sync with each other over Wifi. - A really helpful community forum.

Downside: - The firmware isn't open source, though some of its tooling is, and the firmware is stable and gets fairly regular updates, so it's not a huge issue to me. YMMV.

For the LEDs, you probably want wired bullet-style strings of LEDs rather than the thin copper LED strips since they're generally more suited to outside use. By far the most common (and generally cheapest) type of LEDs are WS-2812B or similar. They're OK, though you might notice they don't have good definition at low brightness levels. APA-102 or equivalent are a bit more expensive, but have MUCH better dynamic range, so I'd suggest going for these if you can. There are other better (and more expensive) LEDs still, but it starts to become diminishing returns, plus they can be hard to come by or find suitable controllers for. If you're running lengths of more than a 150 or so LEDs then power starts to matter, and you'll either need to inject power regularly into the strips, and/or use LEDs designed to take 12V or 24V. These can come with caveats such as worse power consumption and/or fewer addressable LEDs per meter, so research what you're buying carefully.

[1] https://electromage.com/pixelblaze

You don't need any third party tools for this any more, OCR is now built in to the Snipping Tool. Just press ctrl+shift+win+s, select the region of the screen you're interested in, then use the new "Copy all text" toolbar button. (Note that this is very new and might not be rolled out to everyone yet)

/s noted, and sure Oracle are litigious, but the GPL community version of GraalVM, plus "early adopter" enterprise version licence[0] seems farily clear, and reasonable - at least as far as Oracle are concerned?

[0] https://www.oracle.com/downloads/licenses/graal-free-license... https://blogs.oracle.com/java/post/graalvm-free-license

You can use the left/right arrow keys to step through the existing snapshots, and turn off the "Rotate globe" option in the settings to keep your view in one place.

I'm not sure if it's fair to give it buggy code, but I just changed set(b) to set(d) in the example, and it doesn't realise there's a problem: https://whatdoesthiscodedo.com/g/517c50a

> eSIMs are a massive win when travelling, too. Instantly activate a data plan at cheap local rates in whatever country your travelling to, without having to first get your hands on a physical SIM...

For many years I've owned dual-SIM phones and on many occasions have bought a local SIM a the airport or corner store when travelling for a week or more to countires outside my roaming allowance. This is almost always cheap, usually also easy, but can sometimes be a hassle if it takes a bit of time to track down the SIM.

When I bought my current phone with one physical and one eSIM, I was expecting it to be a huge improvement. The reality so far has been rather different... Twice now I have had to waste a lot of time online shopping around to find an eSIM for the destination country. Most of the international providers are surprisingly expensive (often 10x the cost of a locally bought SIM), have awful websites that look like they were thrown together in a weekend, and they often require you to install their own app to manage the eSIM/account, which is also invariably awful. You're also less likely to have much choice of which network you end up on, which can be a significant issue in less developed countries.

Now that I only have one physical SIM slot and always need it for my home country SIM (my mobile provider doesn't yet even support eSIMs) I regret chosing eSIM over a dual SIM phone. I do expect the situation to improve, but for now at least it still feels like a big step backwards for travel compared to dual SIM.

For what it's worth, I managed to get an RPi4 at retail price within a few days by setting the appropriate filters on https://rpilocator.com and keeping a watch on it with an Android app called "Web Alert". I've used the same trick to buy out-of-stock cameras and laptops too, works a treat.

The obligatory XKCD https://xkcd.com/356/

There are many reasons: power usage, size, cost, availability being some of the main ones. I've been using microcontrollers for wearables and, as much as I'd like the power and ease of use of a Raspberry Pi, the size and power requirements can be too much to deal with. The Teensy 4.0 has proven to be a much better alternative for me - much smaller, lower power consumption, and still plenty of performance including a floating point unit which has been a game-changer.

Face recognition is possible on a tiny and cheap ESP32-CAM[0] using Espressif's own ESP-WHO[1] framwork. Apparently it can process images at around 3 fps. I have an ESP32-CAM on order to try this out as part of a side project of mine[2], so I can make the eyes look at faces :) I would also love to get hold of a Person Sensor[3] which runs custom firmware specificially designed for face detection and would be absolutely perfect for this, but they're not in stock currently.

There's other libraries[4][5][6] that look like they could work too and I plan to try. As far as microcontrollers goes, the Teensy 4.0[7] should be powerful enough for reasonably fast processing (and it has a floating point unit!), though I'm yet to find a good library for doing so.

[0] https://robotzero.one/face-tracking-esp32-cam/

[1] https://github.com/espressif/esp-who

[2] https://github.com/chrismiller/TeensyEyes

[3] https://usefulsensors.com/person-sensor/

[4] https://github.com/ezelioli/Face-Detection-on-Microcontrolle...

[5] https://github.com/nenadmarkus/pico

[6] https://www.reddit.com/r/embedded/comments/g77exq/recommende...

[7] https://www.pjrc.com/store/teensy40.html

As another data point for you, I've travelled 71 miles so far with no photos taken yet. Firefox 106.0b9, various ad-blockers installed.

I'm seeing another possible bug, or maybe I just misunderstand what is happening. If I refresh the page everything is silent and the vehicle is moving, which seems fine. The vehicle window however has a button labelled "resume". When I click that the button disappears, nothing obvious seems to happen other than static starts coming out my speakers. There doesn't seem to be any way to stop the static other than refresh the page. Is that expected?

The classified are probably my favourite part, some of them are hilarious!

The same thing happens for Vincent van Gogh, and presumably others too.

> There's some intelligence and will going on in nature's laws to make life happen.

And how do you suppose the intelligence you refer to originated? You're not offering a solution, you're merely adding another layer of complexity that still needs an explanation along the same lines.

For those of you looking for an alternative, I'd recommend Windy[0][1][2]. It's UI can be slightly quirky but the weather models, features and visualisations are superb. If you're specifically after marine and wind forecasts, PredictWind[3] is about as good as it gets.

[0] Browser: https://www.windy.com/

[1] Android: https://play.google.com/store/apps/details?id=com.windyty.an...

[2] iOS: https://apps.apple.com/us/app/windy-com/id1161387262

[3] https://www.predictwind.com/ https://www.predictwind.com/apps/

In the code you'll see there is also linear interpolation being performed between the LUT entries, hence the reduced error compared to just using the 256 LUT entry values directly.

Discussed here: https://news.ycombinator.com/item?id=30948260

They almost certainly mean triple compared to lithium ion (similarly for the 90% less energy claim). Lithium ion batteries currenty hit a maxium energy density of around 265Wh/kg, with a theoretical maximum of around 400-500Wh/kg[0][1]. Lithium sulphur batteries have a theoretical maximum of around 2500Wh/kg.

[0] https://cleantechnica.com/2020/02/11/lithium-sulfur-batterie...

[1] https://www.lis.energy/site/li-s-energy-applications/lithium...

Li-S Energy[0] is a company with Lithium-Sulphur battery tech that looks to be close to commercial production. They just announced today[1] that they're building a commercial plant that will produce 1000 cells/week (equivalent to 2MWh of batteries annually). Arguably still somewhat vapourware at this point, but much better than most others I've seen.

[0] https://www.lis.energy/

[1] https://www.lis.energy/site/PDF/0f90f952-4a18-45ea-bce9-3c52...

I like the idea but it seems rather US-centric currently. I'm finding it almost impossible to filter by London, UK - a whole load of other locations containing 'London' across the US show up instead. Similarly, trying to reposition the map to London requires a lot of scrolling of the map, because I can't zoom out far enough to see enough of the globe. As it stands it's very difficult for me to use unfortunately, but hopefully it won't be too hard to improve the UX for an international audience.

> But the thing is that the pay is good, that I'm of an age prone to experiencing ageism in the job market, and also this is a place where I have ample slack for tuning my output and inmerse myself in side projects or personal improvement, so their loss...

None of those points prevent you from looking to see what other jobs are available and applying for any that look interesting. Who knows, you might find something that is better on all counts. Worst case scenario you don't find anything better, which will mean you're no worse off than you are already, you learned a few things in the interview processes, and maybe the knowledge that your current role is better than various alternatives you looked at makes things seem a bit more tolerable where you are now?

> If it wasn't for Google giving wind to their sails, the Kotlin ship wouldn't have gone anywhere.

I disagree. While the Google announcement to officially support Kotlin surely gave it a big boost, Kotlin was already in widespread use for Android development well before Google announced their support for it in May 2017. Additionally, it was also gaining traction for server side development since before the Google announcement. I had been evaluating Kotlin closely during this time, and made the decision to start using Kotlin in our (primarily Java and entirely server-side) company codebase in late 2016 because I was already convinced Kotlin had a bright future. We weren't the only ones who thought this, I was tracking multiple other companies in our space (financial tech) that were evaluating and/or already moving to it too.