You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be great to notify twister users easily about new, important versions/updates (1)
In the "easiest case", the update alert could be done like this:
create an official twister account which posts update notifications (2)
and these notif. then could be displayed outside of the normal timeline (e.g. in sidebar, top of the UI)
with a dismiss-button
Why like this? when e.g. the user is already subscribed to a notifier-account? (3)
user will see it faster (instead of being buried somewhere in the timeline),...
There might be other options... please contribute,... it should be that users are less trackable (as always)
(1) e.g. like the twister-core 0.9.30
(2) e.g. there's already @LetsTwist, but it might be useful to make another ?
(3) I guess it has to be discussed also which channels users prefer (perhaps they might see such things better on twitter, via mailing list, ...)
The text was updated successfully, but these errors were encountered:
I thought about loading location.host + '/.git/logs/HEAD' and https://github.com/miguelfreitas/twister-html/commits/master or something similar as iframes, parse the data and match commit history to make any notifications. it was just assumption and I never tried to implement it. but it may be useful only for twister-html, not for core.
It'd be great to notify twister users easily about new, important versions/updates (1)
In the "easiest case", the update alert could be done like this:
Why like this? when e.g. the user is already subscribed to a notifier-account? (3)
user will see it faster (instead of being buried somewhere in the timeline),...
There might be other options... please contribute,... it should be that users are less trackable (as always)
(1) e.g. like the twister-core 0.9.30
(2) e.g. there's already @LetsTwist, but it might be useful to make another ?
(3) I guess it has to be discussed also which channels users prefer (perhaps they might see such things better on twitter, via mailing list, ...)
The text was updated successfully, but these errors were encountered: