a new fix?
![]() ![]() |
in my opinion, it is wrong of twitter to not send all my replies to my followers. some friends who just signed up at twitter to keep in contact with me think all i do on twitter is rant--they only see my unaddressed tweets and never see my conversations (at least my half). probably a large number of my followees were followed to get both sides of the conversation with other followees. my friends are not motivated to follow more people because they don't even know i'm chatting with other people. so anyway, i'll just throw this suggestion out: how about clicking "reply" and instead of in-reply-to data, your script puts a link back to the original tweet? so a reply to a tweet at http://twitter.com/DyNama/status/15149118722 would not have in-reply-to data and might look like: .@DyNama i totally agree →lnk.in/748f the url shortener lnk.in doesn't require the http:// and is still on 4 characters so it only uses up 12 characters. i just chose lnk.in arbitrarily, and by default it shows a preview page before forwarding but that can be turned off. this is a whole new direction for your script and i don't even know if it is doable. |
![]() ![]() |
I agree completely regarding Twitter's reply filtering; it's why I created both this (to make outbound replies public) and CatchUp (for seeing others' replies). Your suggestion is much better than anything I could invent, so we'll try it out. The latest version includes an [sl] link for adding a short-URL reference to the parent tweet (this is a manual process to avoid wasting short-URLs). I've chosen a different arrow and gone with TweaK.tk for absolutely minimal links (3-character overhead), but preserved your core idea and your HTTP-stripping. I've also retroactively credited you as "DyNama". Thanks again for all the help. |
![]() ![]() |
what font do you use? U+21B7 didn't show up in the font i had installed on my winXP laptop. in fact http://www.fileformat.info/info/unicode/char/21... showed me that none of the fonts i have installed have the "clockwise top semicircle arrow", including arial, tahoma, and trebuchet. but i have lots of fonts available, installed DejaVu Sans, set it as the default font for all of windows, and voila! looks pretty nice. later i changed it to lucida sans unicode cuz it was a better looking font. i've probably been missing some things on the net, not having a unicode font installed. i wondered about wasting shortened links, i even pondered upon the philosophy of link shorteners that would expire and be reused--and i see that tweak.tk does just that. thanx for the credit! this is pretty cool. |
![]() ![]() |
I like both DejaVu Sans and Lucida Sans Unicode (Unicode support is important). Arial Unicode MS isn't bad either. If U+21B7 doesn't work for you, you can change it on line 159 (gstrShortenerPrefix), though I strongly recommend keeping it as a Unicode-identified arrow. If you like, I can also make a User Script Command to change the shortened prefix. |
![]() ![]() |
you mean an upfront option to change it to a different arrow? u+21b7 is fine for me, but i didnt have a unicode font on my 6-year-old computer, i wonder how many dont. i liked lucida better than dejavu, but ended up installing the 650mb trial version of the MS Office2007 just to get a copy of Arial Unicode! (just days before the release of Office2010!) tweak.tk is a fine url shortener, tho it doesnt look like a "traditional" url and isnt a link. if i have 7 extra characters, i go ahead and add the http:// which makes it a link, and sometimes i think it looks better at the end of the tweet so i cut and paste it, tho i still need a dot in front which will use another character. tweak.tk links are almost certainly going to expire in 90 days, but that's probably ok, it's hard to guage how important the linkback is. besides, it's twitter's fault! the biggest problem is that if the tweeter you're replying to has protected his/her tweets, you never get the preview and therefore never get the RA RT SL buttons. i try to notice the lock symbol and copy the tweet to the clipboard before clicking on Reply to handmake a retweet. |
![]() ![]() |
I too missed the http: on short links, so the latest version keeps it if enough characters are available. I've also tried to preview protected tweets; please let me know how it works for you. You can easily add a trailing short link by clicking [SL] again. Finally, tweak.tk URLs shouldn't expire. They claim (http://my.dot.tk/tweak/?show=technical ): "We never remove shortened URLs, as long as they are created in accordance with our terms & conditions." |
![]() ![]() |
this script just gets better and better! thanx! in theory anyway--right at this moment the preview says "undefined", and pressing the RT button actually goes to the previous tweet, doesn't copy it into the edit box. i've refreshed a half dozen times and preview isn't working on protected or unprotected tweeters. i even went back to the jun 1 version then installed the june 9 version again and it still says "undefined". i thought i read that tweak.tk links expire if they dont get 25 clicks in 90 days. i looked all over their website but i don't think i saw the page you sent. |
![]() ![]() |
Sounds like a Twitter issue. Try again after this spell of fail whales is done. |
![]() ![]() |
twitter's been having a lot of issues lately! i have got the 9jun version to work, but i'd rather have this script work the 1jun way than not at all, so i've switched between the last 2 versions a dozen times this week. |
![]() ![]() |
Have you tried over HTTPS? If you're still having problems, it may stem from the protocol differences. |
![]() ![]() |
is that as simple as going to https://twitter.com to sign in? i had never used that till now, but even in https i still get "undefined" in the preview most of the time whether the tweeter is protected or not. my tweet count just returned to normal today so perhaps twitter is still having problems. |
![]() ![]() |
i still have problems with this latest version. i don't get "undefined" much anymore, i get "unable to retrieve data" or "sorry, you are not authorized" messages, so i still switch back and forth between the last two versions. are you saying i should use https? as an aside, i've seen tweets and blogs from people who *don't* want to see all my replies and complain that the "dot fix" deprives them of the choice. their only other option is to unfollow, so i have been slightly more judicious which tweets should keep the in-reply-to data and which should go to everyone. i just have to take off the dot prefix manually... |
![]() ![]() |
You'll probably have better results with HTTPS, at least with "not authorized" errors... I suspect that all the "unable to retrieve data" problems are requests failing on Twitter's end. As for prefixed/unprefixed replies, I also try to appropriately self-filter. This is the world we live in since Twitter's kerfuffle. |

