Conversation
Notices
-
From your #experience: Why do people leave !GNUsocial again? cc !gs http://skilledtests.com/wiki/Why_do_people_leave_GNU_social_again
-
Wie ist eure Erfahrung hierzu: warum verlassen die Benutzer wieder !GNUsocial ? http://skilledtests.com/wiki/Why_do_people_leave_GNU_social_again
-
D'après votre expérience: pourquoi les gens quittent !gnusocial à nouveau? http://skilledtests.com/wiki/Why_do_people_leave_GNU_social_again
-
@erkan Community. People stay on the networks that the people they want to follow are on. Presently, those networks are the proprietary ones
-
thx, I have only added short terms (see (1)), but with the link to your comment. (1) http://skilledtests.com/wiki/index.php?title=Why_do_people_leave_GNU_social_again&diff=46155&oldid=46153
-
Due to federation: basic functionalities people are accustomed to from Twitter don't work or are difficult to use (remote block, remote reply, remote fav & repeat).
Due to architecture the user has to learn a lot before he can do basic stuff. This is true even if he stays in his "home"-instance and mimicks the silo communication of Twitter.
For a new user the advantages of federation are negligible, its disadvantages are tiresome.
GNU Social (and federation in general) is for people who share some basic concvictions (copyright, owning one's data, freedom from commercial pressure and ads, etc.) None of that is of major interest for most new users.
So, to use (or learn to use) GNU Social & federation just for idealogical reasons is simply not worth the effort. OTOH, GNU Social & federation don't provide additional functionalities that could differentiate them positively from Twitter.
... just some points ...
-
@simsa0 @expatpaul @mike @ryan @b thank you very much, I hope others will also chip in...
-
@expatpaul @mike yes, the community/cohesion is a strong influence :-( otoh: in the example of the recent Spanish wave 1 user took along many others to here
-
"This isn't a crack at you or the others because you're all doing a great job. This is hopefully #helpful criticism of the software." <- no worries
-
!gnusocial documentation for users/admins: right, so let's start collecting the different resources: (1). You made a tutorial also recently, send me the link please. (1) http://skilledtests.com/wiki/GNU_social_tutorials cc !gs
-
"GNU Social user directory": I guess that is easier to implement for @pztrn with his gstools, right?
-
right :-( "Having said that, the average person doesn't seem to care about #privacy enough to use alternative means"
-
"GNU Social & federation don't provide additional functionalities that could differentiate them positively from Twitter.": what came to mind that the hierarchical threading doesn't work anymore :-(
-
instances broken: right, this happened in the past to others: @jpope, @encycl, @morph, @atarifrisch and others
-
I guess we'd also have terrible experiences with spam (though we have some tools, like block, sandbox, silence). I think for !gs some sp.m waves will be terrible :-( "If people were able to setup their own instance on say a hosting provider instantaneously we would see a #massive influx of users."
-
"stable version": perhaps, personally I think @mmn does a good job so far with his nightly branch. Even if it gets messed up some time, he (and others) are fast to fix it
-
thx, added
-
"I'm kind of nutty about wanting #control over my #own services." <- I understand that very much :-)
-
The hierarchical threading had been one interesting feature, but was itself prone to quickly become as confusing as the stream mode: The indenting of each and every reply made for long strings one had to scrutinize carefully in order to find the dent the reply replied to. Helpful in short conversations but confusing in larger ones. (A combination of both might actually help ease the problem, putting notes into a stream line as long as there is no further reply indenting the conv to the right).
But a main conundrum for GNU Social is: In implementing more and more the features people are accustomed to on Twitter, the less it becomes reasonable to leave Twitter for GNU Social. This could only be avoided if GNU Social would come up w/ a good solution for displaying conversations -- something that hasn't been achieved by Twitter or Free Media.
-
The upgrade (1) is nothing difficult. If you have managed to get your instance going until now, you'll see this, afterwards. Of course, at the first try it is something new, that's clear. (1) http://skilledtests.com/wiki/Statusnet_problems#how_to_upgrade
-
Yes, we need to have something that differentiates us than "just" being #opensource. I guess the #community comes to mind, ...
-
tbh, at this point, I'd have any hierarchichal threading, than none. I had it running here in !gs but I had some side effects (1) :-( So, the only way to get it currently is to view conversations on my old !sn oracle. (1) https://fediverse.com/conversation/485663
-
what just came to mind was: what would happen, if twitter, facebook, ... would decide to go "our way"? e.g. make it more #decentral, some parts more opensource, ... but still have certain things to keep (under) control. They have unarguably larger communities. @question I wonder if some of us would switch to the evil side again?
-
Yeah, I intend to keep the master branch bug free, but occasionally there are stuff I haven't noticed even there. Latest example is the problem which was fixed in the https://gitorious.org/social/mainline/commit/59bbc81c4b71dbfc37f9a2058012bd5c342c3faa - which I didn't figure out until some friendly debugging together with @luvo@quitter.es over at https://github.com/hannesmannerheim/qvitter/issues/102
-
@erkan And nightly tends to be stable if it hasn't been updated in a couple of days. (because that's about how long it usually takes to spot (unintentional) bugs without testcases :D
-
Haha, yes. Unintentional bugs. Sometimes I introduce intentional bugs. Like the @chimo filters.
-
I think the #licence problematic would be "solved" by "muscle playing". I remember when I set up my !friendica how Mike answered me if I'd select another licence than the standard one, a la: "I'd #unsubscribe from you and would tell all my followers to do the same". Thus, to avoid the !twitter users would go with the mainstream licence and the others would "just be islands"
-
I think the incentive of the big silos is to gather #data. By now, most users know that those big silos are bad for them. I think the new l#ie could be a la: "Here, we give you the software for free, under your own control (<ADD-some-fineprint-here-to-assure-big-silos-still-can-get-some-data>), and then some of the masses go on missionizing their friends, families for them...
-
I am sure some researchers tried to analyze that already, but let us know what YOU think :-)
-
I like that notion: it forces the people to #fight until the end. Many people don't do these days anymore
Erkan Yılmaz
Paul Pritchard
simsa0
MMN-o ✅⃠
All Chirp! content and data are available under the