I’d like to see multi-reddit type functionality, so you can see each of the communities as one feed. And the ability to subscribe to that multi-lemmy.
Plus deduplication. One entry in the feed that covers all cross-posts (with some way to pick which comment feed you want to see - or hey, maybe combine them).
Now you mention it, I have spend so many hours on Windows trying to get the damn game to work. Trying to hide run Windows games on Linux, if it doesn’t work immedietly and I can’t find easy tweaks to fix it then I just assume it doesn’t work on Linux. But when a Windows game doesn’t work on Windows, I will spent hours making it work because I know it should!
It’s only beginning, it has nowhere near the features of RES, and mainly it helps with issues related to lemmy federation. But if there’s something you want, the dev is pretty open to new feature suggestions.
Servers are independent. You can only create the same username if it's not already taken. dave@gmail.com and dave@hotmail.com are the same username but different servers. You don't get dave@gmail.com reserved just because you have dave@hotmail.com, but if it's available you can register both.
Is there a way to have that account scrape whatever data you want to back up, saved posts etc from your ‘ghost account’ or your original account on the other server?
Lemmy is pretty young and there aren't a lot of tools. Most likely in future there will be an ability to transfer you account to another server, notifying other instances of the change. But this would require the home server to be available for approving the transfer otherwise you would have people stealing other people's accounts.
Mastodon (a twitter-like federated site) has an option to migrate an account, but as I understand it, that's more about moving your followers to your new account. I don't think the posts move. This page claims there it's a technical reason so perhaps we wouldn't have that on Lemmy either - but Mastodon does re-direct accounts, so perhaps on Lemmy in the future your posts might still point to the old user but if someone clicks on it then it will take them to your new account.
None of this is sorted yet so ideas will probably change over time.
I didn’t intend to imply that by using the same username across instances you were breaking some sort of rule. Different instances have different moderation policies, different federation policies, and different intents. Having multiple accounts in good faith should not be an issue and was not what I was trying to imply.
Rather, the intention was to show that we know bad actors do this with nefarious intent. Here’s an example (they show zero comments as they have been banned with content removed - also I think these ones only had posts not comments anyway):
I don’t really use my TV, but spend a lot of time watching TV lying down. I turn my phone so it’s facing the right way for me to see, though I get it would be a lot harder to get the cat to hold it upright.
I’m not quite sure I get what you’re getting at. If you’re using Cloudflare (for more than just a nameserver), then the client’s browser is connecting to Cloudflare via a Cloudflare SSL certificate. Any password (or other data) submitted will be readable by Cloudflare because the encryption is only between the browser and Cloudflare. They then connect to your reverse proxy, which might have SSL or it might be unencrypted. That’s a second jump done by re-encrypting the data.
How does the reverse proxy help, when the browser is connecting to Cloudflare not to the reverse proxy?
They explicitly use free DDoS protection as a way to get you in the door, and upsell you on other things. Have you seen them “drop your tunnel like a hot potato”?
Now obviously if their network is at capacity they would prioritise paying customers, but I’ve never heard of there being an issue with DDoS protection for free users. But I have heard stories of sites enabling Cloudflare while being DDoSed and it resolving the problem.
If you use DNS with proxy it still applies, you should get a Cloudflare certificate then. But yes, if you use Cloudflare as DNS only, then it should be direct. I believe you get none of the protection or benefits doing this, you’re just using them as a name server.
The Cloudflare benefits of bot detection, image caching, and other features all rely on the proxy setting.
Also if proxying is enabled, your server IP is hidden which helps stop people knowing how to attack your server (e.g. they won’t have an IP address to attempt to SSH into it). You don’t get this protection in DNS only mode either.
Basically if you’re using DNS only, it’s no different to using the name server from your domain registrar as far as I can tell.
I was in traffic on the weekend that was doing about half the speed limit, and passed a car that had been pulled over. I thought they must have done something pretty impressive to manage that.
For one, Aegis is more well known. Aegis has 6k+ stars where FreeOTP+ has about 500. This doesn’t mean it’s better, just that people are more likely to recommend it.
Aegis also has more features, and can import from many different authenticator apps (though as many don’t allow exports, this may require technical knowledge to get the database and feed it in). If you have root then Aegis can pull directly from the other apps.
Aegis claims they are better than FreeOTP because the encrypt passwords at rest.
One big difference is FreeOTP+ lets you not have to enter a pin/password to see the codes while Aegis you need to enter a pin, password, or biometric to see your codes.