Loqiok, I added "https://venturebeat.com/2013/01/30/rubygems-org-hacked-interrupting-heroku-services-and-putting-millions-of-sites-using-rails-at-risk/" to the "See Also" section of /YAML
loqi.meedited /Reading.am (+118) "Zegnat added "https://github.com/reading-am/reading-extensions/pull/1#issuecomment-345412360 Fixed Firefox extension is en route." to "See Also"" (view diff)
snarfedtwo URLs and a photo. photos supposedly don't take up chars any more. counting the URLs as 23 each, it's exactly 280 chars...and yet twitter failed with "Tweet needs to be a bit shorter."
ZegnatThat’s why e.g. Japanese characters now get counted for 2 again, because they wanted to normalise content length for all languages (or something like that)
ZegnatSo I guess that is why they went for the little progress circle? Because they are using some weighting and comparing that to some sort of max permitted weight?
ZegnatYeah, that one simply counts using Python’s len(). So it is correct in all situations where implementations use the same (logical IMHO) counting. Twitter just decided to go with something that sounds like their own counting invention
sknebelso unless I'm missing something, they haven't published their weighting lists. so it's impossible right now to implement that right, without massive try and error
sknebel" The algorithm for length calculation is as follows: ... It is important to remember that this length is not the absolute length of the Tweet" ...
sknebelsnarfed: when I tried to follow your steps the tweet seemed actually decode to one char shorter than it showed for you (I url-decoded the request to twitter)
Zegnatsknebel, seen snarfed’s update for tweet counting? Looks like he is treating char ranges as inclusive. Was that in the doc and did I miss it or did he figure that out himself?
snarfedif i'm voting on your time, i vote for 1) nudging pfefferle to merge the two outstanding semantic-linkbacks PRs, and 2) drive everyone to figure out that mf2 plugin interaction standard