CRX id
oedncfcpfcmehalbpdnekgaaldefpaef
oedncfcpfcmehalbpdnekgaaldefpaef
Description from extension meta
Loads missing replies to boosted toots directly from the source server.
Image from store
Description from store
Mastodon often fails to show up-to-date context and information on posts from remote instances. This addon does that properly.
• See all the replies to any post on your home instance. Local and remote replies are now loaded in parallel so there is no extra delay.
• Interact with all the remote posts as normal. They will be fetched to your instance as needed.
• See the actual latest 20 posts in any user's profile.
• See up-to-date boost/favorite counts on posts.
It should work reliably on mainline Mastodon versions 4.0 and up, your mileage may vary for older instances or forks.
Make sure to open the addon settings and type in the instances it should be active on!
----
It can fetch statuses and contexts from Akkoma/Pleroma and most Misskey/FireFish/Sharkey/IceShrimp/etc instances, better compatibility is a work in progress.
However, it can only run on Mastodon as a home server, and has been tested to work on vanilla and Glitch editions on current development version (4.3.0).
----
Visit the website for more info!
Latest reviews
- (2023-04-29) Halim PARK: 릴레이 연결되어 있는 이용자로 썼더니, 서비스 요청 수 제한에 걸렸다는 메시지가 오네요.
Latest issues
- (2023-09-25, v:0.6.2) Joshua Jones: Mastodon 4.2.0, Substitoot breaking hashtag search
Since Mastodon 4.2.0 was installed on my instance I have been having an issue where if I 1. Perform a search 2. Click through to the hashtag feed for the searched keyword 3. Click through to any post from that hashtag feed I will then get an error, "Due to a bug in our code or a browser compatibility issue, this page could not be displayed correctly. Try refreshing the page. If that does not help, you may still be able to use Mastodon through a different browser or native app." Through troubleshooting, I have determined that if I disable the Substitoot extension this behavior stops. So it appears to me that something about this extension is not playing well with 4.2.0.