Updates tagged with pumpio on Jonkman Microblog!
lnxw48a1: Actually, I think the two #bots were around for part of #GNUsocial after the #bifurcation split the network into #OStatus (mostly GS) and #Pump.io
lnxw48a1's status on Saturday, 08-Jul-2023 04:22:56 EDT
Actually, I think the two #bots were around for part of #GNUsocial after the #bifurcation split the network into #OStatus (mostly GS) and #Pump.io
fu: lxoliva@identi.ca is this public post from #Friendica working on #identi.ca? #pump.io #pumpiverse
fu's status on Monday, 13-Feb-2023 12:38:59 EST
lxoliva@identi.ca is this public post from #Friendica working on #identi.ca? #pump.io #pumpiverse
lnxw48a1: @clacke That reminds me that I have been planning to log back into #Identica just to see what things are like in #Pump.io land.
lnxw48a1's status on Saturday, 21-Jan-2023 00:48:20 EST
@clacke That reminds me that I have been planning to log back into #Identica just to see what things are like in #Pump.io land.
lnxw48a1: One thing about this surge of people migrating from #Twitter to the #Fediverse is that people who gave up on #federated #socnets years ago and solely used #corpocentric platforms are now coming back. Thus, I get announcements about people I knew from #Tent (thanks to fellow former Tentler @bthall) along with news about people from #Identi.ca and other #StatusNet and #Pump.io instances returning.
lnxw48a1's status on Tuesday, 27-Dec-2022 14:25:03 EST
One thing about this surge of people migrating from #Twitter to the #Fediverse is that people who gave up on #federated #socnets years ago and solely used #corpocentric platforms are now coming back. Thus, I get announcements about people I knew from #Tent (thanks to fellow former Tentler @bthall) along with news about people from #Identi.ca and other #StatusNet and #Pump.io instances returning.
lnxw48a1: I actually think that the overwhelming majority of blocking should be done by individuals curating their own timelines. I am sensitive to the effect on the Fediverse as a whole, especially as we've already been through this. Even the original #bifurcation (when the largest instance at the time, Identica, severed communication with #StatusNet / #GNUsocial & #OStatus and switched to the #Pump.io protocol and software) and the subsequent #ActivityPub - #OStatus split have caused untold breakage. I've seen AP-side devs, admins, users patting themselves on the back while commiserating about brokenness that is built into the protocol itself or at least its common implementations. I have also seen people telling other people to create "alts" on various instances, so that their posts can reach all of their intended contacts. Not for resilience against instance shutdowns or separating by posts and recipients by topics and interests (which is what groups and Diaspora style Aspects / GPlus style Circles are for), but because #blockwars prevents posts and members from one instance to be seen on certain others. For the record, I think that instance governance is something that Mastodon should include in its instances.social instance-picker, along with instances' topical foci. People should have a way to see what they're agreeing to (and what the alternatives are) before the sign up. In other words, it isn't my way or the highway so much as it is making it possible to know what one is getting into. I am certain that there are (or were) instances with democratically chosen rules. I also believe that we're not doing the people who use an instance any favor by not making it possible for them to contribute to the financing and administration of the instance. If you're paying all the costs and doing all the work to maintain and moderate the instance, it is difficult to let an election institute a policy that you disagree with. (I've started to really disagree with the idea of individuals hosting public instances wholly out of their own financial and time resources. Besides the "truck factor", it is much easier to keep an instance going if everything was already handled by a team and at least partly member supported.) On the other hand, if the instance encourages those in its membership who can do so to participate in keeping it going, then it is perfectly reasonable to expect the admin team to carry out the decisions voted by the membership. I do realize that not everyone can contribute funds, nor can everyone do the technical labor ... but as @simsa04 will remember, things like writing documentation, contributing in discussions about improving the software, designing and implementing themes, and even marketing-type tasks such as creating a logo and a favicon or promoting the instance to people outside the #Fediverse are beneficial.
lnxw48a1's status on Sunday, 30-Oct-2022 00:26:23 EDT
I actually think that the overwhelming majority of blocking should be done by individuals curating their own timelines. I am sensitive to the effect on the Fediverse as a whole, especially as we've already been through this. Even the original #bifurcation (when the largest instance at the time, Identica, severed communication with #StatusNet / #GNUsocial & #OStatus and switched to the #Pump.io protocol and software) and the subsequent #ActivityPub - #OStatus split have caused untold breakage. I've seen AP-side devs, admins, users patting themselves on the back while commiserating about brokenness that is built into the protocol itself or at least its common implementations. I have also seen people telling other people to create "alts" on various instances, so that their posts can reach all of their intended contacts. Not for resilience against instance shutdowns or separating by posts and recipients by topics and interests (which is what groups and Diaspora style Aspects / GPlus style Circles are for), but because #blockwars prevents posts and members from one instance to be seen on certain others. For the record, I think that instance governance is something that Mastodon should include in its instances.social instance-picker, along with instances' topical foci. People should have a way to see what they're agreeing to (and what the alternatives are) before the sign up. In other words, it isn't my way or the highway so much as it is making it possible to know what one is getting into. I am certain that there are (or were) instances with democratically chosen rules. I also believe that we're not doing the people who use an instance any favor by not making it possible for them to contribute to the financing and administration of the instance. If you're paying all the costs and doing all the work to maintain and moderate the instance, it is difficult to let an election institute a policy that you disagree with. (I've started to really disagree with the idea of individuals hosting public instances wholly out of their own financial and time resources. Besides the "truck factor", it is much easier to keep an instance going if everything was already handled by a team and at least partly member supported.) On the other hand, if the instance encourages those in its membership who can do so to participate in keeping it going, then it is perfectly reasonable to expect the admin team to carry out the decisions voted by the membership. I do realize that not everyone can contribute funds, nor can everyone do the technical labor ... but as @simsa04 will remember, things like writing documentation, contributing in discussions about improving the software, designing and implementing themes, and even marketing-type tasks such as creating a logo and a favicon or promoting the instance to people outside the #Fediverse are beneficial.
lnxw48a1: It's important to keep in mind that GS survived the #bifurcation (when the largest instance #Identica switched to #Pump.io).
lnxw48a1's status on Monday, 15-Nov-2021 20:57:59 EST
It's important to keep in mind that GS survived the #bifurcation (when the largest instance #Identica switched to #Pump.io).
lnxw48a1: He did, but he kept control of them, so when his funds ran short, most of them disappeared. I've thought about deploying a Federati #Pump.io instance, but it runs atop #Node.js. I'd want to rent a completely separate server ( #VPS ) for it, so nothing else is affected if a poorly understood #JavaScript engine goes haywire.
lnxw48a1's status on Tuesday, 24-Aug-2021 22:55:57 EDT
He did, but he kept control of them, so when his funds ran short, most of them disappeared. I've thought about deploying a Federati #Pump.io instance, but it runs atop #Node.js. I'd want to rent a completely separate server ( #VPS ) for it, so nothing else is affected if a poorly understood #JavaScript engine goes haywire.
lnxw48a1: @musicman I know #django moved to LiberaChat, but #python is still debating it. #haskell is moving also. I also checked #nim, but I did not see any discussion about moving. Neither Evan nor Alex have expressed an opinion about moving #pump.io, so I suspect it will remain on Freenode. I checked #hubzilla, but there doesn’t appear to have been any discussion about it. I left #friendica after someone set up a really noisy bridgebot, so I don’t know whether they’re moving. I also left #mastodon Freenode is the official IRC host for the GNU project, so a lot of GNU software is awaiting a decision from GNU. (All hashtags above are names of Freenode IRC channels / rooms, some of which are in the process of moving to Libera.Chat or OFTC.)
lnxw48a1's status on Tuesday, 25-May-2021 12:58:48 EDT
@musicman I know #django moved to LiberaChat, but #python is still debating it. #haskell is moving also. I also checked #nim, but I did not see any discussion about moving. Neither Evan nor Alex have expressed an opinion about moving #pump.io, so I suspect it will remain on Freenode. I checked #hubzilla, but there doesn’t appear to have been any discussion about it. I left #friendica after someone set up a really noisy bridgebot, so I don’t know whether they’re moving. I also left #mastodon Freenode is the official IRC host for the GNU project, so a lot of GNU software is awaiting a decision from GNU. (All hashtags above are names of Freenode IRC channels / rooms, some of which are in the process of moving to Libera.Chat or OFTC.)
lnxw48a1: I’m still looking for a low priced annual payment VPS provider that has a somewhat lower risk (of closure, hardware failure, etc) than most LEB hosts, so I can launch temporary testing instances (for example, the upgrade of GS to the #ActivityPub enabled 2.0 branch, and looking at how well #Zap, #Pleroma, #Friendica instances fit into the !FNetworks roadmap). I’m also considering adding a Federati #Pump.io instance, but I need to talk with the Pump.io project about SSO options. Since they use Node.JS, I’d want it on a completely separate VPS, with some restrictions to prevent incidents. Also, if utilization is too low, that would likely close. Currently, everything is still coming out of my pocket.
lnxw48a1's status on Monday, 10-May-2021 19:00:34 EDT
I’m still looking for a low priced annual payment VPS provider that has a somewhat lower risk (of closure, hardware failure, etc) than most LEB hosts, so I can launch temporary testing instances (for example, the upgrade of GS to the #ActivityPub enabled 2.0 branch, and looking at how well #Zap, #Pleroma, #Friendica instances fit into the !FNetworks roadmap). I’m also considering adding a Federati #Pump.io instance, but I need to talk with the Pump.io project about SSO options. Since they use Node.JS, I’d want it on a completely separate VPS, with some restrictions to prevent incidents. Also, if utilization is too low, that would likely close. Currently, everything is still coming out of my pocket.
lnxw48a1: Now discussing changes needed to switch to #ActivityPub instead of their #Pump.io protocol (an ancestor of AP).
lnxw48a1's status on Friday, 18-Dec-2020 16:20:44 EST
Now discussing changes needed to switch to #ActivityPub instead of their #Pump.io protocol (an ancestor of AP).
lnxw48a1: Looks like #pump.io will be having a release soon. They're merging in security patches for dependencies and replacing #node.js 13 with 14.
lnxw48a1's status on Friday, 18-Dec-2020 15:44:42 EST
Looks like #pump.io will be having a release soon. They're merging in security patches for dependencies and replacing #node.js 13 with 14.
lnxw48a1: If you're insterested in #Pump.io, they're having a meeting at 20:00 UTC. See https://github.com/pump-io/pump.io/wiki/Meeting-2020-12-18 for details.
lnxw48a1's status on Thursday, 17-Dec-2020 21:29:25 EST
If you're insterested in #Pump.io, they're having a meeting at 20:00 UTC. See https://github.com/pump-io/pump.io/wiki/Meeting-2020-12-18 for details.
lnxw48a1: that's #pump.io on-screen keyboards stink
lnxw48a1's status on Thursday, 19-Nov-2020 15:57:02 EST
that's #pump.io on-screen keyboards stink
lnxw48a1: Unless he's using his https://identi.ca/evan #Pump.io account, he must not be active on federated networks. His https://e14n.com/evan 'main' doesn't even load.
lnxw48a1's status on Thursday, 29-Oct-2020 12:02:38 EDT
Unless he's using his https://identi.ca/evan #Pump.io account, he must not be active on federated networks. His https://e14n.com/evan 'main' doesn't even load.
miradlo: 🙁 Unfortunately, nothing happend since your last promise. @evanpro Since 2013 old accounts cannot be deleted. #identica #pumpio ♲ @evanpro@twitter.com: @miradlo Send me an email at evan at prodromou dot name and I'll take a look.
miradlo's status on Wednesday, 10-Jun-2020 08:31:18 EDT
🙁 Unfortunately, nothing happend since your last promise. @evanpro Since 2013 old accounts cannot be deleted. #identica #pumpio ♲ @evanpro@twitter.com: @miradlo Send me an email at evan at prodromou dot name and I'll take a look.
lnxw48a1: https://github.com/friendica/friendica/issues/8642 #Friendica Someone that is familiar with #Diaspora is writing a new socnet based on #ActivityPub, wishes to change other #Fediverse software to follow Diaspora's model (viewer's server hijacks hashtags so the #hashtag search points to the viewer's home server, not the original poster's home server). The model that has been followed by almost all federated socnets for over a decade is that hashtag search links are inserted by the poster's server and point back there. IMO, a remote server changing the links is sketchy as heck*, but if they added local hashtag links in a separate area outside the post itself, that's acceptable. Or if they followed the #Pump.io idea of keeping hashtags completely separate from the basic server, then an external server (e.g. ragtag\.io) would be called to index and link the tag during the posting process, and searches would be performed based on results from the tag server. Anyway, I can't be bothered logging into Github to comment, but maybe @heluecht and other Friendica devs will see this and take this into consideration. * Remote servers editing the contents of one's posts is about as sketchy as it gets. There are rare occasions where that may be acceptable (i.e., to insert NSFW tags / image hiding on posts from instances where untagged NSFW content originates), but editing content to hijack hashtag search is about as questionable as one could get.
lnxw48a1's status on Monday, 18-May-2020 21:41:39 EDT
https://github.com/friendica/friendica/issues/8642 #Friendica Someone that is familiar with #Diaspora is writing a new socnet based on #ActivityPub, wishes to change other #Fediverse software to follow Diaspora's model (viewer's server hijacks hashtags so the #hashtag search points to the viewer's home server, not the original poster's home server). The model that has been followed by almost all federated socnets for over a decade is that hashtag search links are inserted by the poster's server and point back there. IMO, a remote server changing the links is sketchy as heck*, but if they added local hashtag links in a separate area outside the post itself, that's acceptable. Or if they followed the #Pump.io idea of keeping hashtags completely separate from the basic server, then an external server (e.g. ragtag\.io) would be called to index and link the tag during the posting process, and searches would be performed based on results from the tag server. Anyway, I can't be bothered logging into Github to comment, but maybe @heluecht and other Friendica devs will see this and take this into consideration. * Remote servers editing the contents of one's posts is about as sketchy as it gets. There are rare occasions where that may be acceptable (i.e., to insert NSFW tags / image hiding on posts from instances where untagged NSFW content originates), but editing content to hijack hashtag search is about as questionable as one could get.
ActivityPub objects contain links to Friendica for hashtags and mentions · Issue #8642 · friendica/friendica
lnxw48a1: As with other ‘one main dev’ projects, whenever the main #Pump.io dev gets busy with life, development slows down.
lnxw48a1's status on Monday, 18-May-2020 12:49:36 EDT
As with other ‘one main dev’ projects, whenever the main #Pump.io dev gets busy with life, development slows down.
lnxw48a1: I was on the #Pump.io #Github site yesterday and found a wiki page about servers. Not the usual Pump servers, but servers that provide services that most federated socnets generate from each instance. For example, RagTag\.io was to provide hashtagging for the network. There were statistics hubs, a firehose, a find-your-friends service, and more. The repositories are still there, mostly without being touched for 6-8 years, but the primary service point (such as ofirehose\.com and ragtag\.io are almost universally gone, replaced by domain squatters and the like).
lnxw48a1's status on Monday, 18-May-2020 12:46:06 EDT
I was on the #Pump.io #Github site yesterday and found a wiki page about servers. Not the usual Pump servers, but servers that provide services that most federated socnets generate from each instance. For example, RagTag\.io was to provide hashtagging for the network. There were statistics hubs, a firehose, a find-your-friends service, and more. The repositories are still there, mostly without being touched for 6-8 years, but the primary service point (such as ofirehose\.com and ragtag\.io are almost universally gone, replaced by domain squatters and the like).
strypey: Just tried out the AndStatus app on Android. I successfully added accounts for pump.io and Titter, but adding this Mastodon account failed. I tried adding a Friendica account as a GNU social account, since it supports OStatus and I can't see any other way to do it, but that failed. I don't think I have a GNU social account since the Quitter. sites went down, but I'll have to check and maybe set up a new one for testing purposes. #AndStatus #Android #pumpIO #GNUsocial #Friendica #OStatus
strypey's status on Wednesday, 22-Apr-2020 05:27:56 EDT
Just tried out the AndStatus app on Android. I successfully added accounts for pump.io and Titter, but adding this Mastodon account failed. I tried adding a Friendica account as a GNU social account, since it supports OStatus and I can't see any other way to do it, but that failed. I don't think I have a GNU social account since the Quitter. sites went down, but I'll have to check and maybe set up a new one for testing purposes. #AndStatus #Android #pumpIO #GNUsocial #Friendica #OStatus
lnxw48a1: Alex (main maintainer) makes it official: #Pump.io is dead except security patches https://github.com/pump-io/pump.io/issues/1709
lnxw48a1's status on Friday, 03-Apr-2020 11:41:51 EDT
Alex (main maintainer) makes it official: #Pump.io is dead except security patches https://github.com/pump-io/pump.io/issues/1709
Is this project dead? · Issue #1709 · pump-io/pump.io
lnxw48a1: @dude Hmm. This complicates the plan to add a #Pleroma instance for !FNetworks before we upgrade to !gnusocial 2.0. I'm not really interested in hosting incompatible services (one reason why planned #Diaspora and #Pump.io instances were abandoned).
lnxw48a1's status on Saturday, 19-Oct-2019 12:05:26 EDT
@dude Hmm. This complicates the plan to add a #Pleroma instance for !FNetworks before we upgrade to !gnusocial 2.0. I'm not really interested in hosting incompatible services (one reason why planned #Diaspora and #Pump.io instances were abandoned).
lnxw48a1: I wouldn't say https://identi.ca/ is "dead", it just is not accepting new members and suffers frequent downtime. Without the #Pump.io firehose, it is difficult to tell how many active users are on the Pump network (though certainly a lot less than in the months after #bifurcation).
lnxw48a1's status on Tuesday, 23-Jul-2019 22:29:59 EDT
I wouldn't say https://identi.ca/ is "dead", it just is not accepting new members and suffers frequent downtime. Without the #Pump.io firehose, it is difficult to tell how many active users are on the Pump network (though certainly a lot less than in the months after #bifurcation).
lohang: Me: *Checks news* News: It is just #Pompeo. Not #pumpio
lohang's status on Sunday, 21-Jul-2019 20:18:43 EDT
Me: *Checks news* News: It is just #Pompeo. Not #pumpio
lnxw48a1: @moonman #Pump.IO did have Open Farm Game, which probably was not much of a competitor to Facebook's farm game. It would be a good thing, I think, for fedizens to have something to do other than argue about politics.
lnxw48a1's status on Thursday, 18-Jul-2019 21:28:18 EDT
@moonman #Pump.IO did have Open Farm Game, which probably was not much of a competitor to Facebook's farm game. It would be a good thing, I think, for fedizens to have something to do other than argue about politics.
lnxw48a1: @dragnucs I disagree. Once your federated network survives one severe #bifurcation (the #Pump.io split), you know it can survive others. The #ActivityPub addition is still somewhere in the process, but I doubt that defederating from the #OStstus part of the network would speed it up. @gargron @heluecht
lnxw48a1's status on Sunday, 30-Dec-2018 10:44:40 EST
@dragnucs I disagree. Once your federated network survives one severe #bifurcation (the #Pump.io split), you know it can survive others. The #ActivityPub addition is still somewhere in the process, but I doubt that defederating from the #OStstus part of the network would speed it up. @gargron @heluecht
whistlewright: Ok, I have been out of the loop for a while because life. Does someone have a decent article on the state of the #Fediverse and what works and doesn't work? I don't even know what half the stuff is. #Pleroma? #Mastodon? #Pixelfeed? #Nextcloud? Does any of this work and really federate or is it all just a pipe dream? Is #pumpio still a thing? So many questions just to have a place to kill time.
whistlewright's status on Monday, 11-Jun-2018 20:20:55 EDT
Ok, I have been out of the loop for a while because life. Does someone have a decent article on the state of the #Fediverse and what works and doesn't work? I don't even know what half the stuff is. #Pleroma? #Mastodon? #Pixelfeed? #Nextcloud? Does any of this work and really federate or is it all just a pipe dream? Is #pumpio still a thing? So many questions just to have a place to kill time.
lnxw48a1: Project cancellation announcements for Federati Networks (1) #Node.js projects: I was planning to set up (a) #Pump.io (b) #Hastebin (c) #Etherpad-Lite I decided that for now, the hassle of dealing with multiple Node applications is not worthwhile. Additionally, I still consider Node too poorly understood to be safe on a server shared with anything else.
lnxw48a1's status on Sunday, 27-May-2018 11:53:48 EDT
Project cancellation announcements for Federati Networks (1) #Node.js projects: I was planning to set up (a) #Pump.io (b) #Hastebin (c) #Etherpad-Lite I decided that for now, the hassle of dealing with multiple Node applications is not worthwhile. Additionally, I still consider Node too poorly understood to be safe on a server shared with anything else.
clacke: #pumpio 5.1.1 http://pump.io/blog/2018/05/pump.io-5.1.1-docker-images-and-node-4 In other news, AS2 support will be merged Any Day Now, Evan and Alex have been hard at work for this. At that point we'll have a pump.io 5.2 or 6.0, and full AP support will happen not very soon after that, joining the Fediverse and its long lost cousin once again!
clacke's status on Sunday, 06-May-2018 14:29:58 EDT
#pumpio 5.1.1 http://pump.io/blog/2018/05/pump.io-5.1.1-docker-images-and-node-4 In other news, AS2 support will be merged Any Day Now, Evan and Alex have been hard at work for this. At that point we'll have a pump.io 5.2 or 6.0, and full AP support will happen not very soon after that, joining the Fediverse and its long lost cousin once again!
hikerus: Bin gerde ein bisschen ratlos: Auf meinem self-hosted Server laufen #GnuSocial, #Friendica, #Diaspora und #pump.io. Zwischendurch schaue ich auch in #twister und #FreeNet rein. Noch weitere installieren und kennen lernen? Hmm - irgendwie ist die Motivation etwas weg...
hikerus's status on Tuesday, 24-Apr-2018 11:00:33 EDT
Bin gerde ein bisschen ratlos: Auf meinem self-hosted Server laufen #GnuSocial, #Friendica, #Diaspora und #pump.io. Zwischendurch schaue ich auch in #twister und #FreeNet rein. Noch weitere installieren und kennen lernen? Hmm - irgendwie ist die Motivation etwas weg...
lnxw48a1: @bthall I'm not. #pump.io instance microca\.st's domain was taken over by a squatter / spammer, and I don't use my long-abandoned identi.ca account. Maybe some day soon.
lnxw48a1's status on Saturday, 17-Mar-2018 20:46:32 EDT
@bthall I'm not. #pump.io instance microca\.st's domain was taken over by a squatter / spammer, and I don't use my long-abandoned identi.ca account. Maybe some day soon.
colegota: He visto esto en #pump.io Creo que lo clava. ;) https://quitter.es/url/1529766 https://identi.ca/evanarkisto/note/g4qM9bU7QhmTZG5nWs9KiA
colegota's status on Friday, 23-Feb-2018 05:54:46 EST
He visto esto en #pump.io Creo que lo clava. ;) https://quitter.es/url/1529766 https://identi.ca/evanarkisto/note/g4qM9bU7QhmTZG5nWs9KiA
Cambiame a https://gnusocial.villanos.net/colegota
lnxw48a1: the monthly #pump.io is finished. Logs will be posted soon.
lnxw48a1's status on Friday, 16-Feb-2018 16:35:22 EST
the monthly #pump.io is finished. Logs will be posted soon.
lnxw48a1: @musicman Something else occurred to me. His #pump.io and #gnusocial servers are probably on the same physical box or at least in the same room, so default timeout settings for #NS may be too short for those with servers in widely scattered places.
lnxw48a1's status on Thursday, 01-Feb-2018 06:51:18 EST
@musicman Something else occurred to me. His #pump.io and #gnusocial servers are probably on the same physical box or at least in the same room, so default timeout settings for #NS may be too short for those with servers in widely scattered places.
clacke: @benis @jeff That one was probably from #oggcastplanet, possibly #lobsters, probably not but not entirely impossibly #picolisp. Otherwise I'm on the GS Offtopic, Lounge, Cryptid and Tech/Programming heldscalla matrix channels, #squatconf, #heropunch, #guix, #pump.io and #scuttlebutt. That's more than enough to keep me busy. I think you are not interested to hear which Swedish-speaking Suckerberg groups I'm on.
clacke's status on Wednesday, 17-Jan-2018 08:41:53 EST
@benis @jeff That one was probably from #oggcastplanet, possibly #lobsters, probably not but not entirely impossibly #picolisp. Otherwise I'm on the GS Offtopic, Lounge, Cryptid and Tech/Programming heldscalla matrix channels, #squatconf, #heropunch, #guix, #pump.io and #scuttlebutt. That's more than enough to keep me busy. I think you are not interested to hear which Swedish-speaking Suckerberg groups I'm on.
lnxw48a1: @moonman Were you around for OFG? That was pretty early in #Pump.io's life-cycle.
lnxw48a1's status on Thursday, 28-Dec-2017 23:54:09 EST
@moonman Were you around for OFG? That was pretty early in #Pump.io's life-cycle.
lnxw48a1: @maiyannah I think that was in reference to the fact that proxying #pump.io and #node.js behind the main webserver was "unsupported" ... so multi-IP would be expected if the server also hosted other sites.
lnxw48a1's status on Monday, 04-Dec-2017 00:36:46 EST
@maiyannah I think that was in reference to the fact that proxying #pump.io and #node.js behind the main webserver was "unsupported" ... so multi-IP would be expected if the server also hosted other sites.
lnxw48a1: @ajordan This is progress. It makes it possible to host #Pump.io on a non-exclusive server. I'm glad to see it. @bob @bobjonkman @tekk @infernalturtle
lnxw48a1's status on Sunday, 03-Dec-2017 20:47:19 EST
@ajordan This is progress. It makes it possible to host #Pump.io on a non-exclusive server. I'm glad to see it. @bob @bobjonkman @tekk @infernalturtle
lnxw48a1: @musicman I can think of a reason why #Pump.io may not wish to add a visible version string (yet). Up until the E14N servers collapsed, they were all running outdated versions (and way behind now, over a year later). On the other hand, it makes error reports a lot more helpful. And it makes it easier to see when federation-breaking changes can be switched on. In general, I'm in favor, but I think any pumps still in existence will need to be running the current year's code.
lnxw48a1's status on Sunday, 26-Nov-2017 10:30:22 EST
@musicman I can think of a reason why #Pump.io may not wish to add a visible version string (yet). Up until the E14N servers collapsed, they were all running outdated versions (and way behind now, over a year later). On the other hand, it makes error reports a lot more helpful. And it makes it easier to see when federation-breaking changes can be switched on. In general, I'm in favor, but I think any pumps still in existence will need to be running the current year's code.
lnxw48a1: @bob @bobjonkman There is a new #Pump.io maintainer, who is fairly active. But most of Pump's other issues remain, and are worsened by most instances being out of service for >1 year (microca.st's domain is now held by a squatter).
lnxw48a1's status on Sunday, 19-Nov-2017 16:14:52 EST
@bob @bobjonkman There is a new #Pump.io maintainer, who is fairly active. But most of Pump's other issues remain, and are worsened by most instances being out of service for >1 year (microca.st's domain is now held by a squatter).
lnxw48a1: @tekk @bob @bobjonkman Even today, proxying the #Pump.io Node.JS server behind another web server is considered unsupported, even though I think every non E14N pump does just that.
lnxw48a1's status on Sunday, 19-Nov-2017 16:07:15 EST
@tekk @bob @bobjonkman Even today, proxying the #Pump.io Node.JS server behind another web server is considered unsupported, even though I think every non E14N pump does just that.
tekk: Most people who #selfhost have *a* server. Early on #pumpio demanded that it be the only web server running on your system. The "workaround" for this was "have a dedicated pump.io vm and proxy it to your normal server", although with some config hackery people got it to behave behind nginx.
tekk's status on Sunday, 19-Nov-2017 15:51:48 EST
Most people who #selfhost have *a* server. Early on #pumpio demanded that it be the only web server running on your system. The "workaround" for this was "have a dedicated pump.io vm and proxy it to your normal server", although with some config hackery people got it to behave behind nginx.
bobjonkman: To be fair, the !StatusNet network that Evan was running became unmanageable -- it cost too much to run, and I think Evan was funding most of it himself (although there were/are a number of paying #StatusNet customers). Evan developed #PumpIO to reduce the number of servers needed to run a federated network, and purposely kept the UI to a minimum to encourage federation. Sadly, that didn't work. Porting identi.ca from StatusNet to PumpIO was intended to introduce people to PumpIO as well as reduce Evan's costs. That partly worked; identi.ca is alive and well as a community, although much reduced from its glory days around 2013. But the #bifurcation did spawn a large number of new StatusNet / !GNUsocial instances, so that was a good thing too. But you're right in that PumpIO never gained widespread traction, the proof of which is in its lack of continued development. In that respect #GNUsocial and !OStatus are more successful than PumpIO
bobjonkman's status on Sunday, 19-Nov-2017 15:21:18 EST
To be fair, the !StatusNet network that Evan was running became unmanageable -- it cost too much to run, and I think Evan was funding most of it himself (although there were/are a number of paying #StatusNet customers). Evan developed #PumpIO to reduce the number of servers needed to run a federated network, and purposely kept the UI to a minimum to encourage federation. Sadly, that didn't work. Porting identi.ca from StatusNet to PumpIO was intended to introduce people to PumpIO as well as reduce Evan's costs. That partly worked; identi.ca is alive and well as a community, although much reduced from its glory days around 2013. But the #bifurcation did spawn a large number of new StatusNet / !GNUsocial instances, so that was a good thing too. But you're right in that PumpIO never gained widespread traction, the proof of which is in its lack of continued development. In that respect #GNUsocial and !OStatus are more successful than PumpIO
lnxw48a1: By the way, if your #Pump.io account was hosted on microca\.st, it is likely gone forever (which should be no surprise after the site has been down for more than a year). The domain expired and someone else has it (for sale).
lnxw48a1's status on Tuesday, 14-Nov-2017 23:03:25 EST
By the way, if your #Pump.io account was hosted on microca\.st, it is likely gone forever (which should be no surprise after the site has been down for more than a year). The domain expired and someone else has it (for sale).
lnxw48a1: @internetturtle #Pump.io's new lead dev Strugee is pretty active.
lnxw48a1's status on Monday, 13-Nov-2017 21:28:13 EST
@internetturtle #Pump.io's new lead dev Strugee is pretty active.
lnxw48a1: Distropico was persuaded to join the #Pump.io project as a committer. #Compa will be repurposed as a Foursquare clone.
lnxw48a1's status on Thursday, 02-Nov-2017 00:19:32 EDT
Distropico was persuaded to join the #Pump.io project as a committer. #Compa will be repurposed as a Foursquare clone.
lnxw48a1: #Compa is changing to be more like Foursquare. Distopico has been added to #Pump.io.
lnxw48a1's status on Wednesday, 01-Nov-2017 22:33:46 EDT
#Compa is changing to be more like Foursquare. Distopico has been added to #Pump.io.
lnxw48a1: @kris Were you able to add new contacts on #Pump.io?
lnxw48a1's status on Monday, 09-Oct-2017 20:33:54 EDT
@kris Were you able to add new contacts on #Pump.io?
lnxw48a1: @kris Make that #ActivityPub. #ActivityPump was the original name for #Pump.io, back when EvanP was first trying to develop a lower-resource-use federated social server. (There was never an explanation for the name change, either. I always thought AP was a better name.)
lnxw48a1's status on Sunday, 08-Oct-2017 15:35:45 EDT
@kris Make that #ActivityPub. #ActivityPump was the original name for #Pump.io, back when EvanP was first trying to develop a lower-resource-use federated social server. (There was never an explanation for the name change, either. I always thought AP was a better name.)