focus for this week: research helpers
feedback? (popular pages, total: 3,410, >2.9 mio views)

Pump.io

From I ask questions
Jump to: navigation, search

Pump.io is a software (written in e.g. Node.js) which helps you

  • to communicate
  • and more...

statistics

user registrations
(March 26 - May 4)
date
(CET)
hosts users user increase in %
(to last measure point)
user increase per day
(to last measure point)
comment
2013-03-17
9
400
2013-03-26 all new identi.ca users are
redirected to pump.io servers
(see Identi.ca figures)
2013-03-26, 19:31
13
501
25%
11
2013-03-28, 20:24
13
878
75%
189
very likely due to LWN.net article (released 1 day before)
2013-03-30, 00:11
13
989
13%
111
pump2status.net announced 1h ago
2013-03-31, 20:17
13
1074
9%
43
Easter since 3 days
2013-04-02, 00:31
13
1130
5%
56
2h ago these answers made public
2013-04-03, 00:00
13
1252
11%
122
2013-04-04, 23:41
13
1252
0%
0
2013-04-07, 10:32
13
1505
20%
56
2013-04-11, 01:54
13
1624
8%
34
2013-04-14, 19:22
13
1743
7%
32
for ca. 24h identi.ca
didn't deliver dents[1]
2013-04-19, 11:47
13
1885
8%
31
2013-04-25, 16:20
13
2098
11%
34
2013-04-30, 15:41
13
2224
6%
25
since 4-5h: timeouts on identi.ca
2013-05-01, 16:16
13
2250
1%
26
announcement + emails
that identi.ca will use in 1 month pump.io (instead of StatusNet)
2013-05-04, 13:14
13
2453
9%
68
2013-05-07, 15:57
13
2726
11%
88
since 1,2 days major discussions on identica about:
missing client support, backup possibility, ...
(see media section below: 2013 May 6 + 7)
2013-05-10, 11:40
13
2803
3%
27
today another major discussion:
it's decided: no twitter bridge at least until 1.6.
no support of old identi.ca clients (+also federated statusnet servers)
more info on user-dictated ads
2013-05-18, 19:37
13
3033
8%
28
2013-05-28, 12:36
22
3298
9%
27
2013-06-04, 14:15
31
3563
8%
38
the announced migration date (June 1)
postponed first to June2/3 + then June 8
2013-06-08, 17:11
34
3708
4%
36
2013-06-14, 19:58
38
4263
15%
92
2013-06-21, 19:28
39
4733
11%
67
2013-06-27, 19:19
43
5026
6%
49
2013-07-05, 00:07
45
5608
12%
80
2013-07-10, 17:30
48
6163
10%
97
1h ago msg:
identi.ca will be migrated today
-> delay time for migration: 40 days
2013-07-12, 07:34
52
28030
455%
13840
all identi.ca users added now
2013-07-22, 12:19
61
28332
1%
30
2013-07-31, 14:36
66
29092
3%
84
2013-08-06, 17:19
66
30445
5%
225
2013-08-24, 21:51
68
33274
9%
155
2013-09-19, 12:36
72
36599
10%
135

from: pumplive.com

info to identi.ca users

Since there's some confusion:

1. identi.ca is NOT closing
2. identi.ca's software StatusNet was exchanged to this new Pump.io on 10 July 2013
3. no twitter support in near future [1]
4. many/most "old" clients to access identi.ca won't work after the transition (see section: 3rd party apps, [2])
5. 23k users (of the 1.4 mio user accounts) will be ported to the new software
  • backups of other user's data will be on archive.org [3]
    • situation 1.5 months after the migration (2013-08-26): still no backups available :-(
6. see backup section below how to import this into another Statusnet server

FAQ

This "FAQ section" is what we gathered together in this etherpad[2] (since March 13):

identi.ca related

facts

identi.ca registration is closed as of 2013.03.26

communicate alternatives
  • Your friends still can use other SN-servers to stay in contact with their Statusnet buddies
  • meanwhile you could start trying pump.io
  • Q: "If I am following people on identi.ca from my own StatusNet deployment, will I keep seeing their updates or will that break?" [4]
    • Evan (2013, May 1): "That will break, at least for a while. I think we'll get pump.io interface built into StatusNet, but it's not my first priority."
set proper expectations
  • One important thing is that pump.io is radically different from StatusNet.
It's also much younger.
Some things just aren't going to work the way you expect them to; others may never work that way.
Many (most?) of the features needed for this network will not be running when we make a switch over.

questions

How does the switch identi.ca -> pump.io look and feel for the user?
  • Will the user's address still be http://identi.ca/user? only that the engine 'behind' identi.ca will be pump.io instead of status.net?
  • explain the concept 'engine': so far it seems pump.io will do fewer things than the StatusNet software that is powering identi.ca - what features will disappear as a result?
  • There will be no threaded conversations anymore :-( see [6]
Will 3rd party apps continue to work?
  • Almost definitely not. Evan (May 9) announced more delay
    pump.io has a very different API + developers will have to port their apps to support the new API.
    • identi.ca and other sites/services use the OStatus protocol
  • It's possible that we'll have a Twitter API facade available on the day of switchover,
    but it will still require re-configuring the apps to change the API endpoint,
    and for apps that only support identi.ca, there's going to be a lot of tricky parts.



Usage of clients on identi.ca[3] (view complete list):

  • 2013 May 6:
    • 26% use the web UI; (8.4% via api); (7.8% XMPP protocol)
    • 6.6% gwibber
    • 5.8% choqok
    • 3% mustard
    • 2.6% IdentiCurse



client pumpio
support?
comment
gwibber bug report
choqok bug [7], [8]
mustard NO asking dev (notify also on twitter)
identicurse asking devs
"probably no actual support for at least a few weeks" [9]
seesmic / HootSuite asking dev
Adium NO further info
TTYtter see #ttytter (identi.ca)
 ? TTYtter can easily switch endpoints through the config file
but the way it plays out is that you cannot use version 2.1 or later due to Twitter API 1.1 being the highest priority for Cameron Kaiser in development.
2.0.4 is the last version to play nice with StatusNet
Identica-mode (Emacs) NO(t yet) [10]
PyPump yes is a library (not a client)
muon yes "will be a client when someone finishes it" [11]
puma yes Android, apk
Impeller yes announcement, >=Android v4, announced: May 10, Apache License 2.0
Dianara yes May 2: Diaspora support canceled + pumpio support will be added
"It is still in the early stages of development."
Pumpa yes written in C++ and Qt
Laraib yes Ruby library
QTdenter [12]
Pidgin NO
mediawiki extensions see e.g. SendToIdentica
or Send2StatusNet (will work for federated SN sites still)


  • inform 3rd party devs/services
    • This is a great idea; it would be an immense help to me for people to start reaching out to 3rd-party devs, starting bugs in their trackers, etc.
    • that their tools won't work anymore (or what will not work anymore)
    • so they've enough time to code up things
    • Will there still be an Atom or twitter-like xml timeline feed? Or only Json? Or other more exotic formats?
      • Some of this will be part of the Twitter API facade.
Bridging (pump.io <-> SN)
  • Evan (May 2): "about bridges to other services"
  • Interoperability between StatusNet and pump.io will probably not happen with a bridge.
  • There will be a new plugin for StatusNet that will support the pump.io API
    • it will work with pump.io clients
    • it will federate with pump.io servers
    • I don't have a timeframe on it
  • pump2status.net (pump2status source code)
    • This software shows how we'll probably have bridges to other networks like Facebook, Google+, Twitter, etc.
    • The two main pieces of functionality will be
      • Find your friends from <other network> on pump.io (help with on-boarding)
      • Send your pump.io activities to the other network (for at least Facebook, this is a requirement for using the API)
    • "But if StatusNet <-> pump.io interop is going to be at the protocol level, why build pump2status at all?"
      • Most people evaluating pump.io right now were StatusNet or identi.ca users, so "find my StatusNet friends" was a very useful feature
      • It lets me work out the kinks without worrying about some API TOS shutting down the whole thing
  • BridgesArchitecture (wiki)
  • What contents will bridge carry across?
  • What contents will the bridge not carry across?
    • N/A, StatusNet and pump.io won't interop with bridges.
  • Is the bridge a centralized service (e.g., one bridge for all SN to all Pumpio) or will each SN host and each Pumpio host need to host bridging? Federated sites will want to know this before the switchover occurs.
    • N/A, StatusNet and pump.io won't interop with bridges.
  • Will formatting cross over? (Many federated SN sites use Textile plugin to enable post formatting.)
    • The content part of an activity is in formatted HTML. The formatting will cross over but probably not the "source".
  • Will bridging depend on SN-specific hooks, or will other OStatus-supporting applications (Rstatus, Friendica) potentially be supported?
    • Supporting OStatus will probably happen with a bridge. Unlike the Facebook, Twitter, etc. bridges, it will probably be two-way. From either "side" of the bridge, the other network would look like a single site.
    • So if evan@pump.example wants to follow mike@friendica.example,
      he could follow mike%friendica.example@ostatusbridge.example,
      and for Mike he would look like evan%pump.example@pumpbridge.example.
    • There's no reason third-party devs can't implement the pump.io API
    • There is a lot of PubSubHubbub-enabled content out there (Blogger, WordPress, Tumblr), so it's pretty valuable to build this.
Content types
  • What types of content (posts, 'blogs', bookmarks, polls, questions) from SN will Pump.io support?
    • Good question! Right now it supports notes and uploaded files pretty well (although the Web UI only accepts images).
    • Other activities will have mixed support. I think most of them will store into streams OK, so they won't get "lost", but it's unlikely that we'll have in-stream apps (like with polls or events) anytime soon.
  • What Pump.io content types should be ported to SN?
    There are only two content types currently: notes and photos.
    I would expect the photo type to be generalizable to include embedded media and uploads of all (supported) types.
    • This is less clear to me.
  • Are there any other content types that either application lacks? If we are are in the process of adding types to either application to make it more compatible with the other, we may be able to likewise add new content types to each to enhance their cooperation. This can wait until after transition is completed.
StatusNet modification
  • Will it be necessary or desirable to make federation plugable?
    That is, might we wish to be able to add federating plugins to allow SN to better interact with Pumpio, Tent, Red, Diaspora, Buddycloud, Friendica, or other federated networks as desired?
    • Probably yes. OStatus is implemented as a plugin in StatusNet right now.
  • If existing federated sites face the possibility of needing to alter their codebase, perhaps it can be done in such a way that adding other federation protocols is easier.
History of identi.ca
  • Will the existing history of Identica and other E14N-hosted SN sites be preserved when sites switch over?
    • If by "history" you mean the activities of each user, a qualified yes.
      Only users who've been active in the last 12 months will be ported over.
  • If Identi.ca userbase is split up onto 10 or more Pumpio servers, will existing historic links be modified to point to users' current profiles?
    • Right now, the plan is not to split into multiple pump.io servers.
      identi.ca will be on its own big pump.io server.
    • This kind of sucks, because it means that we've got a big supernode problem again,
      but I hope that having registration disabled on identi.ca will drive growth to other servers.
    • Obviously people who are interested in federation should put some time into setting up their own servers.
  • SN internal shortURLs (ur1 dot ca): will they be preserved? Or will those links become dead?
    • preserved: [13]
    • I'm going to try to make at least notice URLs, user urls, and internal short URLs work. I'm sure there will be a lot that don't work.
      • 'If you use the internal URL shortener, you have short URLs like "http://identi.ca/url/<number>". Those should work after the conversion.' [14]
    • "... there are many kinds of URLs, like people tags and search, that aren't part of pump.io. Those will 404 error" [15]
Transition process for federated SN sites, Twitter
  • Not all SN sites will remain as SN sites once the central SN site (Identica) moves to Pumpio.
    Will there be documentation of a migration process for those who choose to move their sites from SN to Pump?
    • I will move all public (community and single-user) status.net sites to pump.io
      • There are about 2000 still active; I need to weed out the spammers, but even then I'll probably need some kind of multi-homing
    • Users who want a backup of their "activity streams dumps" (so they can set up their own StatusNet site)
      should email me at admin@e14n.com
    • Private status.net sites (set to private, used by companies) will probably be shut down
    • Some status.net sites like urmf.net will move earlier to test out the transition;
      others will go after identi.ca.
      status.net sites don't get anywhere near the traffic of identi.ca so they can keep going for a while.
  • Federated SN sites that also choose to transition to Pumpio may need some documentation of the process, particularly transferring the database and duplicating some of the old URLs on the new site.
  • Loss of contacts (from either direction) could cause a little bit of chaos, which could be unsettling. Perhaps a #moving tag could be promoted as a way to inform contacts of pending changes.
  • External OStatus contacts will probably be lost
    • There may be ways to make that easier
  • Will my Twitter follows also be migrated?
    New twitter follows have been turned off, but there are still some twitter follows in Identi.ca that I don't want to lose. Example dent: https://identi.ca/notice/87448345
    • There will be a Twitter bridge.
    • It will almost definitely not be operational by the switchover.
    • It will concentrate on the two main bridge functions:
      - find your Twitter friends on the pump network,
      - and post your pump.io activities to your Twitter account.
    • I think it's unlikely that I, for one, will build a wrapper around Twitter.
      It's functionality in StatusNet that I'm growing to hate.
      If we want to have a federated social network, we need to live there, not spend all our time looking over the fence at Twitter.
    • Twitter is a click away. If you really want to use Twitter, go use Twitter.

mention backup

Import a backup from StatusNet says: "The default backup file for StatusNet users includes: notices, followers and following, likes, group membership."
  • 2. export only your dents:
    • a. Python script (because I had errors when exporting) for import/export of dents: backup identi.ca account
      • max. 6000 dents
      • I'm the author of the script. I'll update the README with instructions how to download the script w/out knowledge of git. Perhaps also an easy-to-follow blog post if I've time.
    • b. new script: statusnet backup script
  • There will also be automated, opt-out backups on archive.org.
    All your public notices will be pushed to archive.org's S3-like service in an Activity Streams dump.
    Even if you sleep through the transition, you can get this backup much much later, and others can review it for whatever reason. No private stuff in there, though.
  • Both options above seem to provide an incomplete set of what data exists "in" an account;
    a "complete" backup should contain (please extend list):
    • dents yes
    • repeats yes
    • direct messages sent, with addressee acct no
    • uploaded files (or a complete list + a method to download) no
    • profile description & URL yes
    • list of personal (profile) tags yes
    • profile image no
    • list of subscriptions (including to remote accounts) yes
      • with any attached "people tags" no
    • list of group memberships (including remote) yes
    • ...
  • Problem with getting a backup of your data is then: What on earth do you do with it?
    The third-party devs for Identicurse and the like may need to be encouraged to work on tools to take the StatusNet dumps to be able to turn such into somewhat human-accessible views.
    • You can restore them to another StatusNet account.
importing your backup into another StatusNet server
  • The backup on archive.org will be in activity streams format + one can restore it via:
    • "restore" feature in the web service [16] AND
    • the restoreuser.php script
  • this backup does NOT include:

clarity what's going to happen about SN

  • Will there be some sort of "official"/endorsed branch for SN?


Status about the StatusNet wiki: http://status.net/wiki/ ?

  • It will definitely stay up for a while but it'd be great to transition it to a new home

Pump.io related

  • central communication place?
    • blog?
    • Evan's notices, somehow marked as 'important' and collected like a blog?
      • https://e14n.com/evan is the best place to look for updates.
      • Important ones will be linked as mentioned by @identica and on the site notice
  • tutorial for how to use pump.io
    • explain how to subscribe to others [log in via 'account on another server?' doesn't seem quite obvious to people]
    • Great idea; I hope someone works on this
  • known bugs (so people won't report obvious problems over and over)
    • bugtracker (at github)
    • Yes, great
      • Note that I've been capturing some stuff in this issue list that strictly speaking will be implemented
  • Why was node.js selected ?
  • How many users does a pumpio server allow ?

What can you do?

  • try the public sites at http://pump.io/tryit
  • Install pump.io on your own system
  • Report bugs here
  • Work on client libraries (see 3rd party apps above)
    • Super important!
    • Lots of languages needed
  • Work on apps
    • There are probably 12-20 apps, bridges, and search engines mentioned in this document alone
    • We need apps for mobile platforms and for desktop platforms
    • If you work on something really popular (like XMPP bridge ) you have a chance at fame and fortune
    • Scratch an itch

Evan: Some things I want people to think about

  • This is a really, really exciting time. I have not been this excited about federated social web technologies in many years.
  • "Doing more with less" means that the core of the pump network (pump.io) is going to do just a few things really well.
  • All the interesting stuff is going to happen in web, mobile, and desktop clients
  • That means it's up to you to work on it
  • A lot of code that hasn't been written == a lot of exciting projects to work on. Lucky us!
  • Need at least 2-3 example use cases to explain to people how they can build around the pump.io core so as to better understand the paradigm

user feedback

I think many people are now aware of what the pump.io intro on identi.ca really means. Let's collect some opinions:

  • "I don't see how this is for the "well-being" of pump.io - instead of connectedness, we'll just get a new island", @marjoleink, 2013-05-06
  • "the more I think about it, and all the unfinished software, and a less-than-amonth deadline, the more I think it's totally destructive", @marjoleink, 2013-05-06
  • "technically great (performance x5), legally bad (AGPL→Apache), socially bad (breaks API + LAMP→special) — new identi.ca", @arnebab, 2013-05-07

media

title date language author(s) identi.ca user? type comment
StatusNet, Identi.ca, and transitioning to pump.io 2013-03-27
en
Nathan Willis in LWN
Microblogging - Umbau bei Identi.ca 2013-05-04
de
Hanno Böck in golem.de
upcoming Identica / Pumpio transition 2013-05-06
en
mcnalu + Gordon Sinclair
in Crivins audiocast
yes
podcast
Crivins - episode 61
starts at pos. 30:40
Mikroblogging: Identi.ca wechselt die Software-Plattform 2013-05-06
de
too short,
not much info
The revenge of Amarok 2013-05-07
en
Urpo Lankinen
yes
The End (Of My Time On Identica) Is Nigh 2013-05-09
en
Gordon Sinclair
yes
further info
Identi.ca is throwing away everybody’s work that made identi.ca what it is 2013-05-28
en
Roy Schestowitz
yes
Understanding pump.io 2013-06-03
en
Evan Prodromou
yes
slide show/presentation
pump.io: the decentralized social network that's really fun 2013-07-15
en
Evan Prodromou
yes
Fork off you utter cad 2013-09-29
en
yes
starts at 51:30, summary here

notes

  1. I was expecting that this could have an effect on new pump.io users, but the trend stayed
  2. since many people edited this text on Etherpad the text from this "FAQ section" is not available under this wiki's licence, please msg me about questions regarding this. Some of its contributors can be seen here.
  3. this stat is from a subset of all dents on identi.ca but you can imagine that a trend still keeps its high value

see also

Pump.io:


other links: