Difference between revisions of "BarnCamp 2011 Workshop Notes"
m |
m |
||
| Line 7: | Line 7: | ||
=== Why set up this type of blog services? === | === Why set up this type of blog services? === | ||
| − | We heard the story of the Bristol Blogger - a political blogger who had been using a WordPress blog for a long time. They posted a blog that was critical about a person, who then complained to WordPress. WP removed the entire blog. After complaints, the blogs was restored, but the post in question was removed. The Bristol Blogger had no control over their own site, and data was removed from it.<br>We also heard about a Manchester based blogger who posted an item about somebody from Manchester University. WP passed on personal details about the blogger to the university.<br>So, the key questions are: who controls your data? Who knows who you are, and who do they pass that info onto?<br> | + | We heard the story of the Bristol Blogger - a political blogger who had been using a WordPress blog for a long time. They posted a blog that was critical about a person, who then complained to WordPress. WP removed the entire blog. After complaints, the blogs was restored, but the post in question was removed. The Bristol Blogger had no control over their own site, and data was removed from it.<br>We also heard about a Manchester based blogger who posted an item about somebody from Manchester University. WP passed on personal details about the blogger to the university.<br>So, the key questions are: who controls your data? Who knows who you are, and who do they pass that info onto?<br> |
| + | |||
| + | [https://network23.org/ Network 23] used WordPress to set up a non-corporate site that would respect people's anonymity. The approach is to deal with editorial issues on a case by case level - what the hosters want to host. So may issue take down notice - blogger has to fight own corner.<br>Refer to N23 terms & conditions. Editorial decisions - hierarchy & accountable. Not only place for free speech. People can go elsewhere. Is this an argument for lots of providers with different terms & conditions. | ||
| + | |||
| + | === Why WP network instead of separate installs? === | ||
| + | |||
| + | It is possible to set up an individual group on a single WP installation, but they don't keep it up to date.<br>Multi-user option available out of the box to create sub-blogs of main blog. So all blogs are running the same code - means that one update on a plugin will affect all sites using that plugin. Some plugins won't work with this set up (will only work on main blog). | ||
| + | |||
| + | How many sub blogs? Not sure, but lots. | ||
| + | |||
| + | User can Request new plugins.<br> | ||
| + | |||
| + | How it was done<br>N23 were lucky to have one person who had already done similar stuff. Their key tips were:<br> | ||
| + | |||
| + | *Started with small number of plugins | ||
| + | *Get lots of users | ||
| + | *Install new plugins when people want them. | ||
| + | |||
| + | === Features === | ||
| + | |||
| + | Able to import from other blogs (e.g. from an existing site on WordPress.com) - useful for migration to N23. | ||
| + | |||
| + | Can there be different language options - e.g. admin interface in different languages? Seems not out of the box, but plugins may be available. | ||
| + | |||
| + | === Server resources required === | ||
| + | |||
| + | Lots of memory on the server | ||
| + | |||
| + | Lots of disc | ||
| + | |||
| + | === Making a HL site<br> === | ||
| + | |||
| + | 1. Use online form contact N23 asking for blog | ||
| + | |||
| + | 2. Admin fills in new site form. Creates site, emails user.<br>- admin can access the control panel. | ||
| + | |||
| + | 3. Look at plugins ...<br>Anti-spam - WP sites are suseptable to spam. Use wp-spamfree | ||
| + | |||
| + | <br>Limitations<br> | ||
| + | |||
| + | Space for uploaded media | ||
| + | |||
| + | Look at FAQ | ||
| + | |||
| + | <br>Q? Anon posting on archive.org. | ||
| + | |||
| + | Moving from N23? Yes, using export | ||
| + | |||
| + | Issues around domain mapping - https. | ||
| + | |||
| + | SSL certs. | ||
| + | |||
| + | Apache mod - remove IPs and replaces them, e.g. with no luck here copper. | ||
| + | |||
| + | Table within db that logs IP - but takes it from | ||
| + | |||
| + | WP-Piwick (plugin) stats system | ||
| + | |||
| + | |||
| + | |||
| + | <br>Ways forward | ||
| + | |||
| + | Lots of small services, with their own rules?<br><br> | ||
Revision as of 17:48, 11 June 2011
These are the notes from the many different, varied, and sometimes random workshops that took place during BarnCamp 2011
Why & how to set up an non-corporate anonymous blogging hosting service
Why set up this type of blog services?
We heard the story of the Bristol Blogger - a political blogger who had been using a WordPress blog for a long time. They posted a blog that was critical about a person, who then complained to WordPress. WP removed the entire blog. After complaints, the blogs was restored, but the post in question was removed. The Bristol Blogger had no control over their own site, and data was removed from it.
We also heard about a Manchester based blogger who posted an item about somebody from Manchester University. WP passed on personal details about the blogger to the university.
So, the key questions are: who controls your data? Who knows who you are, and who do they pass that info onto?
Network 23 used WordPress to set up a non-corporate site that would respect people's anonymity. The approach is to deal with editorial issues on a case by case level - what the hosters want to host. So may issue take down notice - blogger has to fight own corner.
Refer to N23 terms & conditions. Editorial decisions - hierarchy & accountable. Not only place for free speech. People can go elsewhere. Is this an argument for lots of providers with different terms & conditions.
Why WP network instead of separate installs?
It is possible to set up an individual group on a single WP installation, but they don't keep it up to date.
Multi-user option available out of the box to create sub-blogs of main blog. So all blogs are running the same code - means that one update on a plugin will affect all sites using that plugin. Some plugins won't work with this set up (will only work on main blog).
How many sub blogs? Not sure, but lots.
User can Request new plugins.
How it was done
N23 were lucky to have one person who had already done similar stuff. Their key tips were:
- Started with small number of plugins
- Get lots of users
- Install new plugins when people want them.
Features
Able to import from other blogs (e.g. from an existing site on WordPress.com) - useful for migration to N23.
Can there be different language options - e.g. admin interface in different languages? Seems not out of the box, but plugins may be available.
Server resources required
Lots of memory on the server
Lots of disc
Making a HL site
1. Use online form contact N23 asking for blog
2. Admin fills in new site form. Creates site, emails user.
- admin can access the control panel.
3. Look at plugins ...
Anti-spam - WP sites are suseptable to spam. Use wp-spamfree
Limitations
Space for uploaded media
Look at FAQ
Q? Anon posting on archive.org.
Moving from N23? Yes, using export
Issues around domain mapping - https.
SSL certs.
Apache mod - remove IPs and replaces them, e.g. with no luck here copper.
Table within db that logs IP - but takes it from
WP-Piwick (plugin) stats system
Ways forward
Lots of small services, with their own rules?