podge

I agree with your point about fragmentation. But isn't the "Year Of The Linux Desktop" just a joke at this point? Even more so now that desktop computing is becoming less and less important to most people.

This looks nice, particularly the automatic discovery.

Any monitoring system I've ever worked with can check for expired certificates. So usually the issue at previous jobs has been either there is no monitoring system (time to set one up!) or no SSL expiry checks are configured in the existing system (usually relatively straightforward to add manually or automate). I think I'd struggle to justify using yet another external service to cover that particular type of check.

With that in mind I wonder what the uptime % of HN is, and if the master/standby setup involves automatic failover.

Yep, I've done this with nginx and SSH tunnels, it works well.

It just immediately struck me as a website optimised for a mobile device - but this is very much a personal preference/bias. As soon as I saw 4 small icons in the middle of a black void I twitched :) I do like the minimalist approach though.

Thanks for sharing this. I'm not a fan of this kind of design when browsing from my desktop, but I did enjoy browsing through your Projects list. NIGHT.FM is great!

I love the fact that these interviews include people from a wide variety of backgrounds. Not just tech, but artists, journalists, photographers... even a few historians.[0][1]

[0]https://usesthis.com/interviews/margaret.omara/

[1]https://usesthis.com/interviews/trevor.owens/

I found this to be an issue as well, but there are a few ways around this for when you need to debug something. The most useful approach I found was to launch a new container from a standard image (like Ubuntu) which shares the same process namespace, for example:

docker run --rm -it --pid=container:distroless-app ubuntu:20.04

You can then see processes in the 'distroless-app' container from the new container, and then you can install as many debugging tools as you like without affecting the original container.

Alternatively distroless have debug images you could use as a base instead which are probably still smaller than many other base images:

https://github.com/GoogleContainerTools/distroless#debug-ima...

That tweet seems to be misleading to me based on my (admittedly minimal) understanding of BGP. The tweet states that the "Problem seems to have occurred at Cloudflare's end", but the problem likely originated on Facebook's end and a Cloudflare staffer noticed it.

At work I've only ever used various distributions of Linux, but at home I've started using OpenBSD and FreeBSD. I'm currently running FreeBSD 12 on my long in the tooth HP Microserver N54L, with a ZFS mirror + NFS/Samba serving up music/photos to my home network. It's been rock solid for the past few years, and I love in particular how 'boring' it is. It has great tech like ZFS but it's very predictable.

Thank you, I appreciate it.

Crippling depression.

Interesting! Particularly the discovery of the sparing use of green in Akira. I haven't seen either of those films in quite a few years and it really brought back to me how staggeringly beautiful they are.

When I was in Sydney in 2018 I was fortunate enough to stumble upon the 'Anime Architecture' exhibition[1] at the Japan Foundation, which included various pencil drawings and hand-drawn cells from Ghost in the Shell. It's a traveling exhibition so if it ends up near you and you're a Ghost in the Shell fan I highly recommend checking it out.

[1] https://anime-architecture.org

Interesting! I've been thinking of building a NAS and hadn't considered the rockpro64. Have you found that 4GB RAM has been sufficient for ZFS? I'm currently running a small ZFS array with 12GB RAM and the box never seems to use anything close to that amount, but ZFS has a reputation as something of a RAM hog.

A quick glance at the documentation would seem to indicate that this is very similar to Ansible or any of the other major configuration management tools (Chef, Puppet etc). I'm not quite sure why you would use this over one of those.

I like the idea, but something that does concern me is the potential lack of transparency.

While sponsors won't have any control over the projects they are funding, they will have access to a Sponsors-only issue tracker on GitFund with support for upvoting issues — thus gently nudging the maintainers on what they consider to be important.

I wonder if this Sponsors-only issue tracker be visible to the public? Although I suppose you could argue this sort of thing currently happens behind closed doors anyway...

...or not, according to a follow up in Ars Technica a few days later:

https://arstechnica.com/science/2017/09/experts-are-extremel...