WIP: Conditional posting via favourites #109
Conversation
I don't know the correct way to reserve a migration ID, so I've named this `abcdef012345`. Guidance welcome. Also I expect to rename the existing `conditional_posting` storage, because it will be confusingly named if this new conditional posting method is added.
And fix behaviour for conditional toot relaying also.
|
@xurizaemon Thanks for this PR! I think one tricky thing about this is that a person has between 0 and 300 seconds in order to fav their message. In other words they might easily miss the window to fav. There may be a way to delay the processing of messages if you have this option enabled. |
|
👋 thanks! Yeah, I'm aware of the time window to fave - for me, that works OK, since the clients I use for Twitter and Mastodon make it straightforward to fave straight away. But it is a bit of a UX trick, and unpredictable if you're at the 0s end of things 😁 Doing otherwise would probably require more effort to track recent faves as well as recent statuses, and I don't think that's essential. 300s - is that the frequency the worker task is run at, or some other time window in moa that I didn't spot yet? |
|
Yeah I run 5 workers each every 5 minutes. |
Rather than requiring the user to include a hashtag to set conditional cross-posting (which I don't like because the user then has to mention other, less cool networks when posting, sullying their carefully crafted toots with unsightly metadata), this empowers moa.party users to opt into post relaying by tapping the ⭐ button, which is empowering and excellent UX.
See #108.
I'm testing this myself, it's WIP and I hope @foozmeat (and you!) will give some input on improving it.
Todo: