Notices tagged with statusnet, page 2
-
@gargron Yeah, that makes sense. That may be why #StatusNet & #GNU_Social have a built-in #PuSH server.
-
@kat That's one thing I don't remember, but #Identi.ca was changing pretty rapidly up until sometime around the #StatusNet v.1.0 release. @gargron
-
Sure! Although I'm still running !StatusNet v1.1.1 -- gotta get that #RoundTuit
-
Sure! Although I'm still running !StatusNet v1.1.1 -- gotta get that #RoundTuit
-
It looks like you have found a bug in !gnusocial . It might be a legacy from #statusnet code. Oh, have to turn myself in. !tzaf to the friendly people of the !fediverse
-
@thelovebug Yep! We carry the full #StatusNet commit history, so just use the timemachine correctly and you can step it up from there. But as I said, the upgrade _should_ work from 1.1.0 too.
Just make sure you backup files as well as the database before you start rampaging! :)
-
@bes It was actually not like that in #StatusNet. I'm eager to hear if usernames and groups should have different namespaces. I don't think so, but I'd like to hear an argument otherwise .)
-
@bastianilso Ah, subscribers wouldn't be preserved anyway in the backup method we have right now... But we have full #FOAF support! So that's a good place to start if you want to do any "triangulation" :)
Check out the Linked Open Data cloud for example: http://lod-cloud.net/ (the big section of #StatusNet accounts, that's us).
-
@mikegerwitz Yeah, the #GoogleAnalytics thing probably doesn't work either. It's mostly just there because it's been there since #StatusNet. I wouldn't mind a merge request that removes it ;)
-
@imojito good to see #TurnKey have finally updated their !Statusnet to !GNUsocial. It looked like abandoned before.
-
Hmm. Even though I selected different !Listening groups from the drop-down list, the links on that message all point to the one on http://sn.theru.org/index.php/group/179/id I'm gonna have to upgrade my !StatusNet to !GNUsocial so I can properly participate in bug hunting...
-
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.
-
@fsf Can you please try to migrate your #statusnet instance to !gnusocial to stay up-to-date?
-
@mmn This appointment shows the wrong dates on my instance (31 Dec 1969) but is correct in the original. Is this a known problem between !gnusocial and !statusnet instances? http://social.gtalug.org/notice/140
-
Back in the #StatusNet days there was a bug that made every single reply to something directed at a group become a mention of that group. I like it better this way (though perhaps the feed should be more conversation oriented).
-
@if you should be able to create an instance w/ !StatusNet code. Many instances are still using it.But lets better ask a !gnusocial !SN guru
-
For #StatusNet yes, for !gnusocial a little but going to be fixed entirely.
-
@aroque I think @mike holds a grudge to previous #StatusNet dev team. Apparently they had strifes. I think they're doing good work with #RedMatrix for a different use-case than for !gnusocial. There are different kinds of secure, private etc. and there is some overlap but our implementations are not necessarily trying to solve the same problem. I have several times co…
-
http://www.skilledtests.com/statusnet-1.1.1.tar.gz (sha512sum = fc7472c0692f000c708d212103360ec47195cd54b7c21b6ce7a47a2799e20d3fc4563fe18008c4a3431060917367776bd8f7b5a21e3696517499e41ef63dc7b0, downloaded on: 2013-07-16) cc #forthosewhoneedit !sn !gs !statusnet !gnusocial