Honestly there is rarely a blog I want to follow that doesn't have it. I do think it would be great to have more readers using it so that it becomes more significant, but for my reading it is actually pretty great.
I wouldn't say that it never caught on. I run a feed reader and ~6% of feeds have WebSub. Most of these are probably wordpress.com blogs which include it by default.
YouTube also sort of supports it, but they don't really follow the standard so I don't think it counts.
But the nice thing about WebSub is that it is sort of an invisible upgrade to the existing feed (or any other HTTP URI) so it just works when blogs enable it.
Most major feed reader services support it. One problem is that you need a stable URL to receive the notifications. So it is hard to make work with client-side readers. But I don't think there is really a way around this other than holding a connection open to every feed you follow. So I would say that it does its job well. I don't really see a need to get to 100% adoption or whatever. If you have a simple static-site blog that updates every month or so I don't think it is a big deal that it doesn't support WebSub.
Fuck Unified Push. Just use the Web Push standard. https://www.rfc-editor.org/rfc/rfc8030
It is what is used for browser push messages, is already widely supported. Is compatible with existing push infrastructure and users and is end-to-end encrypted. IDK why Unified Push felt the need to create a new protocol when a perfectly good one already existed.
Although there is no "client side" spec. The Unified Push client side could be useful. But they should throw away their custom backend protocol and just use Web Push.
You can set up SFTP with a password.
Or WebDAV isn't that awful.
The problem with IPFS is that kubo sucks. I used it for a while and it is always burning CPU doing nothing, failing to publish anything to the DHT and fetching files is slow. GC collects files that are supposed to be "pinned" by existing in MFS and so many other bugs all of the time.
I would love to see a new server take off that was built with quality in mind.
I think the core protocol is pretty good (although I think they should have baked in encryption) but even the mid-level protocols like UnixFS and DAG whatever are mired in constant change for no real reason as the developers jump on new fads.
Yup. Way too many people using different chat apps. I've bridged most of them but still annoying.
For business email is thankfully still pretty common. But some of them try to push you to one of the Facebook messengers.
I want an open widely used chat app ASAP.
You greatly overestimate the intelligence of the average Stack Exchange question asker.
I wouldn't say just omit it. If you don't include a phone number or address they are most likely to ask, rather than skip you over or something. Especially if you applied via some sort of managed recruiting system that most companies use as all responses will automatically go to your email.
My resume is here: https://kevincox.ca/resume/
I do have a flag to build it with personal information included, but that is just my phone number, and honestly I don't even remember the last time I did that. I basically "print" the public version to PDF and share.
Just about all of the information on the resume could be found elsewhere online. None of it is stuff that I consider private.
I created a USB with an encrypted copy of my root password to a few people. It also has backups of encrypted passwords databases and some other useful files.
It really is a better name.