UI or a separate external app π
UI or a separate external app π
- 0500 UTC (original time)
- 0000 UTC
- 0300 UTC
- Something else?
- 0500 UTC (original time)
- 0000 UTC
- 0300 UTC
- Something else?
* 0d751800 2022-11-11 | Add FeatureFixCachedTwtersForArchivedFeeds (fix_cached_twters_for_archived_feeds) to avoid caching Twter objects for Archived Feeds (HEAD -> filter_and_lists, origin/filter_and_lists) [James Mills]
And blacklisting
^lyse\\.isobeef\\.org$ (_because I couldn't figure out how to go fix broken/bad Followings of Users on my pod easily_) there should only be two Twter objects for you now, @lyse and @lyse-backup (as expected).Hopefully we don't run into any other weird edge cases π
* 0d751800 2022-11-11 | Add FeatureFixCachedTwtersForArchivedFeeds (fix_cached_twters_for_archived_feeds) to avoid caching Twter objects for Archived Feeds (HEAD -> filter_and_lists, origin/filter_and_lists) [James Mills]
And blacklisting
^lyse\.isobeef\.org$ (_because I couldn't figure out how to go fix broken/bad Followings of Users on my pod easily_) there should only be two Twter objects for you now, @lyse and @lyse-backup (as expected).Hopefully we don't run into any other weird edge cases π
* 0d751800 2022-11-11 | Add FeatureFixCachedTwtersForArchivedFeeds (fix_cached_twters_for_archived_feeds) to avoid caching Twter objects for Archived Feeds (HEAD -> filter_and_lists, origin/filter_and_lists) [James Mills]
And blacklisting
^lyse\.isobeef\.org$ (_because I couldn't figure out how to go fix broken/bad Followings of Users on my pod easily_) there should only be two Twter objects for you now, @lyse and @lyse-backup (as expected).Hopefully we don't run into any other weird edge cases π
> That's a good one to post on Yarn
So I use the term post and Yarn (to refer to Yarn.social)
> That's a good one to post on Yarn
So I use the term post and Yarn (to refer to Yarn.social)
- You are following someone that replies to a feed that you don't follow and whose Root Twt is missing from your Pod, so your Pod asks its peers if it has that Twt.
- You are following someone clearly having a discussion with one ore more folks you don't follow and so you only see one side. TBD (_this is not implemented yet_)
- You are following someone that replies to a feed that you don't follow and whose Root Twt is missing from your Pod, so your Pod asks its peers if it has that Twt.
- You are following someone clearly having a discussion with one ore more folks you don't follow and so you only see one side. TBD (_this is not implemented yet_)
I fixed one case already but this is different π
Looking into it... π
I fixed one case already but this is different π
Looking into it... π
- In Timeline view, a Reply will show the (#hash) you're replying to.
- In Conversation view, a Reply _will not show the (#hash) you're replying to. It's implied from the Conversation view.
- In Conversation view, a Fork will show the (#hash) of the Twt you're replying to and forking.
I guess there's some subtle differences that we need to take care of in the UI/UX to make things a bit more obvious and clear before we go completely hide them from the interface? π€_
- In Timeline view, a Reply will show the (#hash) you're replying to.
- In Conversation view, a Reply _will not show the (#hash) you're replying to. It's implied from the Conversation view.
- In Conversation view, a Fork will show the (#hash) of the Twt you're replying to and forking.
I guess there's some subtle differences that we need to take care of in the UI/UX to make things a bit more obvious and clear before we go completely hide them from the interface? π€_