Conversation
Notices
-
@mk I see a total of five !Coffee groups: http://sn.jonkman.ca/search/group?q=coffee By "correct group" I mean the one you *want* to send messages to. The only way to ensure that is to unsubscribe from any other groups with the same name.
-
Looks like your post addressed the !Coffee group at http://sn.jonkman.ca/group/coffee To ensure your messages go to the correct group, you need to unsubscribe from all the other !Coffee groups
-
@bobjonkman "all the other !coffee groups"?? how many are there?!
-
@bobjonkman oh, and define "correct group" please. ;-) This is confusing! confuzzling, even.
-
@rtsn What page is displayed when you see that error message? The !Coffee group has a successful subscription from @vinzv@gnusocial.de so our servers have communicated successfully in the past. Sadly, I have logging turned off because it used to fill log files at the rate of about 20 kBytes/s...
-
And I see that your server sees *six* different \!Coffee groups: http://oracle.skilledtests.com/search/group?q=coffee of which we have only four in common: on vinilox, oracle, status.fsf.org, and sn.jonkman.ca; sn.jonkman.ca sees one on loadaverage, and oracle sees one on identi.ca and quitter.se. So that's *seven* !Coffee groups now...
-
@bobjonkman what I really want is only *one* group for !coffee (or anyting, really). I think it needs to be easier to "discover" already-existing groups, so people would be less likely to create 'duplicates'. OR there might be a mechanism by which groups exchange their content automatically.
-
@rtsn Go to http://sn.jonkman.ca/group/coffee, click on "Subscribe" and then enter https://gnusocial.de/rtsn -- that gets me the login screen on your server. Don't know why the @ address doesn't work, tho...
-
@mk Yes, I really do think that the function of a group should be federated. If I start !NewGroup and there are already other !NewGroup instances defined on other servers then my !NewGroup should participate in sending messages to subscribers in all instances of !NewGroup. That provides some resilience too - if one !NewGroup disappears then the other !NewGroup instances can divide the subscribers and workload amongst themselves. I leave the development of a protocol to do that as an exercise for @mmn :)
-
@bobjonkman exactly!