Sorry to hear about the bad news, wish you best of luck with the job search.
I'm currently on the 5th day of an apparent plateau and found this super helpful. Thanks for sharing!
I really like the darkly-pureblack theme, but I wish there was also a darkly-compact-pureblack :). I also like the vaporwave themes, but I wish it would let us choose a different monospace font (or any other font for that matter).
Data being lost?
It seems lemm.ee is missing data that is available in other instances like lemmy.world. Even posts and comments made on lemm.ee itself.
For example, compare the profiles of @[email protected] on both sites. You'll notice that on lemmy.world there are more comments more recently.
https://lemm.ee/u/sunaurus
https://lemmy.world/u/[email protected]
Edit: as soon as I posted this the data seems to have synced back up again.
I get that you're trying to pay homage to Apollo's logo, but to be honest it's a bit creepy. Apollo's logo was a bit creepy in the same way. I think it's the red half-moon eyes.
Oh yes, trust me, they do. Your butthole will never feel so clean.
I wish I could install a washlet in my apartment, but the toilet is installed into the wall so there is no pipe for the washlet to take water from.
Now that I'm back home after travelling in Japan I feel like a caveman. Sometimes I even end up taking a shower after pooping.
Still working for me as of the time this comment was posted.
I chose lemm.ee because:
- Its admin @[email protected] has been working hard at improving the instance's performance and fixing issues.
- It has been relatively smooth and performant since the infrastructure upgrade.
- The domain name is cleverly satisfying.
I can confirm it works without a VPN now from my location :). Thank you!
I can confirm it works without a VPN now from my location :). Thank you!
I am suffering from the same issue. I opened my browser's devtools and noticed https://lemm.ee/static/e20bfa7/js/client.js is returning 404. So I turned on my VPN into a random other country (I chose Norway), and the issue stopped. Could it be that your CDN is not serving the client.js in some parts of the world?