- Let's do a little experiment. It's obviously biased by my relative participation in each, but I'm comparing the reach of twitter, facebook, Diaspora, pump, G+, and GNU Social (plus anything that can talk directly to it...that is not via NavierStokes).Please like this if you see it. Obviously, if you want more people to like it, then you share it, but I'm only going to count likes.Show all 12 repliesHere are the final numbersGNU Social/Mastodon: 49pump.io: 31Facebook:26Diaspora: 15G+: 7Twitter: 0What's interesting is that on Diaspora, pump, and GNU Social, I all got actual comments about how the study was being conducted. I got literally zero comments on twitter or G+. There's all sorts of bias in this, but I have more "friends" on facebook by an order of magnitude and significantly more on twitter than the free platforms. So, it seems like people join the proprietary networks and just don't use them very much.GNU Social up to 97: https://nu.federati.net/conversation/510099#notice-1072972
I am going to use this account more.
Ran 24km today. First time in around four years. Ah, I'm tired. Legs did better than expected. Didn't time it, and didn't push the pace.
wow .. it was hard enough for me when as a kids we were asked to run around the school !
back then I did ok (not winning but above average) on short sprints but for me running long distances was torture.
around the school perimeter was already a "long distance" for me
Got in a 10k run today. Haven't done that in two months cuz of work. (Had been only going 5k.) Feels good to hit the longer path through Koganei Park.
- I updated the identi.ca cert. Thanks to everyone who told me about it.Show all 5 replies
- identi.ca went ↑↑↓↓←→←→B A Start but it's OK now.Show all 7 replies
- Identi.ca cert updated.
- identi.ca had a problem; I restarted it. Thanks for the reports.
Happy Birthday Evan!
Happy Birthday @Evan Prodromou! Thanks for making possible awesome communities in the #freesoftware #socialnetworks #StatusNet #PumpioShow all 19 replies
If your pump.io server is identi.ca...
...remember the Pump network is much more than that! ;)
Lots of things changed when identi.ca migrated from the StatusNet system to the Pump.io system.
- Pump.io is not microblogging. You can post long texts, with some formatting and line breaks. Well, like this one! You can post short text if you wish, of course. Also, you don't need shortened URL's, and you can make pretty links.
- You can follow people from any other public Pump.io server, like microca.st, hotpump.net, fmrl.me, pump.jpope.org, etc. Start following some new people! You can take a look at this user finder, for instance. Or keep an eye out to see who your friends are following, in the Meanwhile feed ;)
Don't be afraid to follow people from other servers. That's what federation is all about, and that's our strength! If you've been scared by the "permission" message using the web, where you have to authorize the other server to post as you, etc, know that this isn't necessary if you use a desktop client.
- If you use the web interface, when you create new posts, they are not public by default. If you want to make a public post (currently recommended due to some issues with the comments), you'll have to add "Public" to the "To:" field. Try to make at least one public post, so people who see your profile can see you're active before trying to follow you. Ideally, if the post can be public, you should post it to Public; it works better.
- You can use several external web services with your account, like hip2.it, pump2status.net, or the "proof of concept" game, OpenFarmGame, to name a few. One of the strenghts of Pump.io is not being a monolithic beast, but instead, a lot of connected services an applications providing all kinds of features. Check them out!
- You can upload pictures, audio, video and other files in your posts, though the officially "supported everywhere" attachments are pictures, for now.
- There are already several pump.io applications (clients), for PC or mobile devices that can do more than what the web interface can at this point. I seriously recommend checking them out: Clients List.
- You can check out a pseudo-user directory at inventati.org/ppump/usuarios.
- If your account was used for some sort of entity, like a free software project or organization, you can take advantage of tools like Spigot, to post to Pump automatically from your RSS feed, or PumpTweet, to automatically send your Pump.io posts to Twitter. And you can find more options here.
If you have any doubts about any of these points, please feel free to ask.
This list has been modified a few times, and might be modified again, because yes, you can edit your posts and comments in Pump.io! =)
Edit: Posted as a blog post at CommunicationFreedom.
Spanish version at ComunícateLibremente.Show all 26 replies
@Jason Self, about pump2status.net, the site goes up and down all the time (I have reported that some months ago...), but it works, once you pick a moment when it's up and you configure your account. My notes (if they are shorter than 140 chars) arrive my quitter.se account every day, even if the site looks down.
For getting it up (so you can setup your bridge), I think the best is that you mail admin [at] e14n.com. I would do it myself, but I prefer that other people show that the service is interesting too (sometimes I think I am the only user of pump2status.net...).
In the pump.io wiki there's a page Clients with detailed info about much of the software/service pieces that form the pump.io network.
Hope that helps!
- Bradley Kuhn recently me asked me what the plan is with pump.io. He pointed out that there a number of UI bugs with the Web interface, as well as some essential federation issues (for example, how comments don't get distributed to all followers).
As most of you know, I've taken another full-time job, and pump.io has become a side project for me. A beloved side project that matters to me very much, but it's no longer what I spend all day working on.
When I do have time to work on it, much of my work is system administration. E14N has some money still, but there's not any new money coming in, so I have to use what's left sparingly. Using cheaper resources more wisely with more efficient software is a big investment for me right now -- it means that we can keep these services running almost indefinitely.
The good news there is that this has mostly been a success. From a peak in 2011, the cost of running the servers E14N uses has gone down two orders of magnitude. That's a huge step.
That also means that I find myself with more time to work on the core software and supporting sites.
Another big step is the incipient Social Web Working Group which I will be co-chairing. The group has a mandate to build a social data format, a client-to-server API, and a server-to-server protocol for social interaction. It's likely that the resulting suite of standards will bear a close resemblance to the current pump.io API, and I definitely intend to track it.
Bradley asked me, "What's the plan?" and I'm going to take this opportunity to sketch out a plan for where pump.io is going.
- Over the next week, I'm going to take the current state of pump.io and release it as version 0.3 and start the 0.4 development. Yes, I realize there are still bugs outstanding, but it's probably time to just stamp it and move on.
- In the same time, I'm going to deal with the long list of pull requests and open issues with pump.io. The PRs will either get a reply, get pulled to 0.4, or closed. The issues will get put into milestones for 0.4 or "maybe later" or "probably never".
- I've been working on the Facebook bridge for pump.io, and I'd like to get that operational before starting any other development work.
- My next project will be a Github bridge to share data about commits, issues, and pull requests to accounts on pump.io. I think that will help with some visibility of the development activity.
- I'm going to convert the pump.io codebase to CoffeeScript. This may sound radical, but it's mostly a mechanical process with js2coffee. CoffeeScript is a mostly syntactical transformation of JS, and it's really a lot more fun to write. All the regular NodeJS libraries and modules work fine with CoffeeScript, and the installation process will stay the same (no coffee binary needed).
- I'm going to upgrade the pump.io dependencies -- Backbone, Bootstrap, Express, etc. A lot has changed in the last few years, and I'd like to keep up better.
- Start knocking down bugs in the core software -- mostly concentrating on distributed conversations and the notifications in the Web UI, but seeing if there are others that can get fixed.
- I'd like to release an 0.4 version by September of this year.
I appreciate everyone's attention to pump.io. I know that you've all put a lot of work into this platform, and I really appreciate it. I especially love that there are so many new clients and tools for the platform -- having that kind of ecosystem has been especially important to me.
And everyone who's put their online social presence into an E14N server -- believe me, it's appreciated. You are literally the lifeblood of this network, and making things work right for you is why I do this.Show all 19 replies
>> howcanuhavemyusername (Metal Biker):
“What about OStatus bridge with the other federated social platforms?”
There is a bridge to StatusNet/GnuSocial. What would be great would be if GnuSocial added a Pump plugin on their side to have transparent federation, not bridges.
[ Reposting this comment to make sure it appears publicly ]
Evan, first of all, in case you didn't see my later comment after my post, I want to link to it here. My main point there is that we need to start thinking about pump.io as a community-oriented volunteer project now, and that's a good thing. Everything will take longer, but such projects have a long history of producing much better, longer-lasting results that VC-funded stuff.
I don't have a lot to give, but I'd happily give $5 toward a Kickstarter. But, if you're talking about what I think you're talking about, I suggest you team up with the FreedomBox people and see if they have money left.
I've been critical of FreedomBox because it took on too much. It tried to make a home server for all network services everyone could imagine where 'hard reboot' was the only sysadmin task. But, pump.io actually seeks to be what the FreedomBox said it would be on the social networking part, so you should at least talk with them about helping you with fundraising.
Related to that, I encourage pump.io to apply to be a member project of Conservancy. (Of cousre, as a member of our Evaluation Committee, you'd have to recuse yourself of course from discussion about joining post-applying.) That would bring to bear the (albeit) meager resources of Conservancy to help with your fundraising and other efforts. We may be even able to get you gratis VPS's for pump.io if you don't have them already
As you know from your work on the Eval Committee, no one eval committee member can assure acceptance of an application, but I would strongly support your application and I expect other eval members would to. The downsite for you is it would mean E14N letting go of the project, which may be just too painful to consider after all the work you put into.
Evan, thnk you again for all you'e done: since we started autonomo.us, I truly think you are the only one who did more than "just talk" about what freedom for network services should be. You have worked for almost a decade now non-stop to make it happen. While we don't have a solution, you put a lot of great code out there and our community learned a lot. True federated social networking is one of the hardest technical problems our community has ever tried to solve, so any progress forward is impressive.
Thank you, Evan, for all you have done. You are a true hero of software freedom. (And I'll be nominating you for the FSF Award for the Advancement of Free Software, BTW, and I hope others will too. :)
To answer your question, @Evan Prodromou: "It's not, and Mozilla must adapt or die."
That said, adaptation is necessary to survival but the community must continue to push content onto platforms that are owned by the community so that DRM is a non-issue for the things people create. Companies will do what they want, but that doesn't mean we have to follow them like sheep.