But then ... WP is not tied to one hosting provider. There are no shortage of hosting companies out there to which you can deploy WP. In fact, many make it so easy it is ridonc.
The sandboxing requires CF workers though, as it depends on V8 isolates. Seems fair enough, but it'd be nice to see easily deployable cross-platform support someday for isolates or something similar, and not just for emdash.
I used to use it (better mouse) before BTT added Logitech support - but wasn't really happy with it. Every single update changed something, mostly my cursor speed in some small, but sufficiently noticeable way and I had to adjust it every time, which was super annoying.
At some point my settings kept getting lost every time my mac went to sleep, and I had to restart the app all the time. I messaged the developer, but never received any response or acknowledgement and I just dropped it. It's a pity, because I did like it for a period of time while I was initially using it.
It's just a rebuilt drop-in replacement stylesheet compatible to the built version of tachhyons 4.12 but using css variables (so when you need to write custom css you can use its tokens) and it has support for grid plus a few more modern utilities.
Building an application you use this as your utility layer that gets you 80% and for the rest you use an application specific custom css to write the parts where css is the best.
> IPv6 doesn't make it easy to allocate subnets to every device on a LAN; instead, subnets might be delegated to your local router, and then only individual addresses allocated to each device. If one of those devices then wants to route traffic on behalf of other devices (for example, to a sub-subnet behind a router, where the upstream router doesn't cooperate), it will need to use NAT. For example, this is how Tailscale exit nodes work, even with IPv6.
This is quite wrong, there'd DHCPv6-PD (prefix delegation) specifically designed to do this. Even more interestingly, it has recently been made part of IETF CPE requirements (RFC 9818 update to RFC 7084, July 2025).
That was excellent, thanks for recommending it. I particularly liked how it's a pretty factual FAQ, not particularly cheerleading for IPv6 nor saying "IPv6 is a failure, give up on it".
interesting read, pretty depressing take if you're pro IPV6. I think their guess that IPV6 has low value-add when considered as part of a hybrid environment is probably one of the better explanations I've heard for poor uptake.
"IPv6 is the next generation of the Internet Protocol (IP), the successor to IPv4."
This is a misconception. It is not the successor to IPv4, it is an alternative. Maybe the alternative is so good it will eventually make the older extinct, but it does not look like that
Regardless of whatever other things may be better or worse about ipv6, it's still a reality that as we continue connecting more and more devices to the internet eventually ipv4 addresses will become so scarce and valuable that a not-insignificant minority of residential customers will be behind such aggressive CGNAT that the internet will become nearly unusable unless a majority of the services they are using support ipv6.
I agree with you. While I can see some benefits to v6 on the internet, I find v4 to be miles easier and cleaner to work with in a LAN setup. Unfortunately though v6 oversteps on LAN features and makes bridging v4 and v6 way uglier than it should.
Runbox are a good option - company and servers in Norway: https://runbox.com/
Been around since 2000. They're also working on JMAP support and are the top financial contributor to the Stalwart mail server (https://opencollective.com/stalwart) so I think they'll have a more compelling offering soon.
Also worth keeping an eye on Thunderbird pro which will also use Stalwart: https://www.tb.pro/en-US/
Can recommend Runbox for a lot of reasons, but one gotcha that bothered me in day-to-day use was that emails are delayed by a minimum of 30 seconds, with no real upper bound, just a probability curve with, say, the 90th percentile around 5 minutes. On rare occasions, that means OTPs or login links valid for 5 minutes have expired when you get them. Yes this was really on Runbox' side, yes I talked to support, yes they cared, yes they subsequently ghosted me when delivering the requested headers of emails delayed for more than 5 minutes which they considered a normal delay "because email wasn't supposed to be real-time" (be that as it may, that doesn't take away that you sit there 30 seconds... 60 seconds... 90 seconds, wondering if you should go do something else while you wait for the confirmation link and get back to your current task later)
Seriously though, nothing but recommended in every other regard. Alias management, anonymous domains you can use, configuring the sender in Thunderbird no problem, everything else was great. My colleagues didn't seem to mind this delay so much as me so it's something to be aware of but might work fine for you
Edit: I realised this is already like four years ago now, it could have gotten fixed in the meantime. It was an issue for several years before we switched away for some reason related to calendars (don't remember the details, I wasn't my choice)
I agree, as a happy Runbox customer of several years. But probably the parent post meant non-EEA too, as Norway is effectively subject to any and all EU regulations.
Recently Runbox had a couple significant outages which made me rethink hosting my email with them. I and my family have used them for many years and I liked what they offered (didn't like bad web UI) but will probably be migrating to Fastmail or other when my current subscription expires.
I was disappointed more by their lack of communication than by the outages. And one outage wasn't even reported on their status page although they confirmed it via support. That's a very bad communication.
atproto feels like a move in the right direction for personal publishing that makes content discovery easier withtout the need to post to multiple channels / platforms. https://standard.site/ is one initiative working towards making this a reality.
I don’t think it does. ATProto is merely “managed storage for apps” by Bluesky and it’s quite opposing to POSSE - You rely on third parties entirely, not just for hosting but also access and moderation to your own content.
What you can and can’t do with your own content is also limited and managed by someone else. The entire premise that you can move your posts history etc, while technically true, is not compatible with the web (e.g. support for things like redirects, canonical urls being handled currently etc is again all outside of your control and a not a goal of Bluesky).
ATProto is in many ways like the custom HTML extensions Microsoft had in Internet Explorer to “make better user experience”.
For me one of the main points of POSSE is resilience. If the VCs behind Bluesky got tired of it tomorrow, all that would die is some links to your website. Your posts and content, RSS subscribers, people who linked or bookmarked your website etc - remain unaffected.
With the IndieWeb version of POSSE, the source of truth is the webpage you control.
For the ATProto version of POSSE, the source of truth is the record in your PDS. That record is interesting because it is both content-addressed and signed with your private key.
Where ever that record is syndicated, the reader (or app displaying the content) should be able to demonstrably verify the authenticity of the record.
And you can host your own PDS entirely independent of Bluesky, there are several interfaces for both reading and publishing Standard.site records:
> content-addressed and signed with your private key
Technically valid but also not required. ATProto works hard to present them as valuable or needed, like added value of sorts but:
- The need for signed content is niche to specific use-cases. Not sure even news outlets need this as long as they control their domain.
- The PDS is a funny contraption of protocols and technologies that are quite complex and probably can't (usefully) exist on their own outside the "atmosphere" ... even if you manage to set one up.
The question would be, why bother with all this complexity and layers when you can self-host your website anyway.
The added value of a PDS/ATProto is to participate in the social cloud of Bluesky. Without it, the entire thing is more of an engineering showcase than a useful tool.
ATProto is a great idea that will never go anywhere because of its close association with Bluesky the service, and Bluesky the company, and that's a shame.
Not as simple as wp, but not tied to one hosting provider.
reply