Conversation

Notices

1. Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca (bobjonkmanformer@sn.jonkman.ca)'s status on Wednesday, 28-Dec-2016 07:45:41 UTC Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca

   • Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca
   • MMN-o ✅⃠
   • mcscx2
   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
   • Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca (bobjonkmanformer@sn.jonkman.ca)'s status on Monday, 26-Dec-2016 05:03:13 UTC Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca

     • Coffee
     • David Benfell
     @benfell@cybernude.org There have been some other subscriptions to the !coffee group on sn.jonkman.ca so it's working, but I can see there are many other !coffee groups on other instances: 1) https://status.vinilox.eu/group/1812/id 2) http://oracle.skilledtests.com/group/475/id 3) https://status.fsf.org/group/1/id 4) https://loadaverage.org/group/985/id Make sure you're not joined to any of them. Also, try subscribing by putting your OStatus address benfell@cybernude.org into the "Profile Account" field on http://sn.jonkman.ca/group/coffee or if that doesn't work put in your URL https://cybernude.org/benfell If you still have problems after that let me know and I'll look for bits to twiddle inside the database.
   • Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca (bobjonkmanformer@sn.jonkman.ca)'s status on Monday, 26-Dec-2016 05:10:18 UTC Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca

     in reply to

     • Coffee
     Perhaps I should have checked for those other !coffee groups before setting up yet another on sn.jonkman.ca The group on http://oracle.skilledtests.com/group/coffee already has 40 members; perhaps that's the group we should join...
   • @mcscx@quitter.se (mcscx@quitter.se)'s status on Monday, 26-Dec-2016 14:07:43 UTC @mcscx@quitter.se

     in reply to
     @bobjonkman  although http://qttr.at/2kz may be on a trip to outer space, captainless. Also check the coffee group admin's last posts.
   • Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca (bobjonkmanformer@sn.jonkman.ca)'s status on Wednesday, 28-Dec-2016 06:35:08 UTC Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca

     • mcscx2
     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...
   • Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca (bobjonkmanformer@sn.jonkman.ca)'s status on Wednesday, 28-Dec-2016 06:37:31 UTC Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca

     in reply to
     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...
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Wednesday, 28-Dec-2016 10:56:47 UTC MMN-o ✅⃠

     in reply to
     @bobjonkman Mayhapz!