shameless plug but that's exactly what we're building at Aide (https://aide.app), I would love to chat and see how we can potentially help if this is something you're interesting in learning more about or deploying!
would love to learn more about how you're using Freshdesk and the types of queries you're responding to! I'm building a customer support app that uses openAI's GPT3 to generate automated responses and it's been working great so far!
The holy grail [https://beepb00p.xyz/pkm-search.html#future] of this really resonated with me and fully mirrors what I've been thinking about the past few months. In my observations, it's input capture, information organization, and subsequent retrieval:
Information Capture:
Input Capture - You’re going to have all-encompassing tracking and recording of all activity, but want configurable privacy on the extent to which you want your daily conversations and observations of external things you encounter and are exposed to. Capturing input needs to be holistic and incorporate all properties of encounters and new information.
Potential sources of input:
Vision — point of view recording, see snapchat spectacles, etc as primitive examples.
Audio (voice notes and multi-party conversations) - voice calls, video, etc. and other forms of audio transmission where there is more than a single party in the interaction.
Digital interactions
You will need to keep track of web pages you visit at what times
Conversations you see on Twitter, etc.
Properties and cues must be extrapolated from the information that is captured on input, in the case of audio, transcriptions are sufficient for transcription and retrieval purposes, however since video is a visual medium, it includes significantly more properties that need to be accounted for.
The aim here is to identify sufficient data points (cues) that are subsequently represented in such a way that they are easy to search across things you have encountered but only seem to recall a certain property or cue from. This is because of the fact that human beings tend to remember things in fragments, for instance, you might remember a certain color on a page that you visited within the last 6 months and nothing else.
So long as you are capturing sufficient input and actions then you should be able to go back to any given point in time. How and where are you going to store this information? Storing everything is going to be a large amount of data. The essence of the information and context must be preserved. If you want to wind back to an arbitrary position in time with the original context intact, you want to retain as much as you can in the most efficient manner possible, so determining which data points to retain is essential. (Once the content structure has been figured out, this will be viable).
Examples of Primary Cues:
Time - humans generally keep track of things in a linear time-based fashion.
Color - invokes emotion and is memorable.
Physical Location - the efficiency of information retrieval is highly influenced by the location at which it is originally synthesized, encountered, and stored.
Keywords - the default conventional mode. Can and should be extracted from video/imagery and audio.
Imagery - search for images based on their contents and ambience.
Potential Secondary Cue — Music - see historical associated input and actions while certain music was played.
(What else?)
Meta Cues — Subjects - Automated tagging of keywords/encountered content.
Any combination of these queries is possible, but ultimately the killer feature is the ability to backtrack through time to find a certain piece of information that is made available thanks to the always-on recorded nature of your interactions with the physical and digital worlds combined.
Knowing what to store, and how, + displaying it needs to be worked on further.
You really need to let us try it out without having to sign up. Imagine how many users that think "oh, yet another img -> html/css tool, I wonder how questionably it works" and then get discouraged by having to take a chance on something they have no idea how well/if it works.
Interesting research, in my opinion, this been long coming as the next phase in the evolution of computing and society in general. It's how tech is going change the world to the point of 24/7 always-on connectivity; once the tools, applications, and entire ecosystem is created with more consideration to the human element of the system.
We're actually applying to YC's Summer 2016 batch with a fully automated application deployment process to accommodate for developers, by shifting focus to deployment considerations that have not been eliminated.
I'm based in Saudi Arabia, and considering the deserted climate and environment, there are literally no persistent water sources (aside from a few select wells that are over-exploited by bottled water manufacturers).
After having a look and reading your interview with marketingstartups[1], it is quite an interesting idea.
It strikes me as an evolved incarnation of Buzzfeed[2] in that the entirety of its content is user-generated, whereas this wasn't the case with Buzzfeed until recently, and even now, I believe user submissions are subject to moderation.
I don't think you should give up yet. I wouldn't. I would start by simplifying the design (sure, it looks nice, but it feels over-ornamented), defining stricter guidelines for posting (e.g. encourage "Top/Best X" type posts in lieu of general free-form lists, and figure out other ways to start driving traffic to it.
I wish you guys the very best and again, don't give up yet.
PS: Please get in touch if you'd like to talk more.
Hi Josh. I'm actually working on a book that is intended to provide you with the basic principles and how to actually build applications, which is something I've personally struggled with, considering the language-centricity of the majority of tutorials out there.
It's far from done, however, email me (email in profile) and I'd be happy to send you a draft.
Should've probably clarified that on the website, it's a for-fun-and-interest project.
The standard disclaimers apply, your email won't be sold into slavery or used for anything bad other than a weekly newsletter or something of the sort (aligned with the expectations you had when you signed up).
Good observation. I suppose that there's this expectation that one must achieve success first before a viable story is created.
I think that we, as a community, need to change that. As personally, the stories, & anecdotes that I've benefitted from the most were mostly shared by entrepreneurs still in the trenches--in the process of building their startups.
Plus to be fair, I haven't quite gotten anything "going" yet.
I want to hear your story on how you built your startup.
I'm working on a startup myself, and would like to learn & share lessons from various entrepreneurs on their venture experiences. I'm trying to get my startup off the ground, plus a full time job, so it's a difficult journey ahead.
I figured I'd take all the stories and put them up somewhere, so I created http://buildingof.com , which focuses on sharing an inside look at the toil and hard work that goes into creating a startup. At this point, I'm interested in talking with founders that have interesting stories to share and help everyone learn a thing or two along the way.
"That leaves us with the riddle that every software developer faces at some point: how best to make a UI simple enough to be intuitive for a consumer who wants a solid, fast browser that just works, and yet is customizable and extensible so that power users can add the features they want?"
You don't. Taking both user groups into consideration and weighing them equally assumes that they have the same bearing on the usage of your product. Once it reaches mass market, the tinkerers (occasionally referred to as the early adopters or evangelists) are no longer the largest nor the most profitable segment of your user-base.
Therefore, you can theoretically afford to disregard them--however, in practice, this has implications that can prove disastrous. For instance, they could seek out an alternative and start the disruptive cycle all over again, increasing its appeal and reducing yours, which propagates and ultimately ruins your perception, though this can probably be avoided.
That's is an interesting proposition. Especially considering that hosting is commoditized. Annotations and providing insights is the real value proposition in this case, so it might make more sense to offer that as a discrete service.