Re: Debian identi.ca account/group after migration to pump.io
Hi all
Thanks everybody for your good advices.
Sorry for the top posting, and sorry for the long email, but ideas are
coming from different messages, and I think I can make a wrap-up and
try to find a way to solve this social network puzzle.
The goal of this proposal is to "restore" the functionality that we
had before the migration status.net >> pump.io.
1.- Publish the RSS feeds in identi.ca, as debian@identi.ca was doing
before the migration.
* Those RSS feeds are produced "inside the Debian project" (RSS in
Debian.org machines):
http://bits.debian.org/feeds/feed.rss
http://planet.debian.org/rss20.xml
http://www.debian.org/News/news
* There are some more (dsa...), but I think these are the ones that
were published when identi.ca was powered by status.net.
* Given that there's no built-in feature in pump.io (identi.ca) to
import an RSS feed, a third party client/service has to be used. We
have Spigot (client) and Brdcst.it (service).
** After reading this thread and also this article
http://notes.pault.ag/debian-python by @paultag, I understand the
problematic around packaging/installing python apps in Debian, so I'll
discard this option by now.
** Brdcst is SaaS licensed under AGPL. Michele Azzolari, the author,
also runs a public server and you can ask for an invitation (I did,
and tried the service, and it works. I know other people using it
too). You can create and delete bridges, so you can set all the RSS as
"input" and the pump.io account as output.
http://brdcst.it
Source: https://gitorious.org/brdcst/
Request invitation by mail: brdcst@brdcst.it
** I think requesting an invitation is the best option for now.
We are using a 3rd party service, but just for propagating RSS feeds
that we "produce at home". Brdcst is free software, and identi.ca
itself is also a 3rd party service... If the service has problems or
shuts down or changes (as identi.ca did), we can discuss again what to
do.
2.- Live denting
* Live denting may happen in identi.ca using its web interface or the
client that the person writing the dent prefers. The same situation as
when identi.ca was using status.net, I suppose.
* With statusnet the user could make a backup of the whole account
(dents, followers, following etc). This is not implemented in pump.io
yet, but you can get the public feed by RSS:
https://pump2rss.com/feed/debian@identi.ca.atom , and the user can
also get the feeds in ActivityStreams format using a web browser (you
previously login in identi.ca with that browser):
https://identi.ca/api/user/debian/XXX
being XXX: feed, inbox, followers, following, lists, favorites, profile
Those JSON files can be sent periodically to any place in Debian to be
stored and accessible for the people who should have access right.
I know that it would be desirable to automate this task, but before
the migration, in StatusNet this was a manual task too...
3.- Crossposting to other social networks
Before the identi.ca migration, AFAIK the publicity team didn't setup
any bridge from identi.ca to other places. Other people could get the
identi.ca RSS feed and handle it. Now they can do it too, in this URL
https://pump2rss.com/feed/debian@identi.ca.atom
I can volunteer to propagate the debian feed in the statusnet
fediverse, registering a non official debian account in quitter.se and
joining the two debian groups.
4.- Interaction with users
Before the identi.ca migration, AFAIK the publicity team didn't
interact with people in other social networks different than
identi.ca. The non-official accounts maintainers were doing that. We
can keep on using this system.
I can volunteer to promote debian in the statusnet fediverse, if you
agree with (3).
5.- Group
Before the migration, we had 3 groups
http://identi.ca/group/debian
http://identi.ca/group/debiangis
http://identi.ca/group/debianwomen
Right now, we have no groups in identi.ca, and they cannot be created.
I think this will change soon:
https://github.com/e14n/pump.io/commits/master
I propose to wait.
And I think that's all.
Regards
Laura Arjona
2013/10/10 Stefano Zacchiroli <zack@debian.org>:
> On Thu, Oct 10, 2013 at 05:24:24PM +0800, Paul Wise wrote:
>> It has a couple of disadvantages I can think of:
>
> Right. It seems to me that both are related to the fact that proper
> interaction with other users of a social network is intrinsically a
> social-network-specific (rather than -agnostic) activity. If you want to
> live-"tweet", you really want to do that on the platform in question, if
> you want to keep react to interactions with others, same.
>
> AFAICT this is not in opposition with the idea of a central source for
> the "tweets". But it does add an extra requirement: that source should
> not be the only source, but it should rather be possible to have other
> "tweets" on each social network. That way we can have a common baseline
> for all of them, and invite volunteers to do the extra work of
> interactive on a network-by-network basis.
>
> Cheers.
> --
> Stefano Zacchiroli . . . . . . . zack@upsilon.cc . . . . o . . . o . o
> Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o
> Former Debian Project Leader . . @zack on identi.ca . . o o o . . . o .
> « the first rule of tautology club is the first rule of tautology club »
Reply to: