201–210 of 453 posts
I had a small discussion about this idea[1] and I believe that it is worthwhile: Make private key based authentication useful for logging in to websites. I don't have the chops but introducing private key based auth as an extra can be very worthwhile for some users. So start there and improve the UI until your grandmother can use it. I believe the biggest hurdle will be private key management. The advantage of using…
A usability test of mobile apps delivered to consumers through ad space on free mobile games. You create a "use quest" of your mobile app. One or more screenshots of your application with a stated goal - e.g. invite a friend on a social app. You present the user the home screen and he has to find where in your app he can invite his friends. You record all clicks, and time and etc until he finds it. This test is serve…
A programming language equivalence site that helps you transition from one language to another. I mean it does not have to be perfect because full equivalence don't exist for many languages but just how you would do similar things.
A browser plugin that lets me highlight text on a web page. I can view other user's highlights on that same webpage, and see my highlights again when I revisit the web page weeks later.
Venmo Receipt bill splitter: Mobile app that analyzes a picture of a receipt using tesseract or something similar and allows the user to charge Venmo friends for certain items on the receipt. I would pay for this because then I wouldn't have to create a Venmo payment for each user.
Friend of mine was working on this. Don't know if they are still active or if/when they launch. http://pennapps2014s.challengepost.com/submissions/20858-div...
Startup idea: WiFi hardware that attaches to street lights (for power) and forms a UK-wide mesh network to rival the telcos.
I would love to see a UK Meshnet take off - however activity behind projects doesn't seem to be anywhere near the level of places like Seattle etc. which is a shame. Would there be any issues with regards to attaching these devices to street lights? Who owns that infrastructure - the councils?
EDIT: I made my sentences, make sense.
A subscription service for open source projects. As a company I would pay you monthly and get access to bug and features development for all the open source dependencies that I am using. The more I pay the more things I can get done in a month. If a feature is too big for my budget I can accumulate month to month value on a ticket or get other companies to participate.
This sounds interesting, but doesn't make much sense. Do you mind explaining a bit more?
Now in practice, software is never a done deal. You have bugs. Platforms evolve and you need to adapt the software to it. New features might be added. This is all things you might want to see happen in the future. A subscription service could be a way to participate in the process indirectly. Obviously things need to be balanced as to not corrupt the projects in question.
There are already actors in the place like RedHat and Canonical or product companies like MongoDB but they are focused on their platforms and usually sell "support". As a customer I have a big and changing variety of open source project upon on I depend and negotiating contracts with each of those is time consuming. I would rather pay a fixed amount and have access to a body of experts and direct (part of) their work on projects they own or not. If I scale my subscription up I get more throughput.
A lot of details are conveniently left open to keep the narrative simple and idealistic :)
1) An API framework with an ORM of sorts around the existing graph dbs ( it could be Gremlin based ).
This would allow queries on levels of nodes ( tutorials -> { python | ruby } -> { django | flask } , etc. Another dimension would be { beginner | intermediate | hard }. An important search dimension might be the popularity of the curator (submitter), the upvoters and downvoters, etc. The API would allow RESTful retrieval of nodes, and based on permissions granted to the user allow operations such as voting, modification, creation and deletion. Wikipedia like data could be public domain, but the API itself could be self-hosted on private servers allowing for enterprises to have their own internal wiki of sorts.
Licensing should allow extension of the API if needed for premium revenue models that might allow users to create 'n' relationships on a server that is a kind of bookmarks, can keep private graphs, clones/forks of existing graphs/sub-graphs with annotations, etc. Or contributors may contribute code to extend features on the open source platform as well.
2) A web/mobile UI that would leverage this API and create the UX around searching, for example, a) cross-indexing wikipedia and storing as graphs and allow different search algorithms to be built. b) a knowledge graph of maths ( similar to the ones at khan academy ) and linking in the URLs / videos based on dimensions such as target age, content length, language, pre-requisites, etc.