Conversation

Notices

1. MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Tuesday, 08-Sep-2015 15:30:51 UTC MMN-o ✅⃠

   • espionage724
   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.
   • Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca (bobjonkmanformer@sn.jonkman.ca)'s status on Wednesday, 02-Sep-2015 16:25:24 UTC Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca

     • lnxw48 (Linux Walt)
     • espionage724
     • gnusocial
     • Self Hosting
     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
   • Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca (bobjonkmanformer@sn.jonkman.ca)'s status on Wednesday, 02-Sep-2015 18:30:38 UTC Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca

     • espionage724
     • Self Hosting
     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
   • Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca (bobjonkmanformer@sn.jonkman.ca)'s status on Wednesday, 02-Sep-2015 18:56:15 UTC Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca

     • espionage724
     • the federated universe
     • statusnet
     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.
   • Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca (bobjonkmanformer@sn.jonkman.ca)'s status on Tuesday, 08-Sep-2015 15:21:39 UTC Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca

     • espionage724
     @espionage724 I'll have a look at that script when I can babysit the server. I want to see the magic smoke come out.
   • Temporary Marjolein (mk@oracle.skilledtests.com)'s status on Tuesday, 08-Sep-2015 16:14:24 UTC Temporary Marjolein

     in reply to

     • espionage724
     @mmn this is odd: in identicurse this dent of yours appears as addressed to no-one; in the web UI it's addressed to @espionage724
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Tuesday, 08-Sep-2015 17:28:33 UTC MMN-o ✅⃠

     in reply to

     • Temporary Marjolein
     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.
   • Temporary Marjolein (mk@oracle.skilledtests.com)'s status on Tuesday, 08-Sep-2015 17:50:12 UTC Temporary Marjolein

     in reply to
     @mmn I don't know exactly what identicurse does, and don't know enough Python to even try to tackle it. :( But fact is, in some contexts the missing of @-name in the dent itself causes "context-less" messages - much better to auto-generate the @-name for a reply (as StatusNet used to do before that got broken in 0.9.6 or so).
   • Temporary Marjolein (mk@oracle.skilledtests.com)'s status on Tuesday, 08-Sep-2015 17:52:01 UTC Temporary Marjolein

     in reply to
     @mmn but I don't know if it's even possible to request a dent (or dents) from the API and NOT get the in-reply-to bit returned in the returned data - is it?
   • Temporary Marjolein (mk@oracle.skilledtests.com)'s status on Tuesday, 08-Sep-2015 17:54:15 UTC Temporary Marjolein

     in reply to
     @mmn even more to the point, this dent of yours I'm replying to now DOES show it's addressed to me in identicurse, even though it doesn't have '@mk' in the text. So how can the addressee be known in some cases and not in others?