Another fediverse newbie mucking about. Since joining I’ve been digging in and learning as I go, trying to determine what best suits how I’d like to interface everything. I am not, however, super well versed in all the ins and outs of this system yet. I’m not the most tech savvy person to be honest.
I’ve enjoyed this kbin instance so far. No complaints considering how new it is and how strained it got under the new user load. Grateful for the work that’s been put in to keep things whirring. If everything keeps going the way it has I’ll be sticking around. Though I have considered signing up to a different platform as well to use for more personal blogging, or interaction with closer friends and associates. I think I’m leaning toward Hubzilla for this.
The sorting tools used to filter your incoming feed as well as group contact sorting to control who sees what from what I’d be posting seems like it’d get me a long way toward how I envision wanting to use a macroblogger. There’s a whole host of features I’d probably never use besides. The account mirror and syncing feature seems pretty clutch.
If this ability to compartmentalize everything works the way I think I’m understanding it, there’s less a reason to even create multiple profiles across different platforms even if the intended usage between a link aggregate/subforum platform like kbin and a macroblogging platform are different. I guess you’d need a profile to moderate a magazine/community on a certain instance, but I’m not seeing much beyond that.
I know it doesn’t operate entirely (primarily even?) on the ActivityPub protocol, but it sounds like it’s integrated with with all the platforms operating on ActivityPub./?
Has anybody here tried it out? Are there inherent downsides? Anything I’m not considering that I ought to be? Any type of critical failure or a specific reason Hubzilla hasn’t taken off despite offering what looks to be a pretty elaborate feature set?
I haven’t tried any of the macroblogging platforms, but I plan to. For what I’ve read Hubzilla has a feature call Nomadic Identity that, while it makes server migration easier, creates problems with federation, but nothing too severe as to render it unusable.
It just that, because it’s a Zot feature, when you go from a clone to another, your contacts from platforms other than Hubzilla (or anything based on Zot are lost), but If you don’t care much about that, it’s a great feature because it means that you can keep using the platform even if your home server is offline
This is good to know. As long as the use of the second server profile was temporary due to something like server downtime my understanding is that any activity taking place on the second profile would sync to the primary profile once it comes back online. So it may mean delayed receipt of any of this activity to anyone not connected through Hubzilla, but it’d get there eventually upon syncing? Is this correct?
If the primary profile were to go down permanently though it sounds like it’d be a good idea to have a list of existing contacts backed up somewhere else to be able to duplicate on the secondary server profile if necessary.