jeduardo

There is some info about archiving here: https://www.gwern.net/Archiving-URLs

Lots of jobs and scripts, plus usage of archive.org as well. It's an interesting read.

Ah yes, I went through the announcement and missed this sentence, thanks for pointing it.

Makes sense as well, since "commercial licenses are also available from MongoDB, Inc." (https://www.mongodb.com/community/licensing)

Not a bad thing for MongoDB. I think Atlas was the only managed service after they bought mLab, it's good to have options. It also illustrates a point that working with them to have a managed version can actually happen.

Curious about how DigitalOcean will deal with clause 13 of the SSPL[0].

[0] https://www.mongodb.com/licensing/server-side-public-license

Hey, that's quite interesting. Just tested it here with alacritty and was able to get data from a remote server into the clipboard. The downside here is that it did not seem to work immediately from inside tmux, but a quick search shows that there are ways to make it work. Also found a vim-plugin[1] that would allow it to work from inside vim as well. If I can also find a way to pipe random commands to it, it might indeed work better than clipper for my use cases. Finally, there is the added benefit of removing the need to forward the local UNIX socket over SSH, which I find to be a bit flaky. Thanks for sharing it!

[1] https://github.com/ojroques/vim-oscyank

Useful tool indeed, thanks for sharing. I use clipper[1], which delivers a similar function through a different implementation. What I like about that one is that with right config you can also pipe output from remote servers back into your machine's clipboard, which is quite handy in so many situations.

[1] https://github.com/wincent/clipper

Indeed, zooming out is a trick I use for a couple websites but even so it isn't perfect. I often face the situation where 80% size is still too big or brings the dreadful horizontal scroll but 70% ends up being too small and very hard to read. These and layouts that bring colour combinations that break in dark mode (browser native or dark reader) are my current bane.

Just tested the pure HTML version and was pleased to find out that it does not force a minimum browser width upon the user. I usually set my desktop (1080p) to use a 3-column layout with i3 and am always bothered by the fact that I cannot escape from horizontal scrolling on every search I run on DDG.

I needed to add the HTML version as a new search engine option in the browser options to have it running as default, but hey, it works! Horizontal scrolling is now a thing of the past.

If you're using any chrome-based browser, you might want to enable the "force dark mode for web content" flag under chrome://flags. Some few websites look weird, but the vast majority becomes pleasantly darker. HN looks good. I cannot live without this option anymore.

Do you have more info about this? As far as I understand if you use e2e encryption with riot/matrix you should be quite safe.

I also hope Matrix takes off. I have been using riot.im for some time to check if it could replace the many chat applications one is forced to use these days (FBMessenger, Slack, Signal, Telegram, WhatsApp, etc).

It does have its quirks but I'm finding the ability of having e2e-encrypted chat with multiple parties in a way I can move across devices quite useful. It also does support some more modern features like sharing pictures, files, and emojis without major issues.

Didn't bother to find and try a text-based client yet, although matrix does seem to have an IRC gateway (of course): https://matrix.org/docs/projects/as/irc-bridge.html

> Booting from ZFS seemed like a hassle, without clear benefits.

It used to be a major hassle around 2 years ago but since then things have evolved significantly, up to the point where as long as you follow the install instructions correctly the first time, you can trust it to just keep on working.

One benefit (for me) is the ability of having full system snapshots taken periodically with minimum storage cost. I've used a setup on my personal workstation for years where a zfSnap job takes snapshots every hour. This has proven itself to be super convenient when accidents occur. Of course that the important data is backed up externally or committed to Git, but having the possibility to quickly revert mistakes is a big nice to have.

Such a system could also be easily improved to ship these snapshots to an offsite location as incremental backups. Of course the same process can be done in many other ways, but it is also other thing nice to have.

Another benefit I've had with this is portability between machines. My current Debian Stable system with ZFS on root began its life running out of an external HDD plugged onto an old Macbook Air. After I was able to get an external SSD and a Thunderbolt adapter, all I needed to do was to add the new device to the existing pool as a mirror and wait for resilvering, then remove the old device after all data was mirrored and the migration was done. When I finally got a new laptop, all I needed to do was to boot from the SSD and add the new NVMe device to the pool as a mirror, then remove the old SSD afterwards.

There is also the transparent compression feature that can potentially save a lot of HDD space depending on the usage pattern of the particular system.

And of course since ZFS is there present in your system (as it's the rootfs anyway!) you can use all other features you want, such as slicing volumes to use as root volumes for virtual machines or to use it as the backend for a local Docker host, where Docker can use an specific ZFS driver and leverage filesystem capabilities when storing images.

Of course you don't need to run it as the rootfs for many of these things, but you if do like ZFS then the benefits, possibilities, and the fact that you can do it outweigh the (nowadays reduced) hassle. :)

Well, we (and by this I mean myself and my fantastic team) have been running it since 2015 as the main filesystem for a double-digit number of KVM hosts running a triple-digit number of virtual machines executing an interesting mix of workloads, ranging from lightweight (file servers for light sharing, web application hosts) to heavy I/O bound ones (databases, build farms) with fantastic results so far. All this on Debian Stable.

The setup process was a bit painful given some interesting delays when using some HW storage controllers that caused udev to not make some HDD devices available under /dev before the ZFS scripts kicked in and we have been bitten a couple times by changes (or bugs) in the boot scripts, however the gains provided by ZFS in terms of data integrity, backup, and virtual machine provisioning workflow were definitely worth it.

157xxx here. Logged in just for kicks and found out that yes, the password still works. :)

I don't remember meeting anyone with a lower number than mine, although I was aware that, at least on the global user directory, there were 2 people in my city with a lower number, both related.

In my case I got last online times for several people (mobile app) but mostly all from 2015. I wonder if that's in any way related with the govt blocking WhatsApp that year...