![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Track mentions
Title:
Track mentions
Area:
notifications
Summary:
Enable users to track when they're mentioned elsewhere on DW.
Description:
Any time someone writes an entry with <user name="desh"> (desh) in it, that should fire off an event that I can subscribe to and be notified for.
Ideally, this would fire every time an entry is posted that I have access to and that mentions my name, every time an entry that I have access to is edited and mentions my name but didn't mention it pre-editing, and every time the access rules for an entry are edited such that I now have access to it and my name's in it. (It's probably a bad idea to also notify for all old entries any time someone adds me to their access list, though.)
The same would happen for new/edited comments (either as a separate "when I'm mentioned in a comment" event, or as part of the same "when I'm mentioned anywhere" event).
EDIT: There are a lot of variations and pros and cons discussed in the comments below. For those who are not interested in reading all of it, I'd like to direct you to this thread, in which a so-far-noncontroversial modification is discussed.
This suggestion:
Should be implemented as-is.
11 (21.6%)
Should be implemented with changes. (please comment)
17 (33.3%)
Shouldn't be implemented.
19 (37.3%)
(I have no opinion)
4 (7.8%)
(Other: please comment)
0 (0.0%)
no subject
I would be All For if it were a new way of forming a tag that would notify, and the existing <user name> didn't notify, too. Basically, I just don't like changing a behavior that people have been relying on for ten years to do something so radically different, and notifying people that they're being talked about is radically different.
no subject
I agree with this. Technically, any mention in a public post is, well, public. But I think that making it opt-out in some fashion would greatly reduce the massive potential for drama, wanksplosions, and other social nightmares. Security is one concern, but drama is definitely another, and I'd prefer to massage features so that the drama potential is rather less. :)
no subject
no subject
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
no subject
IMHO, it would really need to be an opt-in (and probably an opt-in on both ends -- "yes I want to notify people that they've been mentioned" and "yes I want to receive notifications").
There have been umpteen times (notably during RaceFail) when I've mentioned someone publicly, and been prepared to have them find out about it, but would really not have wanted them to get an instant e-mail saying OH HAI YOU'VE JUST BEEN MENTIONED.
To sum up: W*ll Sh*tt*rl*y. L** G*ldb*rg.
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
no subject
no subject
I also think that the entry notification should only fire off on journals which permit either site search or latest entry inclusion. If someone has opted out of both of those things (and put in a robots.txt file) then I think the service should respect their attempt at security through obscurity, in this one specific instance where we're changing behavior they have come to rely on.
And I think when I'm mentioned in a comment definitely needs to be a separate event.
no subject
no subject
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
no subject
no subject
Now if only we could have it work cross-site too. Maybe if it were a literal trackback, and it triggered when somebody clicked on it ...
no subject
no subject
no subject
Actually, no. It is also the business of the person doing the talking.
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
no subject
no subject
no subject
I think taking the time to digest the feedback and writing a new proposal to be voted upon would be helpful.
no subject
Cent the first: I think that people are overestimating the possibility for drama here. While Dreamwidth and Twitter are different entities, I think it's telling that the same feature on Twitter manages to exist peacefully. The impression that I have is that most people fundamentally understand that not everything said about them will be glowingly positive.
Cent the second: It's already a simple matter to run a site search for your username to see who's been mentioning you, in entries at least. It would also be a fairly simple matter for someone technically inclined to write a script which did so automatically every hour and popped up a notification any time there was a new result.
no subject
I already have bloglink searches through most major services bookmarked (not many links since I stopped posting, strangely), but they're all unreliable, especially with DW.
If DW could tell me if someone links to me on any post I can see, that'd be cool, but I wouldn't want it clogging my inbox, a search page'd be enough.
no subject
no subject
Can Open ID comments make this user code and would trigger a notification? Maybe if was only proper accounts there would be less chance of getting notifications due to stuff like "I think this penis extension is great, ratcreature" or the like.
(no subject)
(no subject)
shorter username code with ping option
I don't use facebook or twitter or buzz, but now I understand that it's about inviting someone to join the conversation.
My vote is for creating a shorter way to write usernames:
@noracharles for <user name=noracharles>
@nora_charles.lj for <user name=nora_charles site=livejournal.com>
@noracharles* for <user name=noracharles ping>
(I don't know enough about code to know whether an asterisk would be the best ping symbol, it's just a suggestion.)
Re: shorter username code with ping option
Oh, yes. Never mind the faux-html for plain old usernames, but the LJ usernames are almost three times longer than the actual usernames...
Re: shorter username code with ping option
A shorter way to write usernames would be brilliant!!
Re: A shorter way to write usernames would be brilliant!!
Re: shorter username code with ping option
Re: shorter username code with ping option
Re: shorter username code with ping option
Re: shorter username code with ping option
Re: shorter username code with ping option
Re: shorter username code with ping option
Re: shorter username code with ping option
Re: shorter username code with ping option
Re: shorter username code with ping option
Re: shorter username code with ping option
no subject
If/when DW implements pingbacks, I think this would fit in nicely with that behavior. (IIRC, both the person doing the referencing and the person being referenced have to have pingbacks enabled in order to trigger one, which would circumvent cases of pinging people you don't want to ping.)