Download “AWE 0.3.5 Demo Video”

The background music is from the Into Infinity project, a remix by Anthony Valedez

Wanted to post an update to the first post made on October 3rd, 2011 here on this list, thanks to for the prior feedback. Many of the previous plans have been changed, and now entirely exists, for the most part, in the WordPress admin interface.

WordPress Plugin Directory:
http://wordpress.org/extend/plugins/awe/

Updates for version 0.1 to 0.3.5, from latest to oldest:

• added link to demo video
• php-cli nolonger required to retrieve posts
• added buttons to reader for more options
• use same sanitizer fetch_feed for adding sources …
• php cli fix for differing hosting setups
• fix for widget styles
• files for reblog button
• retrieve updates when adding a source  …
• streamlined subscription to websites
• changed to use custom taxonomy instead …
• fix so that multiple wpcron tasks are not scheduled
• prevent the feed reader from running simultaneously
• add missing screenshot
• removed message about template directory
• moved to use default wordpress theme  …
• added error reporting …
• removed avatars for feeds …
• fix for control chars breaking fetch_feed
• fix for duplicate posts in reader
• fix for other xml content types …
• updated description and screenshots
• moved pending/reader to admin area
• removed cache, fixed login redirect error …
• cache directory uses ABSPATH and fix for slug validation
• added cli, repost, and sources for promoting other blog posts
• added repost post_type …
• initial urls and templates …
• fixed routing interface dropdowns

SVN:
http://plugins.svn.wordpress.org/awe/trunk/

Mailing List:
http://www.freelists.org/list/awe

Thanks,
Braydon Fuller

Summary of previous discussion and problems raised with solutions implemented for each of them:

> Problem #1. Search engines and Google not taking to it kindly because it would spam their indexes.

I’ve made a post type now called “update” for all external posts that are being read into the blog. These posts when viewed have “noindex,nofollow” in the header of the their html to not be indexed at Google and others. In addition these posts do not have yet another permalink, the permalink remains the same as the original. In feeds it will link to the original, and on archive and pages on a website they will link to the original. They are copied to be a convenience, and made more accessible.

> Problem #2: There were concerns about “cross-posts” and how it could be abused from exact duplicates of sites with a different theme.

There could be malicious copies made, this currently has not been addressed with current development but is part of the next. If a problem were to be discovered, the malicious IP could be blocked. For more security, a move towards fully encrypted and authenticated feed connections could be made so that only those who you intent to share with get the information. Currently read posts are the status “pending”, as a partial solution to this issue.

> Problem #3. Auto-generated posts leading to drop of participation.

I’ve address this by making all read posts default to status “pending”, and you can go through your reader and “approve” posts and then those are shared and made available for others to view. They go back into a feed, they permalink and guid remains the same, to make a feed that is a mix of other feeds. These approved posts then are also made available to view on your site, and can be searched (though search isn’t implemented yet).

> Problem #4. Issue with comments getting lost between the two separate copies.

Commenting on a “update” post is disabled, to comment on the post it’s necessary to return to the original.

> Problem #5: Copies taking attention away from the original.

There isn’t a “single” view of “update” posts, and the permalink remains and goes to the original.

> Problem #6: JavaScript front-end would create more work, and would be easier by doing plain old html first.

I’ve written the front-end as plain old html, with only a small part of JavaScript that is necessary for approving posts.

> Problem #7. Potential problem with planning on bundling with WordPress, as the core team plans to unbundle Akismet and move towards a featured plugin model.

Plans of bundling along side WordPress, as a separate WordPress distribution, “package” or as part of the core have been taken out. Continuing work under the impression of being a plugin standalone.

Best,
Braydon Fuller

http://braydon.com/

Posted on the WP-Hackers Mailinglist | View Original

You can get it at the AWE – WordPress Plugins page. Subscribe to the mailing list at http://www.freelists.org/list/awe, and donate to support the project.

I have been working on a free software solution to social networking. Many projects are focused on starting from scratch, such as; Freedom Box, StatusNet, Diaspora, and Libre.fm. My approach is different because I am planning on building upon what is currently already at the heart of social media, WordPress, and just fixing one problem — those pesky share buttons everywhere. I have just completed PHASE 1 of the project, and would like to make this the first public release, which does not include all the required features.

In the same way that people will post links of WordPress posts to Social Media websites, the goal of this is to automatically cross-post to a community of websites for promotional purposes and is a distributed method for online marketing campaigns. This will not require a visitor to leave to visit the post, since it is copied verbatim, and does not require users to be either a member of a network or not a member. This will serve as two-way posting making it possible for a dialog between separate websites and community organization. I am terming it “networked media” to be distinguished from “social media”.

Websites are built in the millions for publishing articles, videos, music and linking these to Social Media websites for promotion. My goal is to build new networked media websites that bring together a community of individuals based upon topics of interest; opening the opportunity for verticals and topic based networked media websites as opposed to Social Media differentiated by differences of software.

That is the goal. This is the future of online marketing. Now, here is what I have made. I have started with a method to define new URLS and templates, and am currently working on the aggregation portion. Here are the links to the resources for the plugin:

WordPress Plugin Directory:
http://wordpress.org/extend/plugins/awe/

SVN:
http://plugins.svn.wordpress.org/awe/trunk/

Project Management ( Documentation / Tickets / Git ):
http://code.braydon.com/p/awe/

Here are the phases of the project I have been planning:

1. URLS/Templates:

* Editing URLS
* Managing Menus
* Editing Templates
* Feed reader for synchronization

2. JavaScript Templates:

* JavaScript URL routing
* JavaScript Templates
* NoScript accessibility

3. Admin Interface:

* Unified front-end/back-end interface
* JavaScript admin that is extensible

4. Complete WordPress Distribution:

* Packaging the plugin as a part of WordPress
* Clean API for our JavaScript applications
* OpenID for network to network authentication and privacy

5. AWE Plugins:

* Write extensions to the core of AWE to add new post types
including: video, sound, gallery, events and shop.

6. Web Service:

* Dedicated web host for users that don’t want to run it on their
own hardware.
* Sign-up and payment settings.

For those that I have previously contacted about URL routing, this is the plugin I was mentioning. I am now looking to work in collaboration because this project can not succeed without the support of a few people working in synchronization. So let’s get going!

Sincerely,
Braydon Fuller
http://braydon.com

Posted on the WP-Hackers mailing list. Read Discussion (21)