Oh no, I'll be sorry to see https://cybernude.org go away. Would you consider wiping it out and setting up a new instance at the same address? After the #bifurcation I found I couldn't restore my identi.ca dents to sn.jonkman.ca, but I found that participating in the !Fediverse was far more important than preserving old messages -- I haven't missed the old content at all.
@benfell@cybernude.org There is definitely something amiss between our instances. My DB shows you've joined only \!security http://sn.jonkman.ca/group/416/id , \!selfhost http://sn.jonkman.ca/group/164/id , and \!crypto http://sn.jonkman.ca/group/348/id , but when I look at https://cybernude.org/benfell/groups I see you're subscribed to \!security , \!selfhost , and \!gnupg http://sn.jonkman.ca/group/1014/id . If I add you to \!coffee manually then my instance will happily forward to you the notices posted to \!coffee from other users, but your instance won't know to send notices you post to !\coffee to my group. I think some DB surgery is required, and while I'm happy to twiddle the bits in my DB manually I'm not sure how we can coordinate our activities, and I'm not sure that my DB's integrity won't be compromised (ie. that all the appropriate pointers in one table still point to valid records in other tables). @mmn, any advice?
Used to be, the admin that created a group could add other accounts to be admin. But now that the account that created !gnusocial is deleted, I don't know how. I think @mmn has a script for that kind of thing.
Just had a lovely chat with @KenFa11on in the !HPR New Year's Party #Mumble chatroom. Yes, I will be contributing a show soon! But first, !tzaf for the night.
@alpacaherder This false dichotomy sums it up: "The trademark of a worthy employer is the ability to masterfully manage the tension between employees as costs and employees as assets." As an employee I want to be treated neither as a cost nor as an asset. Morale of employees won't important improve until employers figure that out.
I created a test account on one of the first instances, which might still have been called laconi.ca. I created my "real" @BobJonkman account in 2008 when it was already called identi.ca. But that doesn't qualify me to host the GNUsocial group, that honour (duty? burden?) should fall to @mmn@social.umeahackerspace.se
Of course, if it's true that people should only be subscribed to one groupname at a time then everyone needs to do that individually. That's not something I expect everyone to do, or even to remember. And it prevents people from receiving messages from different instances with the same groupname. Group federation would be the correct solution...
I think the key to avoiding group name conflicts is to be subscribed to only one group with a particular group name. I find that when I unsubscribed from Vinilox's Coffee group I had no problem sending to my own Coffee group. Of course, that may have had more to do with group locality than groupname uniqueness...