Monday, September 28, 2009
Android application Ideas
Server Monitor
Block Callers
Bulk Mails/SMS
Command lines for all
Pipes - similar to automator
Card Reader
Building COntact from orkut
Switch on vibrator while driving
Random number generator
Anagram solver
Game based on Hyd Central;s logo
orkut contact's sync
Billiards
Scheduled SMS/Email
Hangman
STD Codes - console
Coconuts
Calculator like Sravani's phone
Free Mind Client
Block Callers
Bulk Mails/SMS
Command lines for all
Pipes - similar to automator
Card Reader
Building COntact from orkut
Switch on vibrator while driving
Random number generator
Anagram solver
Game based on Hyd Central;s logo
orkut contact's sync
Billiards
Scheduled SMS/Email
Hangman
STD Codes - console
Coconuts
Calculator like Sravani's phone
Free Mind Client
The Acoustic Fingerprinting based Music Manager
I use the iTunes quite much because it helps me organize the music nicely and because Winamp is not available for Mac OS X.
But most of the current players have the following problems:
1. Songs are duplicated.
2. If songs are relocated all your albums and tags are gone for a toss.
So, the basic principle I am planning to have is Accoustic Fingerprinting [http://en.wikipedia.org/wiki/Acoustic_fingerprint] as the core.
The moment a file is added into the system it would generate an id for this which will be used as the primary key for everything like play lists.
The same concept can be extended further to provide downloading of songs if law permits.
The SDK for audio fingerprinting is available at: http://musicbrainz.org/doc/libmusicbrainz
The UI can be written using Mozilla's UI components as these are easy to use and app would work across all plateforms.
But most of the current players have the following problems:
1. Songs are duplicated.
2. If songs are relocated all your albums and tags are gone for a toss.
So, the basic principle I am planning to have is Accoustic Fingerprinting [http://en.wikipedia.org/wiki/Acoustic_fingerprint] as the core.
The moment a file is added into the system it would generate an id for this which will be used as the primary key for everything like play lists.
The same concept can be extended further to provide downloading of songs if law permits.
The SDK for audio fingerprinting is available at: http://musicbrainz.org/doc/libmusicbrainz
The UI can be written using Mozilla's UI components as these are easy to use and app would work across all plateforms.
A web based and offline keepass manager
It should be compatible with all the devices and should have the capability to use gears to save the data locally too.
Can be done with google appengine.
Can be done with google appengine.
Sunday, September 30, 2007
P2P Web
What if you could just host your site from your laptop?
You just have to register your name and thats it. You don't have to buy any server space or public IP.
You got the difference between current web and this idea?
The basic thing you will need is:
1. An Apache Kind of server
2. A P2P plugin to Apache
3. A P2P plugin to firefox
Or
a single application combining all three.
What are the benefits?
1. Dont have to buy a server space or Public IP
Since the content will be served directly from your drive, you dont have to run around buying a server space and uploading the content.
2. If you have to share the files with nearby friends (in your office, school), it will be faster because it will be using the Peer-to-Peer network.
3. The supply increases with demand.
Since every person who is downloading a file becomes supplier of the file, any file which is in demand will be faster as opposite to the current system where most of the companies will fail to handle the load.
4. Copyright crap will not bother
Since no one knows the actual identity of a person, no one can sue you just for sharing some lovely song with your friend.
How?
If you havent looked at eMule, have a look.
She first downloads a plugin for her browser. Now, opens up a website called "p2p://poople/". It opens up the home page (it might be a list of files) of poople. Now, she clicks on a links and it starts downloading it from all the sources available. The similar sources are decided based on the hash (signature) of the file.
Now, this file which she is downloading (or downloaded) can also be served to other people.
Thats it!
Challenges:
1. Firefox might not suport p2p so, we might have to write a separate browser having the same rendering engine as firefox so that the whole presentation can be done using same technologies (HTML/CSS/Javascript)
2. The firewall might be a big problem.
This can be handles using the same mechanism as skype is handling.
Your comments are welcome!
~Alpha0
You may say I'm a dreamer
But I'm not the only one
I hope someday you'll join us
And the world will be as one
You just have to register your name and thats it. You don't have to buy any server space or public IP.
You got the difference between current web and this idea?
The basic thing you will need is:
1. An Apache Kind of server
2. A P2P plugin to Apache
3. A P2P plugin to firefox
Or
a single application combining all three.
What are the benefits?
1. Dont have to buy a server space or Public IP
Since the content will be served directly from your drive, you dont have to run around buying a server space and uploading the content.
2. If you have to share the files with nearby friends (in your office, school), it will be faster because it will be using the Peer-to-Peer network.
3. The supply increases with demand.
Since every person who is downloading a file becomes supplier of the file, any file which is in demand will be faster as opposite to the current system where most of the companies will fail to handle the load.
4. Copyright crap will not bother
Since no one knows the actual identity of a person, no one can sue you just for sharing some lovely song with your friend.
How?
If you havent looked at eMule, have a look.
She first downloads a plugin for her browser. Now, opens up a website called "p2p://poople/". It opens up the home page (it might be a list of files) of poople. Now, she clicks on a links and it starts downloading it from all the sources available. The similar sources are decided based on the hash (signature) of the file.
Now, this file which she is downloading (or downloaded) can also be served to other people.
Thats it!
Challenges:
1. Firefox might not suport p2p so, we might have to write a separate browser having the same rendering engine as firefox so that the whole presentation can be done using same technologies (HTML/CSS/Javascript)
2. The firewall might be a big problem.
This can be handles using the same mechanism as skype is handling.
Your comments are welcome!
~Alpha0
You may say I'm a dreamer
But I'm not the only one
I hope someday you'll join us
And the world will be as one
Subscribe to:
Posts (Atom)
Posts
