Conversation
Notices
-
@hiker does the s.russwurm instance give you that msg? You can also join from your instance in classic mode (profile→+remote→add group url)
-
@blog2read I'm no expert, but probably more info is needed: do specific groups fail constantly, or does joining 1 group need several tries?
-
@mcscx I'm also running into problems when joining certain groups though not with that message (but the UI may hide the message, of course). Could be a StatusNet«-»GNU Social incompatibility or even incompatibilities between different GS versions/implementations. Maybe combined with other factors. Fact is, I cannot join the #tea group.
-
@blog2readIt is impossible to debug this without knowing which instances, groups and accounts are involved. cc: @hiker
-
@mk I guess there was already a #tea group on old-identica and your instance knows that group and tries to connect to identi.ca →
-
@mk → even though you tell your instance to join quitter\.se/group/tea. This #groupnameconflict problem seems to need debugging
-
@mk I've jst been able to remote-join the !tea group from my Vinilox acct, so the culprit doesn't seem to be the instance hosting the group
-
@mcscx that is certainly needed, even if (?) it's not the problem in my case. these things need to be morer robust, if things don't work as a result of something (still) sitting on an 'abandoned' server... maybe the code could try some fallbacks to work around problems like that. http«-»https can occasionally also cause problems with joining/subscribing
-
@mk you can test this by trying to join quitter·se groups that were likely existent on identica (e.g. !wordpress), vs newer groups
-
@mcscx Yo when's StatusNet or whatever it's called now gonna do for groups what it already does for u…
-
@mcscx hmm, there's an idea...
-
@hiker I noticed the #Need>1TriesToJoinAGroup, esp. w/instances w/ overloaded network→remote-sub timings should be more tolerant !gnusocial
-
@hiker@social.bitcast.info @mcscx Hmm. s.russwurm.org is up, showing no strange behaviour. I'm hesitant to twiddle the !DB manually; perhaps it is my previous twiddles that are the root cause of today's problems :(
-
@bobjonkman likely a timing/slowness issue (maybe not on your side). I could join !tzaf from my vinilox acct, just took some seconds more.