Show Navigation
Notices tagged with statusnet
-
I seem to recall there's a standard API that should be common to all the #StatusNet derivitave servers. I'm pretty sure that in its infancy Mastodon conformed to that API. But Mastodon's API expanded beyond that, and I suspect some of the common API was removed, probably around the time #OStatus was dropped from Mastodon too.
But that's sheer speculation on my part.
Time to upgrade my server, so I can upgrade PHP, so I can upgrade this GNUsocial instance...
-
And if it's not possible to run !GNUsocial or #StatusNet on #PHP7, whether it's possible to run #Apache with #PHP7 in one virtual server, and #PHP5 in another...
-
@dissolve Even #StatusNet could do it actually .) Just like how you can supply an http/https URL when subscribing.
-
@craigmaloney #StatusNet was not only released under the #GPL, but the #AGPL (Affero GPL). The AGPL was explicitly designed to also keep remote services free as in freedom. The GPL unfortunately doesn't defend rights when it comes to webservices etc. but (if I remember the legalese correctly) AGPL has the language of "conveying" instead of "distributing" etc.
-
@maloki Right, that thing could probably be fixed by doing a remote-fetch of parent (which I believe #Mastodon does for replies to unknown posts, right?).
I haven't checked whether the feed is fixed yet (@Gargron mentions the Suprrrfeedrrrrr "sanitation" with thr:in-reply-to)
We stitch together instances in !GNUsocial based on the conversation URI though, which is never stored or distributed from #Mastodon (which relies entirely on thr:in-reply-to)
What we have is however a bit of a mess and I don't remember which part is what we actually use and which part just comes along from #StatusNet (where none of this worked and conversations were even more broken).
-
@strypey For example !GNUsocial allows for remote deletion but there is no guarantee that anyone cares about the requests. Take older #StatusNet installations for example, they don't support the 'delete' verb.
-
@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 .)
-
@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 ;)
-
@fsf Can you please try to migrate your #statusnet instance to !gnusocial to stay up-to-date?
-
Back in the #StatusNet days there was a bug that made every single reply to something direc…
-
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 s…
-
http://www.skilledtests.com/statusnet-1.1.1.tar.gz (sha512sum = fc7472c0692f000c708d212103360ec47195cd5…
-
@thelovebug #StatusNet discards 4 byte UTF-8 characters (actually it's #MySQL which has inc…
-
A little background on this is that the #SubMirror plugin only ever worked for #StatusNet w…
-
@fsf I hope you will update soon to !gnusocial ? #StatusNet is really far out-dated and unmaintained.
-
@eljay Kommt dies auch von mir an? Der @erkan nutzt noch eine #StatusNet Version, welches der Vorgaenger von !gnusocial ist.
-
@erkan I think #data-portability is to much/hard for @mmn to archive? You @marcusmoeller also nee…
-
@nawi Einige Teile von !gnusocial und insbesondere aeltere #StatusNet Instanzen kommen dann durch…
Bob Jonkman
MMN-o ✅⃠
Roland Haeder
erkan
All stadeus content and data are available under the