Conversation:
Notices
-
@simsa01 Nobody is forced to join !gnusocial.
-
@hikerus Please. I don't see the relevance to see that post in my home timeline based on my interest in GNU social oriented discussion. Do you really need to use the bangtag for it?
-
@hikerus I guess initiating a discussion on it is fine... but getting it bumped up in my home timeline for every response is at least not my favourite method of discussion. If we want that, we should implement subscribing to full conversation threads instead ;)
-
@maiyannah Yeah it's one of the zillions of things on "the list".
-
@orphean Posting it there at least means it's written down. When it comes to stuff I fix usually it's in the spur of the moment, as I seldom have time/motivation to sit down and explicitly look at bug reports :]
-
@orphean Putting it on the issues list also means anyone else can pick it up and tick it off.
-
*adds to the issue list that @maiyannah should update !GNUsocial because her instance doesn't properly fetch orphean's mention with the bare nickname in a conversation context*
-
@verius There's an ostatus:conversation
-
@maiyannah that (full mention for local users thing) is also a behaviour that's improved significantly in recent versions ;)
-
@maiyannah just make sure to backup files as well as database first .]
You can ping me on xmpp:mmn@hethane.se if there's some odd behaviour.
-
@gargron That's what we have ... lists for! They're a bit buggy since noone uses them, and noone uses them because they're buggy. But it's got something to do with the "tags" you can put on remote profiles (in the classic interface).
Tags you set on others can be viewed in a separate timeline and you can even use them to @-mention lists, like \@#debugging or something.
-
You're meant to be able to do that anyway. It's buggy. Probably doesn't work. It needs some love.
-
@lnxw48 Do you get a 500 internal server error? If so yeah, I noticed that too. Hence the \@ .)