statusnet (statusnet) group
-
I'm leaving the !statusnet and !snbug and !sn groups now because I think it's time to get rid of that name. So you won't reach out to me through those groups (even though one has "& GNU Social" in its name.
I'm still of course in !gnusocial if anyone wants to ask federation/development related stuff. But StatusNet issues should be resolved by upgrading ;)
-
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.
-
http://www.skilledtests.com/statusnet-1.1.1.tar.gz (sha512sum = fc7472c0692f000c708d212103360ec47195cd54b7c21b6ce7a47a2799e20d3fc4563fe18008c4a3431060917367776bd8f7b5a21e3696517499e41ef63dc7b0, downloaded on: 2013-07-16) cc #forthosewhoneedit !sn !gs !statusnet !gnusocial
-
about translate-wiki: I am trying to contact some people, because !statusnet translation management was once hosted there: https://translatewiki.net/wiki/Translating:StatusNet
-
@simsa0atquitter @hannes2peer @mmn there was first !GNUsocial, then Evan continued on it as !statusnet, then statusnet "merged back" into !gs
-
come to the irc channel to see what people ask or where they have problems with their !gs (to even install). I am sure @lohang can tell you also some stories about his old !statusnet ;-)
-
updated the "use cases for new !SN / !GS instances" cc !gnusocial !statusnet http://skilledtests.com/wiki/Statusnet_problems#use_cases_for_new_SN.2FGS_instances_.28aka:_when_one_of_the_fixes_below_work_for_you.29
-
well, you actually did run your own instances. but !sn has failed you, bad !statusnet
-
cc: from !sn !statusnet -> !gs !gnusocial
-
use the names !gnusocial or !statusnet in the playstore, perhaps you find more then. what are you searching for exactly?
-
If you've set up a new !gs instance, please do the "use cases for new SN/GS instances" (1). cc !sn !statusnet !gnusocial (1) http://www.skilledtests.com/wiki/Statusnet_problems#use_cases_for_new_SN.2FGS_instances_.28aka:_when_one_of_the_fixes_below_work_for_you.29
-
see http://skilledtests.com/wiki/XMPP_MUCs_for_GNU_social !xmpp !gs !gnusocial !sn !statusnet
-
I have here (1) this info: "last version with direct support for !StatusNet : Adium 1.5.6" (1) http://www.skilledtests.com/wiki/Statusnet_clients cc !sn !gs !gnusocial
-
@var see "how to upgrade from !statusnet to !GNUsocial ?" http://skilledtests.com/wiki/Statusnet_problems#how_to_upgrade_from_statusnet_to_GNU_social.3F cc !sn !gs
-
!status - running latest !gs code, nightly. Report bugs you observe, please (also to other instance admins: have a look in your logs for possible errors, thx) cc !sn !statusnet !gnusocial
-
I explained once, for me: why !statusnet? in short: emotions for the community, my bot http://skilledtests.com/wiki/Blog:Observations/why_statusnet cc !sn !gs !gnusocial
-
"My interpretation was that @mmn didn’t see !GNUSocial as the solution for the long run, but since it 1. had many users, and 2. it works well, it is valuable to keep maintaining it." http://sjoberg.fi/blog/join-the-federation.html !gs !sn !statusnet cc @sazius !consensus
-
RT @reality So is !StatusNet still being maintained as a separate entity to !GNUsocial at all? What is the situation here? !sn !gs
-
cc !gs (opportunity for #XSS attack also in !sn !statusnet )
-
good decision, more should start their own instances! RT @mattl Deleted my Quitter.se account, and I'm now exclusively at mattl.io for !GNUsocial :) cc !gs !sn !statusnet