I have a Lenovo ThinkPad T430 that is by now almost 10 years old, it runs perfectly on Linux and is a fantastic choice even today. It's built like a tank and that Intel i5 powering it is immortal. DDR3 RAM is dirt cheap now and it takes up to 16Gb, you can swap its HDD to a SATA SSD (if not done already) and batteries for it are still cheap and plentiful.

If you're looking for something affordable for software dev, I can't think of a better choice for $200-$300

https://www.lenovo.com/lt/lt/laptops/thinkpad/t-series/t430/

They really built this one right, they don't make them like this anymore.

This is a Lemmy-ui bug, not related to CDN/cache.

I had submitted a bug report for it some time ago but it's not that urgent in the great scheme of things so they didn't get around to it yet: https://github.com/LemmyNet/lemmy-ui/issues/1865

(the report speaks about this happening after you log in, but it's the same thing).

This is insanely bad. I don' t know how they can recover from something this catastrophic.

CloudNordic is a market leading Cloud Computing and Enterprise Hosting distributor and wholesaler, offering Software as a Service to Resellers and End Customers.

CloudNordic offers Resellers a complete Cloud Computing platform and portfolio, including Virtual Servers, Hosted Exchange, Hosted SharePoint, IASO Backup, Shared Web Hosting, Domains and SSL certificate encryption.

So they likely have business customers that lost all of their e-mails, business files, servers, etc. Now that is a bad day at the office.

Awesome project and the tool looks great - nice work!

There was an existing tool which was similar: https://federation-checker.vercel.app/

Yours is definitely nicer.

That project is a great find, thanks! A real time saver, I should have these marked up shortly.

I'll do some more thinking on how we represent Cloudflare instances in general, I think for the time being I may just include a short note for them as people will wonder why they're marked anyway.

Edit: This is now done, all Cloudflare instances marked and an explanation added.

Hey, thanks for your feedback. I like your idea of labeling Cloudflared services, reporting is indeed a bit tricky for those especially if they use "Always online" to serve cached copies while the instance is down. I have some ideas on how to combat that, but labeling them also makes sense.

I can add tags against services - I have done this for ani.social as a proof of concept, I think it works but I welcome feedback. Sorting through the entire list is a bit daunting and will take me a while, but I'll get there.

Manually adjusting availability is a can of worms that I don't want to open, I'd rather we try to find other ways to level the playing field.

Yes it was changed some time ago: https://github.com/LemmyNet/joinlemmy-site/pull/170

I think you're one "active user" short of being back on there:

I believe you need 5 to be listed.

I've updated the post to include clickable URLs. Lesson learnt that I shouldn't rely on clients to treat domain names as links.

Thanks for your feedback. I like your idea, I'll have a look into what I can do to make it happen.

Absolutely!

Uptime Kuma Github: https://github.com/louislam/uptime-kuma

Note that I am not the creator of Uptime Kuma, https://github.com/louislam gets all the credit there.

It's just a play on words: Le(mmy) + Stat(us) or Le Stat(us)

I think it's short and easy to remember, the fact that it's also the name of a famous vampire is just a bonus.

Https HEAD requests - I find it yields accurate results for Lemmy and it's extremely light on bandwidth.

https://lestat.org

Hey thanks for your feedback. I've made them all URLs now.

Search and sort are tricky as it's not something Uptime Kuma status pages can do, I'll look into what can be done there.

Of all the ones to miss!

Thanks for pointing it out, I've added it now.

Have you thought of self-hosting mailcow? https://github.com/mailcow/mailcow-dockerized

It's very easy to set up and fairly straightforward to maintain, if you have a static IP and it's not impossible to get a PTR record then I highly recommend it. Yes you're self hosting your own mail server but mailcow vastly simplifies this.

Alternatively plonking it on the right VPS can also work.

That's fine too, the short of it is it's entirely up to you.

There are no requirements, and they wouldn't be enforceable even if somebody tried. The admin of instance1 has no way of knowing that you already have an account on instance2. Your identifiable details (IP address, e-mail address) are private to the instance that you sign up with and it would be a violation of privacy (and inherently scummy) for those to be shared between instances - they're not.

You can be anonymous on the fediverse, just like the Internet in general used to be before Facebook.

That's entirely up to you, it can be the same username if you want. Speaking as an instance admin, there is no problem with users creating multiple accounts across instances, even if they're the same username.

Spam would be creating as many usernames as you can on any given instance (e.g. trying to register 100 users on lemmy.world because reasons) - there's obviously a problem with that. Creating you@instance1, you@instance2 and you@instanceN is perfectly fine.