-
Notifications
You must be signed in to change notification settings - Fork 52
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
Twitter’s 280 chars #773
Comments
thanks for filing! last we checked, the API still doesn't support 280 chars, https://chat.indieweb.org/dev/2017-09-27#t1506565409291000 , nor does it have a way to determine whether a given user has access to them, even in the UI. so, we probably need to wait until they're rolled out to everyone. |
There had been an interesting work around to fool Twitter, but they closed that loophole pretty quickly. Links found through here: http://boffosocko.com/2017/10/18/heres-a-hack-so-you-can-tweet-with-280-characters-right-now-the-verge/ |
Just updating this with the fact that Twitter is officially supporting 280 characters. There’s an announcement here supposedly it doesnt’t require any updates if the library is using the most up to date endpoints. |
thanks for the nudge @EdwardHinkle! updated in snarfed/granary@26b29a4 and deployed. bridgy can now tweet 280 chars. |
Yay!! Success 💯 💯 💯 Thanks! |
Couldn’t find this one on here.
Now that Twitter seems to support 280-chars, can Bridgy post them?
I wrote a 173-char note today to see what happened, but bridgy cropped and added a link (I have it on omit_link=maybe indeed).
I heard that there was a way to fool a third party app into showing the 280 UI, which would mean that currently it’s only a UI restriction. In that case, Bridgy could use them already. Don’t know the fine details yet.
The text was updated successfully, but these errors were encountered: