Archives

Categories

Getting Swoosh EVERYWHERE you want to be

To solve the bandwidth problem, Swoosh needs to be everywhere. . . I've included below a post that I made to the webforum a couple weeks ago. . . .


**************************************

Today, Red Swoosh offers great features, cool Javascript API, sweet p2p performance and bandwidth efficiencies, but we're only as good as the number of your users that have our client. Now granted, we have a pretty light, friendly and easy installation, and each of your users only has to go through installation once and voila!, but wouldn't it be nice if Swoosh were everywhere and all of your users could instantly pull from peers the moment you swooshed your links?

One of the best things that Swoosh could do for the development community would be for us to find a way to get Red Swoosh on every desktop PC on the planet.

If the Red Swoosh client is everywhere, then websites and application developers never have to worry whether Swoosh is installed, . . . and never have to worry about how to get each of their users installed. It would be AWESOME, getting instant bandwidth savings across all of your users on day 1, and instant utilization of all of our other tools by all of your users from the start.

So the hundred-million-dollar question:

How do we get Swoosh *everywhere*?

- Product feature enhancements -- make Swoosh cool and desirable by users of media apps on the Net. Users could get interesting features like faster delivery to ALL content swooshed or not, or a cool plug-in to their favorite Podcatching application
- bundle with Firefox or iTunes (doesn't that take lots of money?)
- bundle with other apps (podcatchers, cool niche applications)
- new business models -- Example: website gets free distribution on RS premium product for life for all users that they distribute the client to

What are your guys' ideas?


--chief swoosher

This entry was posted on September 1, 2006 at 11:36 pm and is filed under General. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Comments

noodles and beef says:
September 2nd, 2006 at 12:35 am

…P2P bandwidth sharing is a really good idea, but there just aren’t enough casual-publisher-types to allow wide-spread coverage.

Macromedia’s Flash had similar difficulty achieving wide-spread use-there just weren’t enough games or animations being developed through their platform. The market just needed a bit of…stimulation. Macromedia releases NewGrounds.com, commissioning several animation teams to create new animations and games using their platform. Genius. Flash is installed on almost every internet-capable machine.

Though, it might’ve helped that the installation process for Flash in IE was as easy as viewing an embedded object.

How do you get Swoosh everywhere?
The market is casual web content publishers: teens that podcast, kids that dapple with their parent’s video cameras for YouTUBE, etc… Build a product that they won’t have to think about. Wrap Swoosh up with popular WYSIWYG podcast tools, or make your own PodCasting community ala NewGrounds+MySpace with integrated RedSwoosh P2P bandwidth sharing. Something new, social, viral that people will pick up.

travis says:
September 3rd, 2006 at 4:40 pm

noodles, it’s an interesting idea. . .

we’re looking for somebody with an initative and some killer skills to head something like that up for Swoosh. . .

send me an email at travis AT redswoosh DOT net

Michael says:
October 4th, 2006 at 6:15 am

1. The problem? The key problem for redswoosh is that you need to find a way to get both providers and subscribers to signup in reasonably proportional numbers (aka critical mass). At the same time, providers are unlikely to route their valuable traffic through something potentially unreliable for the sake of saving bandwidth that is continually getting cheaper, and users are unlikely to signup if the end result means simply reducing a provider’s bandwidth bill while at the same time increasing the load on the user’s bandwidth and creating potential user-security issues.
2. The solution? Focus on one side of the equation for now, and make the necessary technology adjustments to allow it to happen. Offering users a plugin that will automatically speed up downloads by detecting geographically-close P2P users might be something worth picking up…especially if the application could work with any link on a page rather than requiring a specially-formatted provider link in order to activate the software.

I like your software, and want to use it in my products…but I can’t do it until you guys reach critical mass!

FirstThought says:
October 28th, 2006 at 8:35 am

I think there are two aspects to the software you are promoting. There is the true P2P global community/cultural component and second, a technology which allows for distributed downloads.

Completely agree with “noodles and beef” on the concept of partnerships with the next big content site or significant content owners (which is what I believe you are doing with game providers etc..).. This helps with the first issue of building the P2P community, ie. get your client out there!!

The though in the back of my mind is how about just considering the second component, ie. distributed downloads. Where does a significant amount of replicated content exist on the internet, my first answer is, internet proxy servers (public, broadband providers, telco’s, corporate, transperant)! How about building them as part of the P2P network. They generally sit at a much fatter part of the internet pipe and have a significantly imbalanced use (ie. they are a net puller of content).

The first though in my mind

Leave a reply