I just set up an account at fedia.io, which is an mbin instance. When I ran the script posted over here to copy my subscriptions I had 111 subscriptions succeed and 49 fail. I've been checking the ones that failed and they've all been ones that haven't had anyone post in them for 5 months or more, so I'm guessing those are "dead" anyway. Seems not too bad, I'll see how it goes I guess.
I posted this same response from both of my accounts, I'm going to watch to see how well it federates back and forth.
It doesn't help that whenever this comes up there's a contingent of users who jump to Ernest's "defense" by calling the folks raising these issues "concern trolls" and accusing them of shilling for mbin.
No, this is simply a matter of what is actually working well. The point of federation is that one shouldn't need to have "loyalty" to any particular instance or any particular platform. Use whichever one's working.
I haven't tried all of them, but the ones I did check were ones that had not had posts on them at their source instance for quite a while. A few random examples:
I had 43 failures and 111 successes, so visual inspection wouldn't really help. I kept copies of the error log and the script output in a text file to figure it out later.
I assume that this means these communities haven't had activity since fedia.io opened, and so fedia.io doesn't know they exist? I've always wondered how the first person to subscribe to a community on an instance is able to do that.
And yeah, I'm using "community" to refer to "magazine".
I just gave this a try and I think there's a potentially worrisome problem, it silently failed on a lot of community subscriptions. The ones that returned HTTP 500 errors were listed in the "fail" list that the importer script generated, but a whole bunch of others returned 404 errors and weren't listed in either the success or fail lists.
So I advise those running this to pay attention to the error log to avoid losing track of those communities rather than trusting the "fail" list.
I actually don't mind that one particular scene much, and that comes from someone who really loathed The Last Jedi overall. Using the Force to propel oneself in zero gravity isn't bad, and the vacuum of space is not nearly as deadly in reality as science fiction often portrays it.
However, the one thing that did stick out as a glaring problem to me was the fact that the Raddus was fleeing the First Order's fleet at that moment, so its engines must have been firing at full thrust. So how is Leia and all that debris floating around motionless relative to the ship? Indeed, even if the ship wasn't actively thrusting, all that stuff was moving away from the Raddus pretty vigorously after the bridge blew open. Why did it stop? Is space actually an ocean?
The first line of the Disney trilogy was "This will begin to make things right." On its own, no biggie. But when you consider the utter dumpster fire of a trilogy that followed, which deliberately went out of its way to despoil the heroes of the previous Star Wars movies and destroy everything that they had worked to accomplish, incredibly frustrating. It's meta-frustrating. You can think of that line right before any of the other individually-frustrating scenes you may think of and it makes it even worse.
Intriguingly, the two structures are at the same distance from Earth, near the constellations of Boötes the Herdsman, raising the possibility that they are part of a connected cosmological system.
Not only that, but they look suspiciously concentric when plotted out on the sky. I know that's jumping pretty far out there into speculation land, but it'd really blow our theories a new one if there are patterns in the cosmos this large. Neat stuff.
Thanks for putting in all this work, especially over a period that's traditionally vacation time. Make sure you're striking a good work/life balance, if you can get the site basically functional (as it appears to be now) don't sweat the small stuff. :)