3 ms·

I meant completely removed from the main stream and hidden in the details section. Sorry for the confusion. It still removes attribution from how most users vie

I meant completely removed from the main stream and hidden in the details section. Sorry for the confusion. It still removes attribution from how most users view tweets - from within the stream. How many users are likely to view the details for each tweet? Why is the attribution given less face time to the user? I would also disagree with the small type in the details section being "prominent"

seldo 16y ago
I don't know about others, but I do so all the time. The application attribution was always of interest to a minority of users. I think it makes a lot of sense to move it to the details pane, to keep the stream simple and give greater prominence to, e.g., the favorite link, which is much bigger in the new layout.
catch23 16y ago
when facebook changed user profile pages to be more stream-centric than app-centric, developers complained too, and subsequently destroyed the user base for a few apps that relied on user profile canvas presence. However, I think the change was for the better and the good apps that survived focused more on the user stream than a flashy annoying front page widget. I think anyone developing heavily for one platform should always keep in mind that you'll need to pivot as quickly as the platform company.
pierrefar 16y ago
still removes attribution from how most users view tweets I thought most users view tweets not through the twitter stream on the web but using clients. The clients may or may not show the posting app's attribution, so I don't see this as a major shift of the status quo. Also the mobile web version doesn't have this attribution either: http://mobile.twitter.com/ http://mobile.twitter.com/
- dho 16y ago
  According to http://blog.twitter.com/2010/09/evolving-ecosystem.html http://blog.twitter.com/2010/09/evolving-ecosystem.html most people use Twitter's web client.
  - pierrefar 16y ago
    That's a very misleading graph. It's not about how many people read tweets through the different channels. There are many reasons to log into twitter.com, and so the graph needs to break out (or at least explicitely state) how many people read tweets on twitter.com. Another, more important, point: there is probably a long tail effect here. I have a hunch that when you aggregate all reading via API vs reading via the web, the breakdown would show a huge API to web ratio.

seldo 16y ago

I don't know about others, but I do so all the time. The application attribution was always of interest to a minority of users. I think it makes a lot of sense to move it to the details pane, to keep the stream simple and give greater prominence to, e.g., the favorite link, which is much bigger in the new layout.

catch23 16y ago

when facebook changed user profile pages to be more stream-centric than app-centric, developers complained too, and subsequently destroyed the user base for a few apps that relied on user profile canvas presence. However, I think the change was for the better and the good apps that survived focused more on the user stream than a flashy annoying front page widget. I think anyone developing heavily for one platform should always keep in mind that you'll need to pivot as quickly as the platform company.

pierrefar 16y ago

still removes attribution from how most users view tweets I thought most users view tweets not through the twitter stream on the web but using clients. The clients may or may not show the posting app's attribution, so I don't see this as a major shift of the status quo. Also the mobile web version doesn't have this attribution either: http://mobile.twitter.com/ http://mobile.twitter.com/

dho 16y ago
According to http://blog.twitter.com/2010/09/evolving-ecosystem.html http://blog.twitter.com/2010/09/evolving-ecosystem.html most people use Twitter's web client.
- pierrefar 16y ago
  That's a very misleading graph. It's not about how many people read tweets through the different channels. There are many reasons to log into twitter.com, and so the graph needs to break out (or at least explicitely state) how many people read tweets on twitter.com. Another, more important, point: there is probably a long tail effect here. I have a hunch that when you aggregate all reading via API vs reading via the web, the breakdown would show a huge API to web ratio.