Mastodon: Support toots starting with #me

Created on 8 Mar 2018  ·  11Comments  ·  Source: tootsuite/mastodon

E.g.

#me cleans the fridge

It should be parsed like an IRC /me, i.e. it should turn the toot into an action-toot.

Unresolved questions:

  • [ ] What should an action toot look like?

  • [x] I searched or browsed the repo’s other issues to ensure this is not a duplicate.
  • [ ] This bug happens on a tagged release and not on master (If you're a user, don't worry about this).

Most helpful comment

Mastodon is not an instant messaging chat application, such messages are completely out of scope of the project.

All 11 comments

???

Remember that one time I also suggested #cw?

E.g.

lewd #cw I like to be lewd

Which would automatically add a content warning with everything before the #cw, and toot content with everything after the #cw?

#me is basically the same but it must come at the start of a toot and turns the toot into an action-toot. (Or we could use @me and make that a reserved username. (well, semi-reserved. use @me@instance in your own instance to refer to it, I guess.))

me
something like this, but looking better?

I don't know?

it should still show up on ppl's home feeds.

I have never seen what you're talking about. is that a mastodon-core feature?

No, there is no feature like this

I mean it looks neat I guess?

I don’t think it would be very useful, but it seems to be pretty easy to implement

I'd support statuses that can be defined with different status_types if that's what you're implying?

Example:
A shortcut key or added menu around the toot box with status_type options (ie: toot (default), action, notice, etc) when selected which would allow the "whats on your mind text box area" to function differently every time a toot was sent. Hell you could even change the color of the toot box too depending on which status type is selected.. And do pretty amazing things with it within the different timelines when those statuses render within the feeds.

Issue:
But, the thought process of adding a #tag isnt the best approach honestly as this information is stored in a text field as it also ruins the purpose of what a tag means. There's really no reason to have this information stored within the text column within a submitted status, and would make it fairly hard to migrate existing data of toots that are marked this way should a status_type were ever to be added to the model. Dont we just love parsing statuses?

To Do:
As I just said though, the model DOESNT allow the storing of statuses with a given status_type within the database model. This is a really good idea though, I'm on base. However, If anything, this feature request should be named around the following instead: "Add migration to add status_type integer column to statuses table with default value 0 which will allow us to properly define statuses as normal toots, actions, notices, etc"

Conclusion:
That way in the future at least the model will be prepared for it and it wont be a pain in the rear to ever implement. I could see potential of the timeline getting very colorful, if something like this were ever implemented. Surprised Gargron isn't that excited :)

Lets do it the correct way (pretty sure you'll agree) and not break and or confuse things. 👍

Have a good one.

SUPPORT TAGS AS AN (ADDITIONAL) ACCESSIBILITY FEATURE

Mastodon is not an instant messaging chat application, such messages are completely out of scope of the project.

Bummer ¯_(ツ)_/¯

Was this page helpful?
0 / 5 - 0 ratings

Related issues

sturmen picture sturmen  ·  67Comments

hach-que picture hach-que  ·  263Comments

inmysocks picture inmysocks  ·  128Comments

nclm picture nclm  ·  187Comments

Thann picture Thann  ·  63Comments