plett
It already has the Early Television Museum: https://nerdydaytrips.org/daytrip/na/us/early-television-mus...
Yes, if you only have one or two terminal sessions or open web pages then you can probably live without using them, but anything beyond that leads you into reimplementing features to cope with your desktop's lack of ability to manage dozens of windows.
The GitHub readme lists "You want the entire planet" as a reason not to use tilemaker. Why is that? Presumably it's excessive RAM/CPU usage during pbf conversion, or when serving tiles from the mbtiles sqlite file.
But how excessive are we talking? How big a machine would be needed to process a planet file? What tools work better with huge input files?
That guarantees that the cache remains hot for records that clients are requesting, but lets unused records expire.
https://action.openrightsgroup.org/help-us-protect-your-data...
There is no BIOS serial redirection, so SoL is no use until the OS starts booting, and grub has a bug[0][1][2] which means it can't find the AMT SoL when booting in EFI mode. But SoL works fine as soon as the kernel starts, and the KVM VNC works fine during BIOS and GRUB if I have an emergency.
One gotcha which would catch someone out who wasn't expecting it - the onboard video disables itself when no monitor is connected, so the AMT KVM just shows a black screen. This can be solved by DisplayPort or VGA "ghost" dongle in the back of the machine to talk EDID and pretend to be a screen.
I'm a big fan of conserver, and intend to use it in this project to spawn amtterm processes to connect to the SoL ports.
0: https://savannah.gnu.org/bugs/?42026
1: https://community.intel.com/t5/Intel-vPro-Platform/No-AMT-se...
2: https://wiki.networksecuritytoolkit.org/index.php/HowTo_Head...
I followed these instructions to add the auth https://github.com/jitsi/jicofo#secure-domain
Facebook already does this - everything is IPv6 only inside their datacentres, and the only dual stack devices are their load balancers at the edge. They had to do this because they were running out of RFC1918 address space to use internally for IPv4, and the traffic was already going through the dual stack load balancers anyway.
On the access side, mobile networks are also going v6 only. EE here in the UK (sometimes) only gives you an IPv6 network and uses 464XLAT to NAT you when you want to reach an IPv4 only address. They can do that because they know what devices all their users are using, and can whitelist recent versions of both Android and iPhone which have CLATs in them which makes 464XLAT possible.
Fixed line residential and business connectivity is much harder - laptops and smartphones will work just fine with IPv6 only, but people expect their games console or old networked print server to work, and frequently they only support IPv4. What's needed there is islands of IPv4 on their LAN and a 464XLAT compatible CLAT inside the customer's router - then the entire ISP network can be v6 only apart from a few NAT64 devices at the edge. I'm sure that will come, but it hasn't happened yet.
It will happen - mass adoption is inevitable IMHO. There are new internet users and services being added every day, and there aren't enough IPv4 addresses for all of them. It's either IPv6 and 464XLAT or IPv4 only with CGNAT. And CGNAT is expensive - keeping state for all those connections makes for expensive boxes with lots of memory.
It's a LineageOS fork which bundles MicroG and several apps to make a more usable out-of-the-box OS.
They have also re-added frequent builds for many of the phones that Lineage had dropped - including the OnePlus X which I have.
I bought new earpads last week for my 15 year old pair of Sennheiser HD477 rather than buying a new set of headphones, and my primary laptop is an X230 from 2012.
I experimented with migrating from Chrome to Firefox 57 when that launched. It's a very capable browser and I could easily use it as my main browser, but Authy was the main thing which stopped me dropping Chrome for work use. There were other things (like Netflix Chromecast support) which were stumbling blocks for home use, but I can always keep Chrome around for those.