-
• #4702
Subtle change... if you @ someone and they had a short username and not many posts... they never appeared on the selection list. This made is impossible to add them to events, share messages with them, grant them permissions, etc.
The change is that if the username precisely matches someone, then regardless of whether they have posted much, they will be the first choice on the dropdown.
-
• #4703
This is the one I'm having trouble with. It doesn't add you.
-
• #4704
If you enter Velocio, I don't appear in the drop down at all?
The database knows that yourself and JD are in that one... not me.
But you have to click or select me once I've appeared in the dropdown. Just coming out when I've been highlighted isn't enough.
-
• #4705
-
• #4706
Once I click Close, nothing happens. You're not added to the message viewer list.
-
• #4707
How strange... I suspect that the bit of JavaScript to do that is somehow broken.
Can you CTRL+F5 it.
-
• #4709
No, one of JD's sales threads wasn't appearing.
I do own Rapha.. I own quite a few of their magazines :)
-
• #4710
Got it. NoScript was blocking microcosm.app but microcosm.app wasn't appearing in NoScript's list until the CTRL-F5. Sorted thanks.
-
• #4711
just got one of these:
1 Attachment
-
• #4712
Just found another problem with escaping reserved characters in mark down, had to change
[merk](https://en.wikipedia.org/wiki/Merk_(coin))
to
[merk](https://en.wikipedia.org/wiki/Merk_(coin\))
to avoid a superfluous close bracket, i.e.
merk
to
[merk](https://en.wikipedia.org/wiki/Merk_(coin))Obviously many Wikipedia entries end in close brackets (pretty much any name or entity which requires disambiguation)
-
• #4713
Reported that to the Markdown parser project that we use: https://github.com/russross/blackfriday/issues/116
-
• #4714
I quite like the idea of having a full username history on profiles somewhere, not necessarily as immediate as hovering over names in conversations. Not a history even, just list of names in choronological order.
-
• #4715
I don't mind implementing it... but if I do so, no-one is going to have the ability to edit/remove or hide any part of the history.
If everyone is cool with this, I'll do it.
-
• #4716
(not sure you'll get an everyone affirmation)
-
• #4717
If everyone is cool with this
Presumably it won't be retroactive, so if you just put a warning next to the 'change user name' input people will know that if they really want to change their ID, they will need to create a new user rather than just renaming their existing one.
-
• #4718
This has two problems:
- A loss of privacy. One of the biggest reasons people requested name changes is because they wanted to not be found by employer/ex/family/etc. The vast majority of people user the same username everywhere, until they determine it's a risk and need to change it. We'd be permanently linking your old identifier to your new one.
- As sign-in is via email (because you can change your username), they need a whole new email account just to get a new username.
The current situation is the best for privacy, and security.
But if people feel that this has eroded trust, as people could change their name and you cannot see the history of who they were and carry trust forward... then I can fix that, but it comes at the cost of some privacy.
- A loss of privacy. One of the biggest reasons people requested name changes is because they wanted to not be found by employer/ex/family/etc. The vast majority of people user the same username everywhere, until they determine it's a risk and need to change it. We'd be permanently linking your old identifier to your new one.
-
• #4719
they need a whole new email account just to get a new username.
That's the difference between geeks and normal people I suppose; creating a new email alias is something I do for pretty much every different site which wants an email address.
-
• #4720
Does Persona support addresses in the format
joebloggs+differentiator@gmail.com
which SMTP would route to joebloggs@gmail.com but could be treated by Persona as either a distinct address or as an alias... might be complicated by the OAuth & Gmail parts.
-
• #4721
Reported that to the Markdown parser project
Also just had to escape the first * in this comment https://www.lfgss.com/comments/11829971/ to allow vice versa to be italicised without having the whole second paragraph italicised.
-
• #4722
That's one of the joys of Markdown that I dislike. According to the syntax, it's correct that it would italicise.
-
• #4723
Yes, I tested that.
-
• #4724
If someone is concerned enough that they need to disassociate themselves from on old 'nym entirely, are they free to create a new account?
Unless you decide to link email addresses as well as user names, and out all aliases, of course.
-
• #4725
it comes at the cost of some privacy.
If it's not searchable, either here or by indexing, how much of an issue is that?
If someone wanted to find TW2, they could search for the user and not find them. They would need to already know that my new pseudonym was TW in order to link them.
I guess it would be possible to click on every single username and view the name history, or programmatically scrape the same. But if you're the sort of person that does that, you could just as easily derive all previous names from the wayback machine or Google's cache.
I'm not in that one, I cannot see it.