Social Geo-Location Is A Weak Medium

Earlier, I was watching an Iron Maiden concert and realized that any decent medium can be used to express a story or culture. Social Geo-location might be able to pass a story, but the majority of the usage I’ve seen, thus far, doesn’t. This is just one of a few issues that make social geo-location weak, there is the issue of user base, barrier to entry, and application of the data.

I feel that the location services aren’t proper for expressing the story. They don’t describe the why and what is happening the majority of the time, and when they do the data is extremely condensed to fit within the minuscule boxes of Twitter or SMS. Twitter is hard enough to express a story through, though you can still manage to get it or a cultural message across in one tweet. Sharing a cultural message through one of these locations is likely even harder, with the exception of religious establishments.

How social can you really be with these applications? These applications all have tiny user bases, even after quite a bit of promotion on large blogs and a period of time. Foursquare, which is one the most publicly discussed ones, only has half-a-million, even after breaking out at SxSW, last year. Compared to Foursquare, few of the other services come close in size comparisons. The problem with low user adoption is that without your friends, how relevant can the product be, which I’ll discuss a little later.

The barrier to entry for nearly all of these services, is that they are limited to internet enabled phones, or smart phones. In fact, only one service of the several that I’ve looked at, had a entry level that wasn’t quite restrictive of it’s base, and it’s none other than Foursquare, with SMS check-in’s, which still appears to be hit or miss. If you’re reducing your initial growth capabilities, immediately, in a social market, you’re damaging your product.

The services use the location data, in their own ways, but I don’t know if they are applying it where it would actually be of value, as an addition of context. If you can take the data from these products and connect it to events and people as they occur, you simplify the enrichment of the story. It’s still pretty easy to just say where the event’s took place, with the addition of maybe 2 dozen key strokes, as I write this at my house.

Another issue is that the product might not be relevant to users, especially, when people begin using them to check in as they leave. If I were to use these services, it would be to let my friends know where I am, so now you have users undermining the principles of your product, way to go. You’re app actually ends up being even more irrelevant than it already is. The likelihood that your friends are even on the service is an anomaly in the first place, unless you live in a metropolitan area(e.g. New York, San Francisco, LA, Portland, Miami, etc.).

I give all the people who work on these applications props, though, because they discovered a great system. They created a user-promotion based advertising system, which you encourage by having deals with various venues to reward the heavy users, and little trophies for reaching little milestones for the rest of the users. They have also brought the idea of geo-location to the fore, which sometime in the future will be used to add context to real stories or cultural messages. So I would like to thank all the people, who work on these apps, for their work, but you guys apparently don’t understand geo-location, it is better served to add context to other mediums, than as an independent social medium.

Splitting the Web Markets

I’ve been looking into the web, trying to figure out what it’s going to look like in a few years. I’m still looking at various scopes, but I decided to analyze some of the more generalized markets that we have right now. You’re not going to find anything new here, just 5 areas of the web we will see changes in, and the coming monetization of the web.

Infrastructure = Hosting & ISP’s

Data Resources = Data

Data Access & Storage Protocols = API’s

Services = Applications that modify the Data through use of API’s to provide a value

Directories = Provide the ability to find what you’re looking for quite rapidly, can be pseudo-static or dynamic.

Each of these different markets can and most likely will be monetized within the coming years, most likely coming from the users themselves. Hosting & ISP’s have already done it. Directories that aren’t fully dynamic can do it with advertising, and even some of the dynamic real-time directories will be able to use the advertising model. The Data & DASP’s will be subsidized, for the most part, by the initial service’s charges, or possibly the service will be subsidized by external developers paying for access to the data, or just the data itself.

The benefits we will see is that our data is more stable, at least in the sense that the company isn’t going to go belly up, services should be better, and there will be more positions, hopefully. We all walked around expecting everything to be free, when we should have been asking how can we help make more services. Maybe the free world was just the accelerant for innovation to get the initial business models developed, promote an open generation, and allow everyone a shot at getting their ideas out there, it’s easier to pick up users, for a simple service, when you’re not charging them after all. The problem that we had with free is that we all became so jaded by it.

Focus on one of these markets and how you can change it. Each one is easily branched into another, you can traverse up or down that list from where you started. Look at Google, they exist in each of these markets. They started with a DASP that collected vast amounts of Data, then used initially used this data to create a Directory Service, along with quite a few other services, one of which is AppEngine which exists to share their infrastructure.

As the web evolves we’ll see these markets split and converge on each other time and time again, we may even see a new general market pop up. Just as an example of the splitting a market look at the services, there are so many sub-markets that exist within it that it would be hard to categorize them. For an example of convergence you just have to look at the various projects being developed to better connect the web, one of the most recent one’s to pop into my radar is Salmon, which is working to pull comments back to the original source and re-disperse them with the source feeds. Time to watch the ebb and flow, and maybe enter one or more of these markets.

Thoughts are Evolutionary: The Idea for Arclings

Do you really want to keep pushing ideas out, but have problems fleshing the concept out fully? Or maybe you just want to express the basis of an idea really quick, get feedback, and iterate. The problem with current systems is it’s hard to keep track of the evolution, if you post a lot of other stuff around it.

Micro-blogging lets you throw the idea out there, but doesn’t allow much room for the idea to evolve, or tracking this evolution.

Blogging in the conventional sense is much too concrete(though I’m doing it right now). I find the preconception of blogging to be you must push out a full thought. Why?

I propose a release quick, release often blogging structure and build arc’s as your story develops, making branching trees using link structures. Let the ideas build over weeks, or months, rather than waiting for one single burst of insight, and fleshing it out on the spot.

I propose using story arcs, along with links to the latest preceding events in the evolution, and trackbacks to the succeeding story events. Though this is possible in the current evolution of blogging systems, it’s complicated. I want an Arcling platform that makes the connection process easy, if not intelligent in managing the tracing of the structure.

A Few Innovative Ideas for Short URL’s

Over the past 6 months or so I’ve seen numerous posts raise flags with the idea of URL Shorteners. Each of these focus on several issues, security issues, non-relative link titles, no pass through for SEO purposes, and the possibility of data loss. Each of the problems, have at least partial solutions, but these solutions are still not effective enough. Here are some of the modifications that I plan on working to enhance the service.

Pretty URL’s – Security & Relative Titles

Making the short URL as human-readable as possible is a plus, however, with the shorteners on the market, they are quite hard to get because every user’s URL is an ID that can only be linked to only once by the service. My solution to this is to embed user data within the link, this abstraction reduces actual URL location to 1-3 characters(b62 range, 62 – 238,328), and you can store the User data in between 4-6 characters(b62, 14,776,336 – 56,800,235,584) at the end. This means the minimal length required for a link is 5 and the maximum is 9. The benefits of applying the User encoding is that it provides the ability to parse the users links, along with any meta-data associated with the link, such as a secondary access to the url, via a user specific vanity title, e.g. http://examp.le/URLxUser = http://examp.le/SteveJ/apple and http://examp.le/XbUser = http://examp.le/LarryP/apple. The User encoding also allows the linking system, to be used as a quick account review if there is any suspicion of malware or spyware being sent by a specific source. One requirement of using the User encoding, is that you define the length that the User data takes up and where it is located. I feel that 5 characters(~1 Billion unique id’s) is optimal at this point in time, and that placing this in the very end of the string is slightly simpler to parse, but that’s just user preference. However, at no point can you change either of these choices without destroying the entire system of links that have been spread over the internet, so you must choose wisely before you begin.

Multiple-Links – More Data, Less Space

Allowing users to batch related content, reduces the total length per link to 22/n to 24/n, where n equals # of links. Applying link specification to the API will extend the length, but also make large batches more usable for sharing data, (e.g. http://examp.le/XbUser?link=1,3). Next topic of discussion for this is how to handle statistics, because regular statistics become a bit blurred by having the ability to access multiple links at the same time. The most accurate collection is only the inbound links to the page, outbound is much more complicated, as it is multiple-permutations on exit paths. The best that you can do is calculate clicks for links, and measure selection for the Open All button by counting all active links. One benefit to the multiple link structure is that it encourages users to become link curators, this provides plenty of data for machine learning, as well as providing associations that aren’t easily discernible to machines, such as what the user likes. It also makes the system an active aggregation center for real-time data. An example of a multi-link(Safari 4 has issues and will open windows instead of tabs) http://lnkr.hiphs.com/socialme

Data Storage – Open Access, Uptime, and Redundant Stores

After, stories such as Ma.gnol.ia’s data loss, Cli.gs hacking, and various services shutting their doors, link rot becomes a very big concern. So I’ve looked into various solutions and one that sticks out is based on work by Directeur for use in federated real-time systems, Socnodes, and the Oruboros & Lamaean Hydra problems that he had to solve. His solution to the Oruboros was using Atom Feeds UID’s with service title to allow the systems to check against themselves. The usefulness of the Socnode layout is you can store and update remote databases with your data, creating a remote redundant store, but also n-ary accessible domains. Assuming you use separate data storage sites, DNS’s, and build otherwise independent systems that operate with the same data in parallel.

There will be a point that URL’s aren’t going to be nearly as important and I see this as a step to reaching it. These steps toward ease of access, safely securing the data, through redundancy, encoding and embedded data, and review systems, and the ability to collect related and relevant data are steps in the right direction.

The Social Web: Defining Real-World Social Factors

I noticed this a while back, while watching FFundercats, as they discussed the possible loss of the service, with founder Paul Buchheit. They also discussed why Friendfeed captured the audience it did and why most of the users hate/dislike Facebook. It’s the content and community that exists on each, and what value you receive from them. I ended up breaking the real-life social experience into 3 fields, to try and explain this.


Introduction

Commonality
A shared interest in similar items, friends, or favorite places to hang out or eat. It should be easily distinguishable to find a similarity to begin with as your mutual friend introduces you or you end up at the same location at the same time. You may both go to a place to enjoy a hobby you both share, and make a connection from that.

Mutual Experience
You have both being through an incident or event in which you share similar experiences, this could fall under commonality, but it is something that isn’t common enough that you would normally share with a stranger. It could be your profession, a disease that has affected your life, or going to an exclusive event. It is a personal connection that randomly comes out and creates an initial connection.

Notable Interaction
This is the kind that is often used in movies, but occurs quite often in life also, the cliche in films is when someone drops there books and gets assistance from someone. It’s just an accident that creates an opening for introductions. In real life this could be any unplanned event where people share some information about each other, whether it be a car accident, being stuck in an airport due to a delay, or any accident that causes people to offer assistance.

Acquaintance

Re-occurrence
The event that any of the aspects of the Introductory Field reoccurs often enough that you begin to know each other on a more personal level, than you would on a one-off meeting.

Mutual Shared Personal Knowledge
The information that most people don’t want you to have if they don’t know you very well, their birthday, their relationship status, where they’re from. It’s the most basic of info that provides accessibility to each other and also a little detail about one’s current state of affairs.

Caring
The use of Personal Knowledge to express yourself to the person. You can wish them a happy birthday, with out it being to awkward, or provide condolences when they lose something/someone very dear to them. It is the ability to express without being perceived as fake that you are willing to be there for the person in the moments they need support.

Friendship

Deep Interaction
The point in which you can discuss things that matter to you, that you might not share with people you don’t know very well. Discussions which involve personal knowledge to be gathered that isn’t public information. It is the ability to trust the other person with more personal information.

Experience
The effect of Deep Interaction is that you are begin to know more about the person. You have inside jokes, can pass on interests, and know how to change their mood for the positive or negative. The insight that comes with being a friend allows you to interact more fluidly with the other person.

Ease of Access
The ability to start a conversation with a person relatively simply, you make time for each other to have a discussion. It can also be, likely is, the provision of multiple channels to reach the person for such discussions. Having such ubiquity helps further and accelerate, the relationship.

Catalysts

Real-Time Discussion
By now we should all understand what this means, but I will clear the meaning up for those that don’t know. Real-time discussions are fluid interactions that happen rapidly enough, within a short period of time, that they can be seen as a seamless conversation.

Randomness
The spark that can ignite a friendship. It is the driving force of introductions and fosters connections. You see someone grasping something that you like as well, you have an accident, you trip. It is the key to mutual experiences, and notable interactions. It also keeps everything interesting, you may come across something new, at any time.

Currently, I haven’t found an online service that offers all of these qualities, but the top few have hit some sweet spots that make it much easier to manage socialization on all levels. Below I posted a chart of what factors Friendfeed, Facebook, and Twitter have become useful for. And I’m not saying that they don’t have ways to do all of this, it’s just not simple, if it’s not simple to manage the social factors, it’s useless.

Factor Chart

The Social Web: At Home, At The Bar, And On The Street

We’re constantly seeing comparisons made between Facebook, Friendfeed, Twitter, and various other networks, sometimes these comparisons are valid. The reasons to use these different services collectively, is because the environments are different. These environmental factors describe the type of interaction people use and receive from the service.

Continue reading

The Hole In FriendFeed’s File Sharing Strategy

Disclaimer: What I’m about to go into while simple it is an unethical practice. You may very well end up violating FriendFeed’s TOS or possibly the Digital Millenium Copyright Act (DMCA)

Today, the folks at FriendFeed unveiled a new addition to their service, file sharing. Though they say that they have only supported a few file types at this time, they don’t offer any video support and you can only share up to 3 .mp3’s within a 24 hour period. The only other current restriction appears to be that you have an undisclosed cap on how much you can share, this is also set on a revolving 24 hour period.

However, as soon as I found out I instantly though of file type obfuscation, in which you pass a file off as a different type. This allows you to share any type of media across the service, including video, and allowing you to beat the “.mp3” quota.

In order to slip through FriendFeed’s monitoring you just have to select the file and renameĀ  it from “FileName.xxx”,(Note: “.xxx” could be a “.mp3”, “.mp4”, “.avi”, or any other file type) to “FileName.pdf”. Upload the “.pdf” to FriendFeed, and leave a note for others to change it back into the correct file type, once they download it on their side.