Most of us are Reddit refugees, and probably clicking more random links than we ever did before on websites we’ve never seen before. This whole experience feels like the old internet, but also throws up insane red flags with a modern internet perspective. What are the cybersecurity weaknesses we should all be looking for, and what are the best practices?
Here’s my reason for posting this. As I search for new communities across instances to follow, I sometimes end up clicking a link and I’m no longer logged in. In the corner, that could be a Sign In link or it could be phishing. It’s likely due to me not understanding how to properly navigate this system, but there’s nothing stopping someone from setting up a sight like this as far as I know.
Thoughts?
If you’re navigating to another community on their instance, you won’t be logged in. When you’re seeing that, check the URL. If you’re on lemmy.ml, you’re still on your instance; if not, you’ve navigated to that instance.
There’s multiple ways to structure links, some of which will take you to that community via your instance, some not.
Could it be phishing? Sure. But far more likely, you’re just on another instance where you don’t have an account (or at least an active login).
Like I said… Most likely legit, but these issues will arise. This whole Fediverse thing feels like the first big thing to happen for whatever comes next. Which is great, but it would be foolish to think scammers, with modern tools wont try to exploit it. We all have some internet hygiene to figure out.
Do you mind giving a short explainer of proper link formatting? I was struggling with this just a little bit ago
As far as I know, there are a few different link formats, and how well they work depends on which frontend you’re using:
- amateur_radio
- !amateur_radio@lemmy.radio (The Web interface gave me autocomplete options for this)
- https://lemmy.radio/c/amateur_radio
EDIT: At least using the web app, the first link is relative, and the others are not. So I think the correct format would be /c/<community>@<instance> for communities outside your instance.
Those opened in the in app browser on Memmy. Testing here
If you link directly to the full URL (including the instance), you’ll take anyone who clicks it to that instance, and they won’t be logged in. This is usually not what you want. Example: https://pawb.social/c/tech - This link will take you to my instance.
If you remove the instance URL, and just leave /c/communityname@instance - for example, /c/tech@pawb.social - the link will still take you to the community, but you’ll still be on your instance. This is usually desirable.
Basically, instance -> community = link to that instance. Community -> instance = link to the community in whatever instance the user clicks it in.
You can also use ! instead of /c/ - I think this might work better for Kbin users (since they use /m/ instead of /c/ - can’t verify this). In that case, it’d be: !tech@pawb.social
Thanks for the explainer! Doing some testing cause your example didn’t hyperlink on Memmy
c/tech@pawb.social /c/tech@pawb.social !c/tech@pawb.social !tech@pawb.social test text /c/tech@pawb.social /c/Lemmy@lemmy.ml
Weird. Not sure when your example didn’t link, because it did in my comment ¯\(ツ)/¯
Edit: I’m back on browser. Everything that hyperlinked works properly. It’s a Memmy issue
I won’t get tired of posting this everywhere it applies :D
I made this userscript, which rewrites all links everywhere (not only on Lemmy) to always point to your home instance. So the link in your comment actually looks like this to me:
i.e. even though you tried to link to your instance, my script rewrote your link back to my instance so it’s working fine :D
But of course I can still hover over the icon to see how your link originally looked:
So just out of curiosity, since you’re the first person I’ve seen actually point out optimal linking with the ! Symbol, I have to ask how you pronounce it. For me, ! will always be “bang”, so I’m just curious what the pronunciation is.
Is there a similar way to handle linking to specific posts? I think all post urls are unique to that specific instance and I haven’t seen any way to do a translation between instances.
The formatting !community@instance should let a user click through but still be logged in on their own instance, so that you can still read posts, vote and comment. If that doesn’t work, you can try entering that same thing into your instance search bar, or in your browser enter https://your instance/c/community@theirinstance
It should all get a lot smoother as this platform is developed!
I haven’t tried linking to a specific post on another instance, so I’m not sure of that formatting hmm
You’re likely no longer logged in because you visited another instance. For example, if I’m browsing from lemmy.ml but click on a link to !baking@kbin.social, now I’m kbin and not Lemmy.
What you can do from your instance is go to your browser, paste the magazine or community url into the search bar, then subscribe from their sidebar.
I understand why this happens, but I consider this is a usability issue that the Lemmy devs should try to resolve. It’s not an easy problem to solve, though.
Federation is great, but it does tend to make certain interactions more complex. If Lemmy wants to retain normal users and not just highly motivated and/or technically adept people, the UX issues federation introduces need some serious work.
- Use a mail forwarding service to generate disposable e-mails used to sign up, if you accidentally give it to someone else it doesn’t expose any other accounts and can be easily replaced by a new one.
- Use a password manager to ensure a strong and unique password.
- Use a JavaScript blocker so you only allow the required JavaScript to make the website work and prevent automatic downloads.
I’ve been doing these in general recently and it’s good privacy a security practice. Also slowly replacing my main e-mail address in different service accounts with disposable forwarding e-mail addresses.
Edit: Other than that read a bit more about Lemmy and fediverse workings, verify what instance you’re viewing and navigate to the desired community via your instance as others have mentioned.
I would like to underline and insist on using unique passwords. Many users like myself are joining small instances to get better performance and reduce the strain on the main servers, but anyone can spin up an instance and then poof, your password is gone if they can get you to sign up!
This was always the case for normal websites on the internet however. I strongly recommend everyone use a good password manager to prevent one breach from cascading into a breach of all your accounts. It’s good OPSEC.
Also, check which instance you’re signing into before you give them your password. Accidentally trying to log into the wrong instance with an account for a different instance is the same as handing them your password. A community could easily be hosted on some tiny server somewhere by a guy named Joe and do you trust him with your password?
Just to add, lemmyverse.net was really useful to me in first subscribing to communities I searched, you can click on the house button at the top and select your particular instance, then any community that pops up in your search you can just click on and subscribe/interact with because you’re doing it through your homebase
Honestly, I think the #1 problem to be concerned about right now is that there a lot of people self-hosting for the very first time, that maybe don’t really have much experience with hosting or moderation. It’s tough! There can be a lot of drama, random software failures, lost data, and disappointments that can happen. An instance can go under at random, at any time.
It sounds bad. In practice, the day-to-day can be fairly smooth sailing. A lot of people just kind of need the experience, need to make sure they’re not the one person moderating thousands of people on a serer. Making sure that moderation is a community effort, that the server has backups, and that there are channels for donations to support the instance - those things go a long way towards long-term stability.
