But they can only be globally unique if each instance has its own range of unique ID’s, otherwise they’ll have to check with the other instances to make sure the GUID they want to use hasn’t already been used. With new instances spinning up all the time you can’t really manage this.
I agree that the @instance provides a little more info, and it fits nicely in line with how user profile and community URLs are handled.
There was also a github issue report about putting the title in the URL, like reddit does, but I think this goes too far - lemmy has the ability to change the title and putting the title in the URL would just confuse things or lead to exploits (eg you put naughty words in the title then change it afterwards, but the URL still has the original title).
Done. I hadn’t seen that issue before, not that I really dig into github all that much.
However the issue is somewhat outdated. We do have instance agnostic links for communities and users now, and we have since I joined, which was less than 2 weeks after this issue was posted. We may need a new updated issue that focuses on posts and comments specifically.
I don’t think there’s a need for a GUID, in fact it would be quite difficult - every instance would have to check with every other instance to ensure that the ID’s are unique. Meanwhile, if we just have the federated host picking a number, then every other host uses that number followed by @hostinstance, we don’t need cross-checking but still have unique ID’s for everything.
For example, https://lemm.ee/comment/123456 would be a different comment to https://lemmy.nz/comment/123456 (as it is currently also), but the first comment could be found on the 2nd instance as https://lemmy.nz/comment/123456@lemm.ee.
Ah right, fair enough. I hadn’t realised Sync was doing that - I’ve been lazy and stuck with Jerboa.
The website seems to generally be the best way to browse lemmy anyway, particularly with its continued development. Apps quite often dont’ conform to things lemmy does, like automatically making instance agnostic links out of /c/fediverse@lemmy.ml, or the drop down box for typing a username and sending them a mention.
By my reading of it, you can still discriminate against pineapple pizza eaters, or any other group whatsoever, you just can’t harass, bully, violate their privacy or threaten them with violence. Which is fine by me, if someone wants to make a community only for ginger haired people and ban anyone they think isn’t naturally ginger, that’s their perogative.
This is the conversation I’m referring to:
https://i.imgur.com/uqW3P8o.png
It may well be that the lemmy.world admin account was compromised as a result of the hack, rather than to make it happen.
Apparently Memmy is immune to this, not sure about other apps. Someone else advised staying loggged out, and maybe be prepared to change your password after it’s resolved.
Fun fact: old reddit used to use one of the header functions as an underline. I think it was 5x # that did it. However, this was an unofficial implementation of markdown, and it was discarded with new reddit. Also, being a header function you could only apply it to an entire line or paragraph, rather than individual words.
The question hasn’t been legally tested, it’s no more certain now than it was before.
While it might be the case that the EU could come down on a user’s main instance for not deleting everywhere, really it’s no different to anywhere else - any app that uses an API or even just a simple scraper can get comments that a user posts, so as with those it could also simply fall to the user to go around each and every instance and request deletion. Arguably, the Fediverse is better than this because it does include a facility for deleting things from a host instance - the only issue is that the other instance might not necessarily follow that (as instances don’t necessarily run pure lemmy code, in fact they could run anything).