CHINERROR - 2048:Declaration of InsertQuery::execute() should be compatible with Query::execute($db, $target, $query = NULL), /home/erikbigelow/get6d.com/app/models/Repo.php, 231
CHINERROR - 2048:Declaration of FindQuery::execute() should be compatible with Query::execute($db, $target, $query = NULL), /home/erikbigelow/get6d.com/app/models/Repo.php, 284
CHINERROR - 2048:Declaration of FindQueryWithLimit::execute() should be compatible with Query::execute($db, $target, $query = NULL), /home/erikbigelow/get6d.com/app/models/Repo.php, 321
CHINERROR - 2048:Declaration of CountQuery::execute() should be compatible with Query::execute($db, $target, $query = NULL), /home/erikbigelow/get6d.com/app/models/Repo.php, 356
CHINERROR - 2048:Declaration of save_object::execute() should be compatible with Repo::execute($query, $obj = NULL), /home/erikbigelow/get6d.com/app/models/Repo.php, 372
CHINERROR - 2048:Declaration of delete_object::execute() should be compatible with Repo::execute($query, $obj = NULL), /home/erikbigelow/get6d.com/app/models/Repo.php, 383
CHINERROR - 2048:Declaration of find_count_by::execute() should be compatible with Repo::execute($query, $obj = NULL), /home/erikbigelow/get6d.com/app/models/Repo.php, 391
CHINERROR - 2048:Declaration of find_by_with_limit::execute() should be compatible with Repo::execute($query, $obj = NULL), /home/erikbigelow/get6d.com/app/models/Repo.php, 399
CHINERROR - 2048:Declaration of find_one_by::execute() should be compatible with Repo::execute($query, $obj = NULL), /home/erikbigelow/get6d.com/app/models/Repo.php, 408
CHINERROR - 2048:Declaration of find_by::execute() should be compatible with Repo::execute($query, $obj = NULL), /home/erikbigelow/get6d.com/app/models/Repo.php, 416
CHINERROR - 2:Creating default object from empty value, /home/erikbigelow/get6d.com/app/resources/IndexResource.php, 12
CHINERROR - 2:Creating default object from empty value, /home/erikbigelow/get6d.com/app/app.php, 980
CHINERROR - 2:Creating default object from empty value, /home/erikbigelow/get6d.com/app/app.php, 980
CHINERROR - 2:Creating default object from empty value, /home/erikbigelow/get6d.com/app/app.php, 980
CHINERROR - 2:Creating default object from empty value, /home/erikbigelow/get6d.com/app/app.php, 980
CHINERROR - 2:Creating default object from empty value, /home/erikbigelow/get6d.com/app/app.php, 980
CHINERROR - 2:Cannot modify header information - headers already sent by (output started at /home/erikbigelow/get6d.com/app/models/Repo.php:231), /home/erikbigelow/get6d.com/app/app.php, 506
CHINERROR - 2:Cannot modify header information - headers already sent by (output started at /home/erikbigelow/get6d.com/app/models/Repo.php:231), /home/erikbigelow/get6d.com/app/app.php, 565
6d, Own your content.

6d, Own your content.

Visitor

Own your content

You want to share your thoughts, ideas, opinions, photos, and videos. Social networks are not private enough and email is restrictive.

You want to socialize and interact online, but some of that should be public, while the other very private.

You should own your content and have a reasonable level of control over it. That's the goal of 6d.

6d is an online identity building application. Its purpose is to allow you to centralize your online life, photos, thoughts, posts, etc, but still share them with friends, colleagues, and/or the world.

We're working on 6d. There's just 2 of us and we're tackling challenging problems. You'll find us online at joeyguerra.com and erikbigelow.com. Share something with us. And, feel free to join our mailing list, or even contribute. We're more than willing to take on help.

Don't Want Your Private Data to Leak? Jailbreak Your iPhone

Just another reason why we're building 6d. Depending on how you look at it, your smartphone is either egregiously violating your privacy or just trying to improve your user experience in a not-so-transparent way. Either way, it turns out, some apps are leaking personal data, like your address book. The controversy erupted when a hacker discovered that mobile social network Path was uploading users' entire address books to their servers. As many have pointed out, Path isn't alone. Twitter does it too. Our own Jon Mitchell points out that these kinds of privacy issues may just be the cost of using a free app. Still, not everybody... http://www.readwriteweb.com/archives/dont_want_your_private_data_to_leak_jailbreak_your_iphone.php

Hell Yeah! Response to Stevey's Google Platforms Rant

Erik sent me Stevey's Google Platforms Rant repost on news.ycombinator.com Subject: I'm glad you get this and that's how you designed 6d. My short gut response was, "well of course", and I was about to hit send, but something compelled me to reafirm why I had that gut response. Here's my reply to the message, after Erik's suggestion to post it.

It's exactly how 6d is designed. 6d is a platform. Blog, Address Book, Media Manager, etc., they are all apps built with the platform. As a matter of fact, I've taken the idea of a platform even further by mimicking and staying close to the design decisions of the HTTP protocol and the web. Every resource is uniquely identifiable and can stand alone, meaning you can call any resource by itself. You don't have to make a GET call to addressbook before you make a POST call to it. It's stateless just like HTTP, which makes it scalable. It's revolutionary to design a web app like this because I have yet to meet someone who thinks it can be done. The ones i have spoken with about this still believe that you have to build a separate admin interface because you can't "mix" the two. But that just tells me that they don't get it. They don't see the app as a platform first.

After reading this to make sure I didn't misspell anything or use grammar that, to my knowledge, is incorrect, I didn't like where the last statement stopped because what I mean is that the app is the platform. And everything else is built with it (or on top of it, depending on your preference). I purposefully chose to design the app as a RESTful application. It's not just an acronym to me. It's a design, an architecture, a philosophy, and constraints. There's so much more to building a RESTful application than just pretty URLs and JSON. You're constrained by the HTTP methods and the idea that everything is a resource that the eventual design is simple, stateless and flexible. Just think about this, the same URL that you used to request this post, represented as HTML, can be modified by adding ".json" to the end of it to get it represented as JSON instead. Think how powerful that becomes when you want to make a web app that makes AJAX requests? It uses the same URLs as the web site does but with different file types (JSON, XML, HTML, etc.). Come on! That's cool!