treffer

That they would never see me buying again from them. That I can stop OTA. That matter is interoperable and I can run multiple gateways before cutting them out.

Most IoT stuff I own had a good track record. The only stuff that screwed me over was the logitech harmony smart remote.

But I usually pick the more open ecosystems and vendors. E.g.heating is on shelly.

Modern wifi has always been a killer for OpenWRT. Usually expect to be 1 gen behind for a few years.

I wanted Wifi 7e recently (upgraded to really fast fiber) and went with Ubiquity for that.

I did find the Totolink X5000R extremely good. 50€, WiFi 6 on both bands, fast. But I couldn't find a 7e upgrade I would be happy with.

RedHat used to have a poster of the linux source code. Because some early version did fit a large sheet of paper.

Not sure if that's still available but it was a fun poster that I can highly recommend.

Or switch to HDR if you have a capable display.

I was pleasantly surprised that HDR also means you can control brightness - it is all software I that case!

And the brightness keys on an external Apple keyboard work.

Oh great, I missed that end of the page. The "Round 2 details" links back to the blog and it is hard to see the FAQ on mobile (needs manual scrolling to the end).

Google search and Perplexity failed when I tried, too. Google search has caught up now (haven't retried Perplexity)

A 41.5mm diameter sounds good. That's a whopping 10mm/20% smaller than my current watch. Should be really neat given the thickness.

I pre-ordered because I loved the Pebble Round - especially the size and look. My intended use case is for formal dress codes and special events (weddings, new years, ...) wheretny fennix 51mm does not fit in (literally and figuratively).

That said: I can't find full dimensions for the new round 2. I can guesstimate that it should be 10-20% smaller in diameter and less than 2/3 the thickness.

Would you mind sharing full dimensions or even update the post?

And congratulations! I really like this. I hope there will be enough of a market to support this project long term.

I had 8 IPs in a hetzner server years ago. One IP had an iptables rule to accept openvpn on any port.

My openvpn config was a long list of commonly accepted ports on either tcp or udp.

Startup would take a while but the number of times it worked was amazing.

Interesting. But who is OpenDevicePartnership?

Looking at the members on the repository this seems to be a Microsoft project?

Compatibility as I understand it means "mixing this in a project is OK".

This is the case if the 2 license aren't at odds. Usually one license is stricter and you have to adhere to that one for the combined work.

A counter-example is GPLv2 and Apache license. Those 2 are incompatible. This was fixed with GPLv3 and you can often upgrade to GPLv3.

So no, this won't allow you to relicense as GPLv2. But you can use GPLv2 code.

This is especially relevant if you have such code redistribution clauses.

I tried a few times as some BIOS have a hidden or disabled setting but I never got past a plain crash. Device and CPU vendor support for classic S3 is shrinking. E.g. on framework laptops the Intel CPU(!) does not officially support S3 sleep.

So I can understand that there is no option for it if all you can get is out of spec behavior and crashes.

Also note that it is incompatible with some secure boot and system integrity settings.

The product page lists EDK II. Is the code available anywhere? I can't see it in edk-platforms.....

I would love to have a UEFI I can compile....

I guess the reason is the screen. It's 320x240, and 0.3M is 640x480 (VGA).the secondary screen is even lower resolution (160x120).

It does work very well for this screen resolution.

And what else would you do with this media given it's a feature phone?

Is it? The article lists 2015 as the year where things improved a lot, 2017 is well past that. The numbers are low and even that's inflated due to recalls.

I've seen >>10 year old laptops where the battery is still good enough to go from charger to charger. Just go to ebay and check out 2009 MacBooks. That's ~15 years now.

I don't think this is unrealistic if you can live with the heavier degradation.

It just depends on what you use for management.

IIRC the /etc/network/interfaces does a reconfiguration that's pretty disruptive.

Things like brctl and ethtool worked on the fly without issues (note though that I mostly used Arista years ago).

It is usually non-disruptive if it gets applied as deltas. If your config tool does a teardown/recreate then that's disruptive. Within the bounds of ethernet and routing protocols (OSPF DR/DBR changes are disruptive, STP can be fun, ....).

Depends on what you are doing. But you can take the path of app / os images.

My home network is just openwrt, and I use make plus a few scripts and imagebuilder to create images that I flash, including configs.

For rpi I actually liked cloud-init, but it is too flaky for complicated stuff. In that case I would nowerdays rather dockerize it and use systemd + podman or a kubelet in standalone mode. Secrets on a mount point. Make it so that the boot partition of the rpi is the main config folder. That way you can locally flash a golden image.

Anything that mutates a server is brittle as the starting point is a moving target. Building images (or fancy tarballs like docker) makes it way more likely that you get consistent results.