Update CHANGELOG.txt for v0.6.19
This commit is contained in:
parent
ebf8ad5947
commit
c746a85c8b
@ -358,4 +358,14 @@ v0.6.18
|
|||||||
- BUGFIX: fix scraper crashing on "composer" entry in threads
|
- BUGFIX: fix scraper crashing on "composer" entry in threads
|
||||||
- BUGFIX: fix "User followed you" notifications sometimes parsing as "New recommended post"
|
- BUGFIX: fix "User followed you" notifications sometimes parsing as "New recommended post"
|
||||||
- BUGFIX: emojis with skin tones now work in DMs
|
- BUGFIX: emojis with skin tones now work in DMs
|
||||||
- Notifications page is now paginated in web UI
|
- UI improvements:
|
||||||
|
- Notifications page is now paginated in web UI
|
||||||
|
|
||||||
|
v0.6.19
|
||||||
|
-------
|
||||||
|
|
||||||
|
- BUGFIX: fix the scraper `GetUser` function which was broken by an upstream change
|
||||||
|
- UI improvements:
|
||||||
|
- Profile and banner images in user feed header can now be clicked to open full-size versions
|
||||||
|
- Reply previews in DMs now include the username who's being replied to
|
||||||
|
- Notifications can now be marked as "read" via command line and web UI
|
||||||
|
@ -109,7 +109,7 @@ TODO: dms-search (#webserver, #dms)
|
|||||||
TODO: search-terms-highlighted (#webserver)
|
TODO: search-terms-highlighted (#webserver)
|
||||||
- on Search page, highlight matches for the search keywords
|
- on Search page, highlight matches for the search keywords
|
||||||
|
|
||||||
TODO: profile-image-template (#webserver)
|
TODO: profile-image-template (#webserver, #code-quality)
|
||||||
- There are a lot of places that use a circle profile image aside from author-infos
|
- There are a lot of places that use a circle profile image aside from author-infos
|
||||||
|
|
||||||
TODO: send-message-last-read-event (#webserver)
|
TODO: send-message-last-read-event (#webserver)
|
||||||
@ -126,3 +126,10 @@ TODO: conversation-thread-missing-tweets
|
|||||||
- In a conversation thread (replies under a tweet), if a user is blocked, the tweet response can be empty
|
- In a conversation thread (replies under a tweet), if a user is blocked, the tweet response can be empty
|
||||||
- These are just completely invisible on Twitter (render as nothing)
|
- These are just completely invisible on Twitter (render as nothing)
|
||||||
- e.g.: https://x.com/sirbughunter/status/1479540319410696192
|
- e.g.: https://x.com/sirbughunter/status/1479540319410696192
|
||||||
|
|
||||||
|
TODO: scrape-user-feed-removes-pinned-tweet (#scraper, #scraper-bug)
|
||||||
|
- Scraping a user feed unsets the user's pinned tweet
|
||||||
|
|
||||||
|
TOOD: notifications-duplicate-bug (#scraper, #scraper-bug)
|
||||||
|
- Older notifications often appear to get duplicated, sometimes quite a few times
|
||||||
|
- Probably related to the fact that notifications can replace old ones but we just treat them as a new notification instance
|
||||||
|
Loading…
x
Reference in New Issue
Block a user