DiasporaHQ account - move to a project pod?
Jason Robinson
Public
Seen by 244
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 [email protected] and [email protected] and [email protected] - 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.
Jason Robinson Thu 28 May 2015 5:05PM
Well. There wasn't much support on moving the account anywhere, so :)
Poll Created Thu 11 Jun 2015 7:58AM
Move the DiasporaHQ account to a new pod Closed Thu 11 Jun 2015 10:03AM
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 [email protected] - move the account to new pod on its own domain name (domain name can be confirmed later) and change the "autofollow_on_join_user: '[email protected]'" value in diaspora.yml.example to match the new account location.
Results
| Results | Option | % of points | Voters | |
|---|---|---|---|---|
|
|
Agree | 100.0% | 4 |
|
| Abstain | 0.0% | 0 | ||
| Disagree | 0.0% | 0 | ||
| Block | 0.0% | 0 | ||
| Undecided | 0% | 260 |
|
4 of 264 people have participated (1%)
Rich
Thu 11 Jun 2015 8:01AM
This should have been done years ago. Literally.
Flaburgan Thu 11 Jun 2015 9:27AM
@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.
Rich Thu 11 Jun 2015 9:37AM
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?
Flaburgan Thu 11 Jun 2015 9:57AM
@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.
Jason Robinson Thu 11 Jun 2015 10:04AM
@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.
Jason Robinson Thu 11 Jun 2015 10:06AM
@rich1 why did you close the proposal?
Rich Thu 11 Jun 2015 10:07AM
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.
Rich · Wed 27 May 2015 5:52PM
Any more thoughts on this?