Loomio
Sat 9 May 2015

DiasporaHQ account - move to a project pod?

JR
Jason Robinson Public Seen by 501

We touched this issue (again, I know it has been up before) on IRC some time ago, happened to agree with @steffenvanbergerem that the project really needs its own pod. The largest reason for this being that posts from the DiasporaHQ account just do not federate out of joindiaspora except randomly. From the last 4 posts, I've received two. I've checked diasp.eu and diaspora-fr.org and neither had received the post either. It's just not something we can live with since we cannot debug problems on joindiaspora.com.

So, what is the current level of support (previous discussions have been rejected I remember) for pushing up a pod.diasporafoundation.org pod OR maybe if jhass wants to give it, diaspora.social .. It would not be an open pod, but would have accounts like HQ and Team.

To be honest, not a huge fan of diasporafoundation.org domain any more since it doesn't look like we're about to set up a legal organization any time soon :( Maybe we could discuss even adopting diaspora.social if @jhass would be ok with that - then we could have hq@diaspora.social and team@diaspora.social and press@diaspora.social - for example.

Anyway, just to kick of discussion about this again - feel very frustrated on the uselessness of the DHQ account right now.

Migration or loss of followers was mentioned last time as a blocker. I don't see it that way - most of the followers never receive the messages now anyway so it's kind of an academic question ;) Once joindiaspora.com updates to 0.5 (Maxwell wants to do it soon, talked with him), we can export the contacts and do a one time "mass follow" on the new pod, and then do a "mass unfollow". This will create a notification to any others who could then hit follow back if they want.

And I'm totally willing to host the pod and pay for it, if lack of volunteers for that is brought up as a problem.

JS

Juan Santiago Sun 10 May 2015

Yes, I think the project needs its own pod, not only for technical reasons, the technician can be fixed, but the development of Diaspora* needs its own identity, I feel great respect for the four people who started with the development of this network and for their first pods, but we must ourselves adults and emancipate and also reinforce the idea of federated network.

DU

[deactivated account] Mon 11 May 2015

Is it ready yet???

Yes, definitely, this should have been done years ago really.

Do you envision the pod running bleeding edge or a stable rls?

DU

[deactivated account] Mon 11 May 2015

Out of interest, when a new person joins jd.com can something be changed so they start sharing with the new official account on the new pod?

Can an auto-follow be cross-pod?

JR

Jason Robinson Mon 11 May 2015

@rich1 haha well considering the level of support yet here, no it is not ready :) I'll create a proposal if no more discussion happens by the weekend.

Do you envision the pod running bleeding edge or a stable rls?

I guess it should run bleeding edge but since it would be registrations closed then it wouldn't matter much to most.

Out of interest, when a new person joins jd.com can something be changed so they start sharing with the new official account on the new pod?

We would just push a new default setting for auto-follow in the next release.

Can an auto-follow be cross-pod?

It already is for everybody else except joindiaspora.com by default ;)

JR

Jason Robinson Mon 11 May 2015

Also, would need @jhass to comment on the domain name :) But I guess we would need at least two proposals, one for setting up the pod and one for the domain..

JS

Juan Santiago Mon 11 May 2015

most disporahq domains are available, .com .org etc.

JH

Jonne Haß Tue 12 May 2015

Well, I kind of would like to run an open pod on it once I have a proper box to run one.

G

goob Tue 12 May 2015

I'd like jd.com to be transformed into a community pod, as most external links to the project are still to that domain. Maxwell seemed interested a while ago in transferring ownership to the core community, any updates on that? Even if Jason or another core member could have admin access, they could help to get the pod functioning better by, e.g. clearing out unused accounts. I think the final transformation would have to wait until pod migration is possible, or there would be a lot of angry people out there! But if it was possible to find a way to do this using jd.com, that would, I think, be the idea situation as it is the domain most associated with the project.

JR

Jason Robinson Tue 12 May 2015

@jhass that is fair and understand totally, it's a cool domain ;)

@goob I don't think joindiaspora.com should ever be a central resource - it was once and that time has gone. Also, maintaining it as a community pod would require not only continuous effort but also money. I assume if Maxwell gives it away, he wont be paying for it :)

So, any support for pod.diasporafoundation.org?

JR

Jason Robinson Tue 12 May 2015

@jhass that is fair and understand totally, it's a cool domain ;)

@goob I don't think joindiaspora.com should ever be a central resource - it was once and that time has gone. Also, maintaining it as a community pod would require not only continuous effort but also money. I assume if Maxwell gives it away, he wont be paying for it :)

So, any support for pod.diasporafoundation.org?

JH

Jonne Haß Tue 12 May 2015

I also have diaspora.software btw

JR

Jason Robinson Tue 12 May 2015

Oh, that is neat :) pod.diaspora.software <3. Then we could redirect diasporafoundation.org to diaspora.software.

F

Flaburgan Tue 12 May 2015

I don't think we should abandon diasporafoundation.org, but this is going out of topic.

About a new pod for diaspora HQ well yeah, why not.
About joindiaspora.com managed by other people, I think that I once read Maxwell saying that if someone wants to help him, he is welcome. That way, the pod would still be owned by Max (and, I guess, paid by him) but maybe administrate more often.

G

goob Tue 12 May 2015

not a huge fan of diasporafoundation.org domain any more since it doesn’t look like we’re about to set up a legal organization any time soon

We have a legal organisation (through FSSN) - we're just not using it. I think the project can certainly make use of the structure they provide until such time as the project sets up its own legal structure.

I think that I once read Maxwell saying that if someone wants to help him, he is welcome.

Jason kindly offered a year or so ago, and I'm pretty sure Maxwell said yes, but then the trail went cold. Jason, did you ever hear back from him?

DS

Dennis Schubert Tue 12 May 2015

Just remember to don't move away from diasporafoundation.org until June, since we've got a valid wildcard certificate for this domain ;)

JR

Jason Robinson Thu 14 May 2015

I think the project can certainly make use of the structure they provide until such time as the project sets up its own legal structure.

When will that be? :) When one tries to talk about it everybody goes silent..

I don't know for sure if moving DiasporaHQ is a good idea or not, but I know using it is useless as long as joindiaspora.com is broken. It's easier to reach diaspora* users by posting to the Diaspora page on Facebook or the account on Twitter than through DiasporaHQ ;)

A

aj Thu 14 May 2015

seems like JD is no longer the place for it so i agree.

F

Flaburgan Thu 14 May 2015

@jasonrobinson maybe we can wait to see if you success to fix joindiaspora? Like, to clean old accounts and old pods... I personally think that there are also limitations inside diaspora* itself, an account with 300.000 contacts will be broken on any diaspora* pod..

JS

Juan Santiago Thu 14 May 2015

@flaburgan

"an account with 300.000 contacts will be broken on any diaspora* pod.."

Also on a pod of only one account?

In that case, we should make a chain?

A Diasporahq acount has a limited number of users, and in athers pods, acounts disporahq1, disporahq2, disoprahq3, also with limited number of followers, and so on?

It may not be very complicated to implement.

F

Flaburgan Thu 14 May 2015

@juansantiago well, we should more certainly optimize diaspora*: diaspora HQ is sending only public post, so only one post is sent to a pod, so this should definitely not take that much power. But we're going out of topic here, we know we need to improve diaspora core.

DU

[deactivated account] Wed 27 May 2015

Any more thoughts on this?

JR

Jason Robinson Thu 28 May 2015

Well. There wasn't much support on moving the account anywhere, so :)

DU

[deactivated account] started a proposal Thu 11 Jun 2015

Move the DiasporaHQ account to a new pod Closed Thu 11 Jun 2015

Outcome
by [deactivated account] Tue 25 Apr 2017

Proposal closed until we know if updating jd.com to v0.5.x.x fixes the federation issues. If not, will re-open the proposal.

Due to incredibly high number of posts which fail to federate out from DiasporaHQ@joindiaspora.com - move the account to new pod on its own domain name (domain name can be confirmed later) and change the "autofollow_on_join_user: 'diasporahq@joindiaspora.com'" value in diaspora.yml.example to match the new account location.

Results
Agree - 4
Abstain - 4
Disagree - 4
Block - 4
4 people have voted (1%)
DU

[deactivated account]
Agree
Thu 11 Jun 2015

This should have been done years ago. Literally.

KAK

Karthikeyan A K
Agree
Thu 11 Jun 2015

JS

Juan Santiago
Agree
Thu 11 Jun 2015

DM

David Morley
Agree
Thu 11 Jun 2015

F

Flaburgan Thu 11 Jun 2015

@rich1 maybe your vote come ~one week to early: looks like @maxwellsalzberg is upgrading joindiaspora.com right now. Let's see if this improves the situation with the diaspora HQ account first before voting.

DU

[deactivated account] Thu 11 Jun 2015

Maybe @maxwellsalzberg is too late - v0.5.0.0 shipped on 3 May and he still hasn't even announced a date for the upgrade yet.

Fla my friend, you know far more about the codebase than me. Do you think v0501 will make any difference to the federation issues of the jd.com pod?

F

Flaburgan Thu 11 Jun 2015

@rich1 yeah, there are some nice improvements about federation in the 0.5.0.0 version, even more in 0.5.1.0 to be released this sunday. + we hope max or maybe @jasonrobinson will clean the inactive accounts on jd, which would probably improve the situation too.

JR

Jason Robinson Thu 11 Jun 2015

@flaburgan I'm not so confident things can be fixed that fast.

I know there are many problems relating to switching the official project account to another pod but in principle I think it should be done. It should have been done a long time ago when the project became not related to joindiaspora. The project account being there is just putting more pressure on jd.com which isn't likely to become magically an ultra fast performance pod just because of updates and cleanup.

And to be honest, people saying "lets wait till we have some organization". I don't think that will ever happen.

I think the priority is to provide an information channel to users and people interested in the project. This information channel needs to be reliable. We can't even edit the profile, aspects or maintain posts/comments on jd. It's just too broken to be a reliable information channel.

JR

Jason Robinson Thu 11 Jun 2015

@rich1 why did you close the proposal?

DU

[deactivated account] Thu 11 Jun 2015

D'oh - sorry @jasonrobinson I closed the proposal while you were typing that post!

Likewise, I don't think the update will fix the jd.com issues either :(

RE:

the priority is to provide an information channel to users and people interested in the project. This information channel needs to be reliable

Agreed - and that's the bottom line too.

JR

Jason Robinson Thu 11 Jun 2015

It's not just federation issues that make DiasporaHQ pretty useless guys..

DU

[deactivated account] started a proposal Thu 11 Jun 2015

Move DiasporaHQ account to a new pod Closed Thu 11 Jun 2015

Move the DiasporaHQ account to a new pod (using pod.diasporafoundation.org) in order to ensure the best possible chance of information being reliably federated and distributed throughout the diaspora* network.

Results
Agree - 4
Abstain - 4
Disagree - 4
Block - 4
4 people have voted (1%)
DU

[deactivated account]
Agree
Thu 11 Jun 2015

I agree for all of the reasons listed in this thread.

DM

David Morley
Agree
Thu 11 Jun 2015

F

Flaburgan
Agree
Thu 11 Jun 2015

I'm fine with pod.diasporafoundation.org but it should be a closed pod with only official accounts.

JS

Juan Santiago
Agree
Thu 11 Jun 2015

JR

Jason Robinson Thu 11 Jun 2015

@rich1 hate to complain but I think the previous proposal was better since it didn't decide on a domain yet.. I'm not sure about diasporafoundation, that domain stuff was what killed the conversation much earlier in this thread.

So if you still feel like editing or starting over, what about just voting first on the "do we set up a pod for official accounts"? :)

DU

[deactivated account] started a proposal Thu 11 Jun 2015

Set up new pod just for official accounts Closed Tue 7 Jul 2015

Outcome
by Jason Robinson Tue 25 Apr 2017

Proposal passed. Only block was resolved.

Set up a new (closed) pod for official accounts and move the existing DiasporaHQ account to the new pod too (pod domain/name to be decided at a later date).

Results
Agree - 14
Abstain - 14
Disagree - 14
Block - 14
15 people have voted (5%)
DU

[deactivated account]
Agree
Thu 11 Jun 2015

Third time lucky lol :)

JS

Juan Santiago
Agree
Thu 11 Jun 2015

F

Flaburgan
Agree
Thu 11 Jun 2015

DM

David Morley
Agree
Thu 11 Jun 2015

JR

Jason Robinson
Agree
Thu 11 Jun 2015

KB

Kamil Boberek
Agree
Sat 13 Jun 2015

A

aj
Agree
Sun 14 Jun 2015

G

goob
Block
Sun 14 Jun 2015

Just a temporary block vote, until it has been established whether or not upgrade to 0.5.x plus blitzing of old accounts will improve jd.com's performance sufficiently.

TR

trekkie@nomorestars.com
Agree
Mon 15 Jun 2015

I agree with the provision that the 0.5.x code stream doesn't fix the issues with the current location.

If it does fix it, don't see a reason to move.

RH

Roland Haeder
Agree
Thu 25 Jun 2015

As I have heard, the joindiaspora pod is overrun and in case of load-balancing it would make totally sense. :-) Sorry for my bad English.

AF

Alexander Finkhäuser
Agree
Fri 26 Jun 2015

T

theradialactive
Agree
Sun 28 Jun 2015

G

goob
Abstain
Sun 28 Jun 2015

Removing my block pending further discussion.

Q

Quetschwalze
Agree
Wed 1 Jul 2015

B

Bady
Agree
Fri 3 Jul 2015

L

lnxwalt
Agree
Fri 3 Jul 2015

JD is already overloaded (as well as its size overcentralizing the network). If we can do something to relieve that a little, I'm in favor.

G

goob Thu 11 Jun 2015

Wouldn't it be better to wait until jd.com has been updated to 0.5.1.0 and had chance to expire those hundreds of thousands of unused accounts, to see if that helps performance and federation enough to make DHQ workable on jd.com?

G

goob Sun 14 Jun 2015

There are very good reasons in my opinion for keep the diaspora* HQ account on joindiaspora.com – for instance, all those billions of web links to that pod from early stories about diaspora* – if the pod's performance can be brought back up to scratch.

Let's wait until Maxwell has had chance to upgrade to 0.5.x and expire all those hundreds of thousands of old accounts, and then see if the performance improves to a level at which the account is useful on that pod. If not, and there remain problems with jd.com's performance, then certainly let's move it.

SVB

Steffen van Bergerem Mon 15 Jun 2015

When we decide that we want to move dhq to a new pod we could still reshare new posts from the old dhq account (for at least some time).

JR

Jason Robinson Mon 15 Jun 2015

@goob

It's very unlikely (IMHO) that jd.com will be magically "cured" at the upgrade to 0.5 - which tbh is still a wip thing to do and could be a month or two away, considering how busy Maxwell and I am (I'm trying to help him here).

After that, the clean-up of accounts will be a thing of probably a year, not some overnight action. And we don't know whether it will help, though Maxwell says it could (which is why I made the maintenance feature).

So, we have one upgrade and one clean-up action - and we don't know for sure whether either of those will actually solve anything. We could do other clean-up, but that will take years, since we don't have action points for large pods like this to clean up (ideas welcome as github issues!).

Consider this also. DiasporaHQ is putting a lot of weight on jd.com. ALL the users of that pod have to suffer because the project wants to use the resources of jd.com. I see this not just as a question of making DiasporaHQ work, but also making jd.com work - and for that actually moving DHQ out might help a bit. I do the promotion of d* on our official FB, Twitter, G+ and Reddit pages + generally do a lot of spamming especially about releases into various open source groups/subredddits/pages etc. Do you know many times I've received replies like "LOL it still doesn't work" from people who when they click the link to the DHQ post, they get a "we're overloaded" message? Lots. While that page looks nice, it's a real killer for any marketing.

Yesterday I decided I'm not going to link to DHQ with any promotion any more. I'll link to the relevant post (if it ever arrives) on my pod which I know can handle the traffic. Now people might just be wondering wtf is iliketoast.net - but ah well, smaller problem - at least they see the post.

I'm more than ever thinking we definitely need to create a project pod for the DHQ account. That would show we eat our own dog food too, which is good for promotion. Of course we already do, but no one outside the project sees this. They won't be able to identify Jonne as a core dev and what pod he runs the latest greatest code on, for example. But when they see an official pod it's like "these guys use their own software".

Remember btw, we voted that a block here is just a strong no. Since this is an important decision, we should prob extend the deadline though.

As Steffen said, it would make sense to reshare posts (federation to DHQ seems to work better than out) from the jd.com account for at least a year or something. Maybe by then we'll have some kind of moved redirect ;)

My only problem with this is the domain. I don't like diasporafoundation.org at all any more. Even though this is going a tad bit off-topic, I'll just rant a bit about that too.

diaspora* is not a social network any more. It stopped being a social network when other social networking servers started implementing the diaspora protocol. At that point we moved to a whole new thing which some people have lovingly called The Federation. Diaspora really is software.

We should not and probably will never have a diaspora* foundation, to me at least that doesn't make sense any more. Diaspora is software. We have excellent software maintainers who maintain that software (<3 to these guys). It would be awesome to have a foundation for federated social networks that play together, ie "The Federation". I know Mike would just announce quickly he's not in but hey who needs his permission. I'd like to be a part of this organization if some other trustworthy, not afraid of legal stuff, highly addicted to social networking (not just federated ones), preferably non-coders would step up (PM plz).

Anyway, to cut a long rant short, I don't think the pod domain, or the project domain, should have anything to do with non-existing foundations. diasporaproject.org would be nice, but since that a.. I mean friendly human owning it isn't responding to anyone and doesn't want to give it up - then it cannot be.

Whatever the domain will be, it would be nice to also change the project home page to the same (without the pod.).

Personal rant off and to work -->

JS

Juan Santiago Mon 15 Jun 2015

@goob

I sincerely believe that although jd.com works perfectly, would be fine one pod to the official accounts.

In the name of decentralization, many people believe that jd.com is an officer or main pod is and good show pods that can be created for specific uses.

F

Flaburgan Mon 15 Jun 2015

ALL the users of that pod have to suffer because the project wants to use the resources of jd.com

I didn't think about that, good point.

Now people might just be wondering wtf is iliketoast.net - but ah well, smaller problem - at least they see the post.

Why don't you link to the post on the official blog?

JR

Jason Robinson Mon 15 Jun 2015

Why don’t you link to the post on the official blog?

In this case, I didn't think a blog post was made - should have checked :( But not every announcement from DHQ ends up in a blog post. And that would be kind of weird, diaspora* being social networking software, not blogging software - so it would make sense to link to the announcements in an official account imho.

G

goob Tue 16 Jun 2015

Jason, thanks for your long and considered reply. There are some interesting points in there that I need to read and think about in more detail. Thanks again.

DU

[deactivated account] Wed 17 Jun 2015

Since this is an important decision, we should prob extend the deadline though.

Thanks to whoever extended it :)

JR

Jason Robinson Sun 28 Jun 2015

@jhass would you be open to discussing diaspora.software for project use, if that was proposed to be adopted as an official domain for the project? We could just with the pod at pod.diaspora.software and go on from there step by step - or just have the pod on that if people want to keep the foundation in the name..

If not, ideas welcome for domains. Two good ones available and not too expensive:

diaspora.network
diaspora.wiki

JH

Jonne Haß Sun 28 Jun 2015

Sure, I happily hand over (control of) diaspora.software to the project.

JR

Jason Robinson Sun 28 Jun 2015

@jhass awesome <3

@goob have you considered your stance as you said you would? Since you are to only one so far opposing, I feel if you would reconsider we could close this earlier and vote on the domain name (for the pod).

As for where to "physically" host the pod - my server at least would be available for use, as one option. I think the whole core team should have admin access to it, wherever it is hosted.

G

goob Sun 28 Jun 2015

Yeh sorry, I haven't had chance to think properly about this. I'd still like to see whether the performance issues with jd.com can be solved first, but if that is going to take in the order of a year, we would probably be better off moving the HQ account.

JR

Jason Robinson Tue 30 Jun 2015

OK thanks @goob if no one objects, I'll close this proposal tomorrow and create a new proposal for the domain of the pod.

G

goob Tue 30 Jun 2015

Is there definitely no hope of jd.com's performance improving within the next three months, then? I would really like to exhaust those possibilities before moving to another pod, and it was on that basis that I removed my block vote. I know a block is only a strong no, so couldn't have prevented that action from taking place, but I do think it's important to know there is no chance of making jd.com working properly before moving the account.

JR

Jason Robinson Sun 5 Jul 2015

Is there definitely no hope of jd.com’s performance improving within the next three months, then?

Well, not looking too good atm. Since 0.5, tag pages are timeouting on jd.com and it looks like sidekiq is falling behind all the time (50K pending jobs ~4 hours ago, now 54K).

I really think we should help jd.com by moving stuff out, not increasing activity there..

I'll create a proposal for the domain tomorrow, been a bit busy last some days.

DS

Dennis Schubert Mon 6 Jul 2015

50K pending jobs ~4 hours ago, now 54K

Are you sure you added workers for the new queues? We added some new queues... ;)

JR

Jason Robinson Tue 7 Jul 2015

@dennisschubert they are receive queue jobs. And I don't have any other access than the Sidekiq admin panel through the UI. I assume these are the jobs Maxwell runs.

It went up to 75K, down to 60K and now back to 71K. Also it seems tags pages are mostly time outing and notifications fail to be delivered (email I guess).

Overall the upgrade has made joindiaspora.com worse for users, it seems.

JR

Jason Robinson started a proposal Tue 7 Jul 2015

Domain for official project pod Closed Tue 28 Jul 2015

What domain should the closed official project diaspora* pod (for official accounts) live on?

YES = pod.diaspora.network
NO = pod.diaspora.wiki
ABSTAIN = pod.diaspora.software
BLOCK = I don't like either of these

diaspora.network or diaspora.wiki will be registered, if still available, after proposal closes. diaspora.software is available for use from Jonne.

Results
Agree - 11
Abstain - 11
Disagree - 11
Block - 11
23 people have voted (8%)
LM

Lukas Matt
Agree
Tue 7 Jul 2015

LM

Lukas Matt
Agree
Tue 7 Jul 2015

we are a network :)

JK

Juho Kunsola
Agree
Tue 7 Jul 2015

It is not a wiki and it is primarily a network

DU

[deactivated account]
Agree
Tue 7 Jul 2015

pod.diaspora.network

JS

Juan Santiago
Agree
Tue 7 Jul 2015

it,s very cler

F

Flaburgan
Block
Tue 7 Jul 2015

I would have go with pod.diasporafoundation.org. We're promoting this domain everywhere for a while I don't want to confuse people and seo with another domain. To deal with the legal structure is another topic which should not interfere here.

KS

Kent Shikama
Agree
Wed 8 Jul 2015

JH

Jonne Haß
Abstain
Fri 10 Jul 2015

diaspora.software is paid already, I have the same concerns with foundation.org as Jason and diaspora.network might suggest a more central role than it actually is.

SVB

Steffen van Bergerem
Abstain
Fri 10 Jul 2015

For me diasporahq is more about the software itself since it is maintained by community members who participate in the software development. diaspora.network would also include friendica and others while the current focus of dhq is diaspora itself.

JR

Jason Robinson
Abstain
Fri 10 Jul 2015

Diaspora is a software project and as such diaspora.software is a very good choice. Plus it is already owned by a core member.

Diaspora is not a network any more, the network also includes redmatrix and friendica.

MM

Michael McKinsey
Abstain
Fri 10 Jul 2015

I think software sounds best as it is clearer that it does not some sort of authoritative role over the network

ST

Sean Tilley
Agree
Fri 10 Jul 2015

Frankly, I'm not totally sold on these alternate TLDs. They all kind of sound sketchy at best. But if I would have to choose, .network sounds the least sketchy of the bunch.

S

SuperTux88
Abstain
Sat 11 Jul 2015

DU

[deactivated account]
Abstain
Sat 11 Jul 2015

Above comments have swayed my thoughts now to favour .software

T

theradialactive
Agree
Sat 11 Jul 2015

TR

trekkie@nomorestars.com
Block
Sun 12 Jul 2015

I wouldn't prefer not another domain and use the diasporafoundation.org

You go there for everything else. Seems logical to use it. But then I'm an old curmudgeon who doesn't like these new fancy domain tlds

S

Sj
Agree
Tue 14 Jul 2015

G

goob
Block
Tue 14 Jul 2015

I'm afraid I'm not keen on any of the options given. Out of the three, .network is the only one which seems to have the right kind of focus for this project.

If we have to move domains, I vote for pod.diasporafoundation.org.

JH

Jakub Hlusička
Block
Thu 23 Jul 2015

pod.diasporafoundation.org

AVB

Andros Villanueva Blanco
Agree
Fri 24 Jul 2015

Creo que es el camino correcto.

M

Milan*
Agree
Sat 25 Jul 2015

BK

Brad Koehn
Agree
Mon 27 Jul 2015

sounds good.

V

ventos
Agree
Mon 27 Jul 2015

R

Ravenbird
Block
Mon 27 Jul 2015

I'm with Flaburgan. Why don't use pod.diasporafoundation.org?