Conversation:
Notices
-
Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca (bobjonkmanformer)'s status on Wednesday, 28-Dec-2016 01:35:08 EST Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca 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)'s status on Monday, 26-Dec-2016 00:03:13 EST Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca @benfell@cybernude.org There have been some other subscriptions to the !coffee group on http://status.hackerposse.com/url/9394 so it's working, but I can see there are many other !coffee groups on other instances: 1) http://status.hackerposse.com/url/9477 2) http://status.hackerposse.com/url/13528 3) http://status.hackerposse.com/url/13529 4) http://status.hackerposse.com/url/1353… -
Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca (bobjonkmanformer)'s status on Monday, 26-Dec-2016 00:10:18 EST Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca 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... -
morph (morph)'s status on Monday, 26-Dec-2016 00:17:27 EST morph @bobjonkman @vinilox @mmn @mcscx2old @vinzv @einebiene @benfell @hobbsc @sorcerer @mcscx The !coffee must flow.
-
Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca (bobjonkmanformer)'s status on Wednesday, 28-Dec-2016 01:37:31 EST Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca 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...
-