birdie-team team mailing list archive

[Contribucious <contribucious@xxxxxxxxx>]

For info, even if Echofon on Mac uses the streaming API, on a few
occasions, it can happens that I don't receive tweets for a while (maybe
API calls limit here too —even if Echofon and other popular clients
don't seem restricted as other clients are— or more probably Twitter
servers that are not always "stable" or even as a normal behavior
desired by Twitter), and then all at the same time therefore. Seems that
it mainly happens in two cases: a guy tweet too much and then, I receive
only all at the same time OR I lost my Internet connection for a while
and then (of course in this case), BOOM, all notifications at the same
time.

Anyway, here is the result I would like to see in Birdie (which is forced for the moment, without streaming API, to have this behavior but… as a normal behavior, as tweet pulling only each few minutes):
=> http://i.imgur.com/CwlGP7v.png

Here, on this screenshot, the "1 More Tweet" notification —another name could have been "1 Additional New Tweet" so here— appears after 5 notifications.
So, I would like to see in Birdie that, by setting "Limit Notifications" to 5, I have really the 5 notifications AND ONLY AFTER THAT, a notification saying "X more tweets", as here. And not, as the limit set is exceeded, just a single notification saying "6 new tweets" (in this example) as it would have been currently the case in Birdie. Which is for me, completely useless and not helpful, as it's just the content that interests me (having at least a limited part of that through the system notification), the number only I know that it's often many… especially if we've many following of course.

And to be more precise, in Echofon, it seems that the limit of 5 is only when coming from a same person.
If it's my Internet connection that I lost for a while and receive many tweets from different people, I can in fact have like 10 or 15 tweet notifications, in addition to the "X more tweets" notification at the top of that if it's even more than that.
But the "Limit Notifications" setting is there precisely to let the user choose the desired value anyway.

But so, in resume, in addition to correct the bug reported in this
report, the more ideal solution would be that this "Limit Notifications"
setting becomes the number of notifications we see BEFORE HAVING A
GLOBAL NOTIFICATION saying, therefore, "X MORE tweets" (in addition)
here. As said in the report too in the section "Ideal behavior (just for
the bonus)". :)

-- 
You received this bug notification because you are a member of Birdie
Developers, which is subscribed to Birdie.
Matching subscriptions: Birdie
https://bugs.launchpad.net/bugs/1185480

Title:
  Have set "Limit Notifications" (…before having a single grouped
  notification) to 30, been notified only for the last tweet of each
  timeline update

Status in Birdie:
  New

Bug description:
  I tried to set the "Limit Notifications" value in dconf-editor to a large number (30 here for the test, but tried less too).
  According to the description of this value: "After limit, only show a summary notification."

  Expected behavior currently:
  At each timeline update (each few minutes), if less than 30 tweets were fetched (as set), show me ALL (individual) notifications.
  If more, RATHER show me a single notification telling me "X new tweets" (e.g. "34 new tweets" for example).

  What happens instead:
  Correctly, I don't have the notification "X new tweets" as less than 30 tweets are coming here in my test, at each tweets fetching (timeline update).
  But rather than having 8 individual notifications for the 8 new tweets for example as expected, I just have one: the one for the last tweet got.

  Ideal behavior, according to me (just for the bonus):
  At each timeline update (each few minutes), if less than 30 tweets were fetched (as set), show me ALL (individual) notifications.
  If more, firstly show me THE 30 NOTIFICATIONS AS DEFINED AS MY LIMIT -AND ONLY AFTER- a single notification telling me "X additional new tweets" (e.g. "4 additional new tweets" for example).

  ADDITIONAL INFORMATION:
  Would be cool to allow us to set the desired limit in a preference panel added in Birdie, by the way.
  But it's already planned that, I'm sure! ;-)

  => Anyway, either through dconf-editor or preference panel options,
  except if we can manage (built-in in OS or though a program) notify-
  osd behavior for each software individually (and therefore for
  Birdie), need to have the possibility to set the notification time
  duration for Birdie specifically and if we want or no to click on each
  to remove them (to have the time to read each, as even 10 secs can not
  be enough to read all tweets from notification in only 10 secs). Not
  very convenient though, soo need the streaming API here (even very
  limited!), to allow us to have few notifications at each time and
  therefore having no problem to read each (without having to think
  about a "click on each to close" system as too many shown at the same
  time but wanted to be read via notification though, as the
  notification system is still a useful system when surfing the Web and
  don't want to have the Birdie window always opened to read these
  tweets).

  TECHNICAL INFORMATION:
  OS: Ubuntu 12.04.2 LTS (with Cinnamon)
  Birdie version used: the r244 from the DAILY repository

To manage notifications about this bug go to:
https://bugs.launchpad.net/birdie/+bug/1185480/+subscriptions