[FM Discuss] cryptoparty book & Tech Tools for Activism

[Tomi Toivio]

There is also a huge issue with the manual, since there are two completely
opposite use cases for StatusNet.

Case 1: Privacy

You want to have private communication, so you set up a private StatusNet
for an organization or a group of people. Naturally you cannot use
syndication at all.

Case 2: Open Source

You want to set up an open source microblogging platform. Here syndication
is extremely important, since many of the people you want to communicate
with would be on other StatusNet installations.

Case 1 would be easier for this first version of the manual, since we
cannot even get all of the syndication features to work on this
installation.

2012/10/26 Tomi Toivio <tomi at flossmanuals.net>

> Hey,
>
> I was fooling around with the StatusNet configuration file and now the
> syndication works a lot better: http://fi.flossmanuals.net/statusnet/
>
> Syndication is exactly what is needed to beat Twitter. I think it can be
> syndicated even further. I don't think that I can make all of the
> syndication plugins work on this server. I think that syndication has to be
> documented in English, I am not exactly sure about some of the settings.
>
> The funny thing is that the local users are using it as a sandbox for
> documentation and then you have a constant stream of syndicated messages
> from some very active external users.
>
> I was looking at various StatusNet installations and some of them have
> totally drowned in spam. Spam bot prevention seems to be the most painful
> issue here.
>
> Regards
> Tomi
>
>
> 2012/10/11 Tomi Toivio <tomi at flossmanuals.net>
>
>> > January sounds like a good date to go for.
>> > I really wonder what the best strategy for creating the English
>> Status.net
>> > manuals is.
>>
>> At least the more technical chapters should be written with
>> developers? I couldn't get the spam bot prevention plugin to work,
>> which is a bit scary, since now I have to delete spam bots manually.
>> So this is one example of an important plugin that really needs
>> documentation.
>>
>> > There is a strong user community that we can reach out to, to ask for
>> > volunteers.
>> > OR
>> > I even wonder if we can do it as a Kickstarter project. There are a lot
>> of
>> > identi.ca users out there and the social reasons for using Status.net
>> are
>> > very strong.
>>
>> It has to be in some more civilized country than Finland, since
>> Kickstarter is not allowed here! Seriously, one Finnish collaborative
>> writing project didn't get a permission to use Kickstarter funding, so
>> they had to return all of the money they received:
>> http://newshub.fi/archives/688
>>
>> Actually I have to advertise this collaboratively translated article
>> as well, since it might be quite interesting to the readers of this
>> list, it is the story of how Nokia screwed up the Linux-based MeeGo
>> and ended up being eaten alive by Microsoft:
>> http://taskumuro.com/artikkelit/the-story-of-nokia-meego
>>
>> Due to examples like these I have been wondering why Finnish FLOSS
>> advocacy is so unpolitical. There is an urgent need to find a
>> localized version of Stallman.
>>
>> > I know Adam talked to the team before but I might try to contact them
>> to see
>> > what their take on it is. I think it's great that you are doing one in
>> > Finish! That might shame them a bit into supporting a good beginner
>> level
>> > manual.
>>
>> I mentioned this project on Identi.ca and there was a brief discussion
>> about it, but haven't really tried to contact them properly yet.
>>
>> --
>> Best Regards
>> Tomi Toivio
>> Open Source Coordinator
>> http://fi.flossmanuals.net/
>> tomi at flossmanuals.net
>> +358453536625
>> _______________________________________________
>> Discuss mailing list
>> Discuss at lists.flossmanuals.net
>> http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.flossmanuals.net/pipermail/discuss-flossmanuals.net/attachments/20121026/dbdef0c0/attachment.htm>