-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Semi-automatic tweeting #23
Comments
Hmm I like "Publish & Tweet" being a one click thing, but I feel your pain; let me propose a few alternatives.
I agree with this. The "Share on Twitter" form should not truncate the tweet automatically -- this makes it a PITA to manually edit down, especially if we're only a few characters off |
That sounds cool. In general, I think there should be some syndication log at the bottom (including tweets) like wordpress has, because although redwind knows which syndications succeeded/failed, ATM if I don't remember whether I did "publish quietly" or not, there's even no indication of that 😉. Does it make sense? |
So we've got a couple of competing goals here; the "new note" interface is already pretty cluttered on mobile, and I have to scroll more than I'd like to to use it. Something closer to Twitter's UI is sort of where I'd like to get. Obviously since we're doing more than twitter, it can't be quite that simple, but still, a target: I'm hesitant to add more stuff without majorly simplifying and cleaning up the current interface. The tagging UI could be tightened up pretty easily. Attaching images is clunky at best (and works differently if you are posting a photo vs. a note with an image attached), and the Location checkbox stuff is total garbage, and I don't even know if it works. As you can see I'm a bit lost :)
There is a "Syndication" text area at the bottom of the edit post page, though you have to click the Btw, Post Quietly just suppresses webmentions, doesn't actually have anything to do with syndication.
I don't understand what "plain tweet" would do.
I'd like to add a log of success/failure on all the background jobs (see #21) accessible somewhere in the UI, though I'm not totally sure how that fits in with what you are suggesting in the post UI. |
In that case, I take back most of what I said (anything to do with adding a tweet editor to the editor gui). 3 simple things could fix all that ails me:
|
The fix of #12 only addresses some of the incidents of "not what I wanted to tweet" (I keep having those).
Here's what I suggest (I can write it if you agree in principle):
publish+tweet
to simply open the tweet form (filled with "best guess") and let the user review/edit it in order to minimize shame 😉.The text was updated successfully, but these errors were encountered: