Conversation:
Notices
-
I had a GS instance running, had a user account, remote joined !selfhost and then nuked that GS instance (without leaving the group). I re-created the GS instance and recreated my account (same name), but can't rejoin the group (Remote group join failed!). Looking at !selfhost it seems I'm still part of the group though. Is there anything I could do on my end to leave the group an…
-
@espionage724 1. I *think* the easiest would be for @bobjonkman to remove you from the group 2. Have you tried without quotes around "0" ?
-
@espionage724 It is possible that the group admin (or the server admin for the instance where the group is hosted) may have to intervene. However, that person is currently busy as a candidate in Canada's upcoming election. Let's see whether any other !gnusocial admins have another idea.
-
@espionage724 Oh, I misunderstood. Don't think it's possible; that DB field has a max length of 191 chars ("255" in the desc is wrong)
-
@espionage724 You could go in, tweak your db and change that field type if you're running your own instance, of course :) At your own risk
-
Campaigning, but not too busy to fix a !gnusocial problem. But I see @espionage724 right at the top of the !selfhost subscription list, so I'm not sure anything is broken here... http://sn.jonkman.ca/group/selfhost/members
-
There are four instances of @espionage724 https://www.realmofespionage.com/espionage724 in the 'profile' table; I've deleted the entry for the one profile in the 'group_member' table. Try subscribing to !selfhost again... #ReferentialIntegrity? #NeverHeardOfIt
-
Hmm, it still fails to remote join unfortunately.
Not sure why there would be 4 instances. From what I can recall, I only joined !selfhost once from my instance.
-
Joining that group fails now probably because I've messed up the DB. There was likely a pointer to that entry I deleted, and now !StatusNet doesn't know what do to. The !Fediverse is full of stories about failed !GS moves, or URL renames, or forcing HTTPS where there was only HTTP before. We need some tools to clean out stale profiles and restore DB referential integrity when guys like me mess things up.
-
@espionage724 I'll have a look at that script when I can babysit the server. I want to see the magic smoke come out.
-
I recommend setting the length limits in the administration interface. Also, if you create a new user with a different URI (right now it's probably yoursite/user/1 ) it will sufice as a workaround. A remote site won't accept a new user with the same URI as an old one it already recognizes.
-
I bet identicurse doesn't know about the metadata and thus only (since it's pretty lousy at federated users too?) lists in-text @ mentions.
espionage724
Chimo
lnxw48 (Linux Walt)
Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca
MMN-o ✅⃠
All Hacker Poesy content and data are available under the