Blogging for DiasporaFoundation.org
We have a blog built into the project site, but only one entry at the moment.
I'm of the mentality that there's actually quite a bit going on in Diaspora development on a day-to-day basis: new features, code improvements, design improvements, new volunteers, and new tools that support Diaspora.
Would it be useful to start blogging about these things regularly?
What better blogging platform for diaspora if not d* itself.
I think there's too much non-project communication on that account to make the recommended way for press etc. to subscribe to. I'd rather consider rendering a filtered list of the diaspora* HQ items as the blog.
Jonne++, I think a filtered view of the profile (only own posts, maybe only posts with a certain hashtag in it) would be easier as representative information source for the project.
Jonne++
Let's use the blog properly and frequently rather than abandoning yet another project resource. Also agree re non-project stuff shared from DHQ account, a filter is a good idea.
I was very much for the blog when we had that discussion, so I'd rather not see it replaced. I think we can feature posts from the DiasporaHQ account on the blog more often, though.
I disagree with a simple redirect. Would like to see a filtered view of DHQ posts on the blog list for example and maybe replace that with a redirect ones diaspora is able to provide the filters we need.
Jonne++
Not the same social profile and blog, Diaspora* needs both
I would think the more appropriate proposal is 'someone start blogging' vs 'delete it because no one does'.
I like the current setup with the blog being more "official" posts and the HQ account being a combo of official and personal.
Let's use the blog properly and frequently rather than abandoning yet another project resource
Give me a dollar for every time someone has said "lets make the blog more active" and I'd be loaded ;)
It's easy to say let's do something but since the blog has appeared we as a project have constantly struggled to write anything on it and the project just looks very inactive for people browsing in.
In marketing, activity is a good thing, not something to feel ashamed of.
To add to the above: I acknowledge that I've been worse than useless re communicating for the project in recent weeks, so my comment is not a criticism of anyone else.
I think we discussed some time ago about getting filtered content from DHQ added to the Planet. I don't think that ever happened, although Dennis got the Planet ready for content. I like the idea of appropriately filtered content going on to the blog.
Yeah, the Planet is there, fully loaded, fully functional. I've asked for contents multiple times but unfortunately there simply are not enough blogs about diaspora out there.
Using a filtered atom view of all DHQ posts is an idea. Although I'd rather have the filtered posts as a list on our blog itself rather than just redirecting to a unfiltered profile.
I can almost smell headlines like "Official diaspora statement: Snowden should use diaspora!"
There are people involved here who are so afraid of speaking, to not hurt anyone or say anything wrong or accidentally give the wrong impression to someone, that if those people were the only voice of the project, everybody, not just most, but everybody, would think the project is dead.
Also, I wonder what people felt if the official Wordpress blog was hosted on Google Blogger, for example ;)
I think using D* itself to promote D* is something that makes sense. If the tool is not perfect yet, it would be a good motivation to improve it, and help adress the issues bloggers may encounter.
As far as I understand, the major concern is about the status of posts which are not always official, and about a filter which would be needed. Why not use a second account then, an official one which would display only the kind of things one would find on the blog? An account such as OfficialBlog@diaspora.software?
Jason, please would you refrain from making personal comments about people with whose position you disagree. It's really not helpful.
Jason, please would you refrain from making personal comments about people with whose position you disagree.
Not personal comments, just true observations, just like the pokes from Dennis :)
And there is nothing personal relating to this proposal - it is a proposal to imho give better communication to people who are interested in diaspora and to also use our own platform for things we want the users to use it for. I can imagine people who think about doing blogging with their diaspora account and then seeing that the project uses a custom built Rails app?
I would think the more appropriate proposal is 'someone start blogging' vs 'delete it because no one does'.
I think that would be voting between;
- Show the project is not very active
- Show the project is dead
Doesn't sound like a very useful proposal ;)
I think that would be voting between;
- Show the project is not very active
- Show the project is dead
Releasing a software update every six weeks sounds fairly active to me...
Releasing a software update every six weeks sounds fairly active to me…
Assuming you blog about it.........
Speaking about release announcements - any reason why they are not posted out from the official accounts, but instead they are posted out from personal accounts?
Also, @jpope , what did you mean by this?
the HQ account being a combo of official and personal.
any reason why they are not posted out from the official accounts
I do not have access to that account.
I do not have access to that account.
If that is the only reason, maybe ask? I don't even mind that developers post release announcements. I just find it conflicts with the stance here on everything having to be so offfiiiiicial that it hurts.
Yes, we should definitely improve the way accounts work for bloggers. Maintaining a separate blogging app for our own blog isn't going to make that happen :)
Personally I'd like something like "promoting" own posts and then having a subroute something like
/u/username/promotedto show a stream of those. Or, subroutes for tags and then just use a certain tag. Dirty though.