-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New dashboard: extension progress #1802
Comments
This is out of date and might be inaccurate, etc. etc. disclaimer disclaimer Auto Tagger 7 Blog Tracker 3 Classic Notifications 1 CleanFeed 7 Don't Stretch Photosets 1 Drafts+ 7 Enhanced Queue 3 Find Blogs 1 Header Options 1 Highlighter 5 Iconified Notifications 5 J/K Across Pages 1 Limit People 3 Mass Deleter 3 Messaging Tweaks 3 or 7 Mirror Button 3 Mute! 7 Mutual Checker 3 NotificationBlock 7 Old Sidebar 3 Old Stats 3 One-Click Reply 3 Post Archiver 7 Post Limit Checker 1 PostBlock 3 Profiler 3 Quick Tags 5 Read Posts 3 Reblog Display Options 7 Retags 7 Scroll To Bottom 1 Search Likes 5 Separator 1 Servant 11 Shorten Posts 3 Show Originals 3 Show Picture Size 3 Tab titles 1 Tag Replacer 1 Tag Tracking+ 5 Theme Editor / Themes / Themes+ (preview) 5 Tweaks 7 Unreverse 3 Vanilla Audio 1 View My Tags 3 XStats 5 |
Why is bookmarker "(Arguably) Impossible to update"? |
@inklesspen the new dashboard's pagination doesn't work via post IDs / doesn't have unique URLs per page, so programmatically skipping to a point in time on the dashboard is impossible through that method |
That's what I thought, but surely it can work through whatever means the Go-to-Dash extension has been fixed to work? |
the workaround implemented in Go-To-Dash isn't permanent and shouldn't be considered a "fix". Bookmarker could also implement the workaround, but the workaround is going to be patched out, probably soon |
How far away does it look like the ETA is for quick tags? IS it one of the higher or lower priority things? |
@Tails-155 there is no ETA or official priority for any extensions. |
Cool, cool. I definitely don't want to rush things, since I'd rather it work, and frankly I'm impressed it is already even partly compatible with a pure overhaul, I just know I use that extension a lot. XD |
Go-to-Dash isn't working at all anymore, even with the sidebar option. |
@chickenwithakeyboard this is due to a tumblr update that we're aware of and have a pending fix for; see #1920 |
It looks like Bookmarker could be updated to work with the new dash! After reloading my dashboard tonight it came up with a notification to skip back to where I was, and a URL like https://www.tumblr.com/dashboard?max_post_id=(POSTIDHERE). EDIT: Also, it doesn't seem like you can scroll very far past the first post it loads. After ~15 posts it refuses to load any farther, unlike the old system where you could infinitely scroll past and load new (old) posts. Take these three examples, While obviously this worked out mostly because old-me would hastily bookmark posts i liked, even ones back to back, it still shows that A) some old bookmarks could still be usable and B) that bookmarking works, like, at all- even for old tumblr era posts before the big dashboard and post ID overhaul (i'm looking at you, sudden jump from 19XXXXXXXXXX to 61XXXXXXXXXXXXXXXX) |
@SupremeDevice The general rule is that you have to add 1 to the post id, and then put that in the URL. That's what works with the Go-to-Dash extension in PR #1936. When the max_post_id thing first came out, trying to go to a really old post id would get a page full of "since you've been gone" recommended posts. but now it seems to work. I can go to a four-year-old post using this method! |
@inklesspen Ah, yep, that seems to work. For some reason my first guess was to lower the number and not increase it, but it seems on several old bookmarks that does work, and I assume the others that don't can be chalked up to general tumblr nonsense, or unfollowed/deleted blogs or posts. Really glad that bookmarks can be brought back again (but also that I now have a backup of them LOL) |
Mirror Button Still Not Showing and therefore not Working |
Are all of these extensions being written off as impossible to update? I'm particularly concerned about classic notifs and blog tracker. I've been able to access blog tracker (among other unchecked extensions) on certain "legacy-powered pages" as y'all put but the last page I was able to use like that - Following - doesn't seem to be a legacy-powered page anymore. There was another page on tumblr that I noticed worked the same way but I can't remember which one it was. Is there a list of pages on tumblr that were/are currently still legacy powered? |
Extensions listed but not checked here aren't impossible to update. Progress is simply slow, since this version of XKit is ill-equipped to handle the React site. There's no definitive list of remaining legacy-powered pages, but the ones I can think of off the top of my head include:
|
I feel the strange need to note that, for now, reblogs that are done from a blog page open on a legacy dash (though that's not precisely helpful in most cases because actually using the legacy dash behind the reblog requires deleting the reblog modal and blue overlay nodes as well as changing the overflow for the page to a scrollable one (and can only be used until you need to refresh, since soft refresh no longer exists)). TL;DR: There's another legacy-powered page but actually accessing/using it is hacky/weird. But it could be useful to some people. |
Tracking issue for which extensions need to be updated for the React site, which launched April 2020 and became permanent July 2020.
NOTE: Maintainer activity on this project has fallen to the point that significant updates cannot be expected. This issue no longer serves as a to-do list, but rather as a reference for users.
This does not mean that XKit is dead; the new iteration of the framework can be found at AprilSylph/XKit-Rewritten.
If you do not see an extension listed here, it may be because:
Extensions that are checked below have been updated and should work.
Extensions not checked here cannot be expected to work whatsoever, except on legacy-powered pages (if applicable).
No updates needed (yet):
Already working on new dashboard without updates:
The text was updated successfully, but these errors were encountered: