shazbot
Addressing your issue, I have bumped the version number to 0.1.3 and made a change to the async method handling so that instances not available at the remote get added to the fail log correctly.
This doesn’t explicitly address the fact that some instances are unfederated, but it will make the log results clean.
As for the federation issue, what I’ve initially found is that a user on an instance has to visit the remote instance for the home instance to be aware of this remote instance, and a user (could be a different user) has to subscribe to that instance for the posts to start federating. What is unclear is how a user on an instance visits a remote instance from the home instance, as this is implementation-specific and could vary from instanc to instance.
Hmm, this is a good finding. Just on a cursory review, I had a look at the magazines list on fedia, and it does list magazines with zero threads, comments, posts, or subscribers on them (on other instances other than kbin.social). So maybe you’ve discovered a problem with kbin.social’s federation? I don’t know too much about this issue, so this is just my initial reaction before looking into it further.
I’ll try to reproduce this and look into tightening the error handling. A 404 error should imply that the magazine is not available at the remote. Are those magazines available at the target instance? Agree that those should at least be added to the log–perhaps should add a third category for “Unavailable.” Remember that it will also navigate you to the magazines list at the end for visual confirmation.
When you said community subscription, were you referring to something in particular, or just using this term generically to refer to magazines?
A bit late, but I saw your post and decided to make a tool for this. Hope this helps.
If using KES, check General > Add mail icon
to append an icon/label next to a username to directly message them. (If on the same intance as you)
I had just forgotten something simple (unload the threaded comments CSS):
Before:
removeDangling();
safeGM("removeStyle", "hide-defaults");
After:
removeDangling();
clearMores();
safeGM("removeStyle", "hide-defaults");
safeGM("removeStyle", "threaded-comments");
This is live on testing, but might take a sec to propagate due to GitHub’s caching feature.