Https HEAD requests - I find it yields accurate results for Lemmy and it's extremely light on bandwidth.
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.
Hey, that is weird behaviour, I haven't encountered it in my testing with Chrome. There are a few things you can try to figure out what's causing it:
- Try clearing your browser cache (cookies, offline site data, etc): https://support.google.com/accounts/answer/32050?hl=en&co=GENIE.Platform%3DDesktop - sometimes, especially after Lemmy updates, things can be a bit wonky until you do this.
- If the problem persists, try using another instance to see if the same thing is happening there too. You're welcome to try lemdit.com if you wish.
This will help you narrow down the problem.
I suspect there may be two separate things going on:
- The comment behaviour you mentioned may be related to browser cache and recent Lemmy updates introducing infinite scrolling.
- The generic page error is likely related to the instance you are using. lemmy.world has suffered through a few DDoS attacks recently so it's possible that you are getting those errors when the instance is down due to those attacks. If it happens again, then perhaps take a screenshot and post it here.
Let me know how you go.
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.
Not at all, it's perfectly fine to have accounts on multiple instances.
I've tried refreshing lemmy.world and Cloudflare blocked me:
I'm officially a bot now I guess.
Edit: But more on the topic, they have been plagued by DDoS attacks recently so my guess is it's more of the same.
Edit edit:
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.