New reply feature hides nickname
New reply feature hides nickname
| Issue ID: | 3350 |
| Issue Category: | bug |
| Component: | core |
| Priority: | major |
| Status: | active |
| Assigned: | Unassigned |
| Version: | 1.0 |
| Keywords: | context, conversation, nickname |
Since status.net & identi.ca upgrade to 1.0, replies coming from both platforms does not show involved nicknames any more.
This makes convos following very hard.
If I agree it's a usefull feature to save some space for 140 car. messages, it's really a nightmare to understand who is talking to who. Since context is available only when I follow all the people involved in a conversation, I can not rely on it most of the time.
More, convos between someone I follow and someone I don't follow previously alowed me to discover interesting people. This is not the cas any more, and that's bad for statusnet spreading.
Updates
#1
I read this issue 3350 alongside
unpredictable addressing when replying in conversation
#2
The idea is to get back @- prefixed replies and mentions as requested by many people on identi.ca yesterday.
I had a look on OStatus XML format and figure out all informations we need are in notice "metadata" in OStatus stream.
So, this could be usefull to provide a plugin for old version of statusnet so that people using these versions for their own instance could get old behaviour back (v1 is not impacted, except for clients using API).
For other client using API, XML and JSON answers already include all needed informations, so it could be made either on client side, or by plugin. Since we need a plugin for old versions of statusnet's web interface, it's basically easier to implement it so that API can benefit from it.
I will try to implement such plugin, but, as I'm not pure dev, it could take some time.
Let me know if someone with higher skills in PHP and better knowledge in statusnet starts it so that we can save time.
#3
+1
@- addressees should not be hidden.
Here's another reason:
there are many use cases for a dent, and not all involve a SN website or a client. dents can show up in all sorts of places - if that is not actually a client, a dent that is in reality addressed to someone but does not have this information *contained* in it is going to have less meaning because it's obviously incomplete. I don't buy the 140-chars argument: abbreviate, be more concise, or just write two dents (and link them together).
You can also subscribe to the
RSS feed for updates to this issue.