Recent activity
Subscribe to this feed-
Seth started following the question "Last updated time not accurate at startup ?" in atebits.
Seth reported a problem in atebits on October 23, 2009 01:55:
When you click the Tweetie menubar icon to hide the app after clicking a link in a tweet, Safari gets hidden as well- Safari open, iTunes open (or any app, it doesn't matter), Tweetie open
- bring iTunes to the front
- bring Tweetie to the front
- click a link in Tweetie
- Safari comes to the front but only the window Tweetie has just opened, not the whole app
- click the Tweetie menubar icon to hide Tweetie
- iTunes comes to the front (which covers the Safari window)
It looks like what's happening when you hide Tweetie by clicking the menubar icon is that the OS is bringing the previously frontmost app back to the front. This is not the desired behavior however. If I click a link in a tweet and then hide Tweetie, what I want to happen is for Tweetie to hide itself and to have my newly opened Safari window still frontmost.
I can't decide if I want all of Safari brought to the front or if I only want the new window(s) to remain in front (where I put them, so to speak), but I certainly don't want iTunes to jump back in front of what I was doing. It's oddly disconcerting, especially if I open several Safari windows by clicking links in Tweetie, to have them all suddenly "disappear" when I click the menubar icon.
It's like there's two different behaviors. Normally when I click the menubar icon Tweetie gets hidden and I get taken to my last used app. But in this specific case, it feels like my last used app is misidentified as not being Safari. As a user, it feels like clicking the menubar icon is hiding both Tweetie *and* Safari (even though that's not really what's happening).
Seth replied on October 20, 2009 20:17 to the idea "Change timestamp from relative to absolute?" in Thing Labs:
As an alternative idea that might be easier to implement (or might not), how about having the timestamps stay the way they are (relative time) but when you hover over them you get a tooltip which gives you the absolute time and date?
Even a "last updated at xx:yy on aa/bb/cccc" line in the large green box above the tweets, maybe right next to the Home label, would be an incredibly helpful addition.
Seth reported a problem in Thing Labs on October 05, 2009 15:55:
Clicking Twitter user names doesn't work as expectedWhen you hover over a link, the browser's status bar tells you you'd go to that page in a new window. When you click the link, this is what happens (correct behavior). When you hover over a Twitter user name it says the same thing. However, when you click the Twitter user name you end up replacing the Brizzly page with that user's page (incorrect behavior). This is almost never what I want but is also completely unexpected because the browser is telling you in advance it's going to do something different (which also happens to be the proper behavior).
What's also weird is that if I command-click the Twitter user name I (correctly) get a new tab in my browser window with the user's actual Twitter page (which is what I generally want) rather than the Brizzly page.
The reason I would click a Twitter user's name is usually to get to their Twitter page so I can see who they're following and to see who's following them. Unfortunately, I can't get this information from the Brizzly page (yet?) so I have to go to the actual Twitter page.
I'm using Safari 4.0.3 on Mac OS X 10.6.1 as my main browser. However, I tried Firefox 3.5.3 and the behavior is different (but still incorrect). In Firefox, the status bar does *not* say it will open in a new window. However, a link *does* open in a new window (correct, even though Firefox doesn't tell you that's what it's going to do) while Twitter user names still open in the Brizzly window (odd behavior), unless you command-click them, which makes them open in a new tab (correctly).
So Firefox basically behaves the same way except that it doesn't tell you in advance that it's expecting to open a new window (even if it will). Note that Firefox not telling you is not a Brizzly problem as it seems that Firefox works that way on all sites.
This is getting complicated, so let me give you my executive summary:
Correct behavior:
- click link, opens in new window
- command-click link, opens in new tab
- command-click user name, opens in new tab
Incorrect behavior:
- click user name, opens in same window
- status bar says all links of all types will open in new window (Safari)
(Note that the screenshot says "in a new tab" but that's due to the fact that it's a screenshot. In real life it says "new window.")-
Seth started following the idea "iPhone?" in Thing Labs.
Seth reported a problem in Thing Labs on September 30, 2009 22:33:
Direct message fails with no explanation if recipient is not following youIt's possible to get all the way through the entire DM process all the way up until it fails because the recipient is not also following you. This is a total bummer because by then it's too late and what you typed is gone. I like that there's a Message button under each person's icon, but when I click that button, *that's* the appropriate time for you to look up behind the scenes to see if that person is following me.
I should not be able to get all the way through preparing a DM only to have it fail with no warning or explanation. All that happens is that the little status area under the Brizzly logo says something like "failure sending message," which is not much help at all. I happen to be following someone on both their personal and business account, but they're only following me on their personal one. If this had happened with someone I didn't know I would probably not have been able to figure out what had happened.
The best behavior (from a user's perspective) is to click the Message button and right away get either a "this person is following you so go ahead and type a message to them" box (the way it works now, more or less) or I should get a "this person is *not* following you so do you want to @them instead or do you want to cancel" type of notice. At the very least put what I typed in as a draft and give me a notice that that's what you did. The current "couldn't send" behavior is just not enough information. Heck, I would have been happy to have you put what I typed in the clipboard for me.
Seth replied on September 30, 2009 18:10 to the idea "Change timestamp from relative to absolute?" in Thing Labs:
I'd like to see the timestamps get a bit smarter. Anything under an hour should say how many minutes ago it was. Anything under, say, 4 hours should say how many hours ago it was. Older than that should have the relative day (i.e., today, yesterday) with the time. Anything past yesterday should just have the absolute date and time. This mix of relative and absolute should make everyone happy (yeah, right!).
My 4 hour time period is not set in stone. It could just as easily be 6 or 8 hours or even as long as 24 hours as an extreme choice. I'm not sure if 16 hours makes intuitive sense to most people, but certainly 4 hours does.
This reply was created from a merged topic originally titled
smart timestamps: use both absolute *and* relative timestamps.
Seth replied on September 30, 2009 00:03 to the idea "Need an un-why command?" in Thing Labs:
I don't want to close the whole Trends and News section with a disclosure triangle or anything. I actually *like* when they're all listed but closed. I like the Why but I would also like to have a Close/Collapse/Hide/UhWhy if the explanation's open. Note that once they're closed they stay closed even when I load new tweets by hitting the R key. If I click the Brizzly logo or reload the whole page they come back (which is what I don't want).
Seth replied on September 29, 2009 16:27 to the idea "Need an un-why command?" in Thing Labs:
Hmmmmm. That's not quite how it behaves in my browser (Safari 4.0.3, Mac OS X 10.6.1). Most of the time none of the Trends are open, especially if I have the site up for a long time (as I tend to do). I'm guessing that they somehow close on their own when the page refreshes, but as I said that's just a guess. Also, when the first trend *is* open, or any trend for that matter, there isn't any "why" showing. All I get is a Search link and a smaller Explain this Trend link as well. If there was a Why link I could click to close the Trend that'd be fine.
I just tried it in Firefox and got basically the same results by the way.
I find the Trends interesting, but I don't want the visual distraction of having one of them open automatically. I occasionally click one I want to see, and I like the feature, but there's already a lot of things going on on the page. Also, it's not always the first one that's open. Sometimes one of the middle ones is the open one.
As I said, I like the Trends and News. I'd just rather it be up to me when I see them as opposed to having one open all the time, and I'd also like to be able to close one if it's open.
Seth shared an idea in Thing Labs on September 28, 2009 22:45:
Need an un-why command?Is there any way to "un-why" something in the Trends and News section? Once I've clicked one of the Why links there doesn't seem to be any way to close it back up again.
Seth posted a topic that has since been removed from Thing Labs. see the change log
Seth shared an idea in Thing Labs on September 28, 2009 20:55:
auto-age timestamps when idleIs it possible to have the timestamps age automatically when the page is idle? It seems odd to have the last tweet say "a moment ago" when it's been sitting there for half an hour. Automatically refreshing the tweets is fine, but if the timestamps don't age you're not sure if there aren't any new tweets or if things are simply not working. The page needs to keep updating even if there are no new tweets.
Seth replied on August 16, 2009 13:27 to the problem "Tweetie for iPhone returns log in error" in atebits:
I have this issue also, but it seems to me like it only started in the last couple of weeks, which coincidentally is about the same time iPhone OS 3.0.1 came out. I'm wondering if something in 3.0.1 is blocking Twitter authentication on the iPhone, because I'm having the exact same problem with my old Twitter app (which I just reinstalled so I could test this). On the other hand, it could just as easily be a change in Twitter that happened at around the same time.
Twitter works fine in Mobile Safari, but Tweetie can't seem to authenticate for me.-
Seth started following the problem "Tweetie for iPhone returns log in error" in atebits.
-
Seth started following the problem "Launching Links no longer works." in atebits.
-
Seth started following the idea "Tweet selection colour in v1.2 is not visible enough." in atebits.
Seth replied on May 27, 2009 13:40 to the idea "BUG: Can't select text of tweets to copy/paste in 1.2" in atebits:
Are you sure? I can select and copy text in mine. I just updated to 1.2. What it's doing is making the selection but the background highlight color is white, rather than blue (my chosen highlight color). At least on my copy it *is* selecting the text, but you just can't really see that it's doing it. It does work, though.
Loading Profile...


