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
Right now the h-card is fetched only the first time a user is seen. This should be re-fetched periodically, need to come up with some trigger to run that since there is no explicit "log in" step in this scenario
The text was updated successfully, but these errors were encountered:
In addition, if an h-card lacks an icon, perhaps Meetable should re-fetch user info more frequently, in case someone just setup their personal site and then added their image later.
One user-interactive work-around for this could be for Meetable to refetech someone’s h-card every time they sign-in, that way, a “user fix” for this could be signing out and signing back in to Meetable.
Another more aggressive user-interactive work-around for this could be refetch someone’s h-card every time a signed-in user (re)loads a Meetable page, since Meetable obviously recognizes that the user is signed in (since it offers more UI options like RSVPing and editing).
That way the UX would be:
signed-in user updates their h-card with a new icon
user reloads whatever Meetable page they are looking at
Meetable detects the user page reload (same URL requested by same IP within 1hr? or use a cookie to note last time page was loaded by the user)
Meetable goes out and re-fetches the user’s h-card
That would feel more responsive and discoverable, since reloading a page to see an update is a very natural thing for a user to do.
Right now the h-card is fetched only the first time a user is seen. This should be re-fetched periodically, need to come up with some trigger to run that since there is no explicit "log in" step in this scenario
The text was updated successfully, but these errors were encountered: