Problem statement: We should be able to comment & annotate long-form media at specific points in time on its timeline as it is increasingly becoming the preferred medium.
- The idea
- A unique interface
- Challenges in the current web2 world
- How Headjack's paradigm fosters innovation
Why not just show a histogram of where most of the comments are and provide a resizable window as an additional widget on the timeline (in addition to the progress cursor) which can filter comments & annotations based on the range and display the threads below Reddit-style with sorting & filtration options? Here's a screenshot of precisely that (ignore the colors & bad style):
The ultimate audio/video player can offer a lot more than just a comment histogram - it has the potential to be a vibrant social experience:
- 1-click repositioning & resizing of the filter window to timestamp ranges for different topics plotted as horizontal bars (already done & visible in the screenshot)
- sharing links to specific ranges - as clips, but without losing the context
- many channels re-upload clips from longer videos - this should instead be a simple "retweet" of the original material with a range (window) as a parameter
- different types of comments: annotations, questions, personal (private) notes
- search field for within the comments that are in the current filter window
- crowdsourced annotations (tagging resources/events/concepts/entities)
- plotting/toggling different types of histograms (not just comment density):
- plotting different types of reactions
- where other users spend most of their time
- where the user has already played the episode
- comments that have more than X upvotes or up/down ratio
- where the most controversy or facts requiring a crowdsourced check are
- highlighting comments that match the current search filter/query/regex
Here's an older video showcasing this UI (can't resize the window with the mouse yet).
This is nothing like SoundCloud where tiny overlapping rectangles with profile pictures are rendered on the timeline that you can just hover with the cursor to see the comment nor like YouTube where you can write a timestamp (
hh:mm:ss) in a comment which becomes a clickable link that fast-forwards the player - fighting it out with the other 20 000 comments in the single linear vertically scrollable section of a 3 hour long podcast and hoping to be noticed - both are horribly insufficient and unusable. For both of them comments are just an afterthought - it is extremely hard to discuss specific parts of long-form media & for good localized signal to actually surface & be noticed.
How would this work as a web2 company?
- For it to provide value it would need many users commenting on the same video or otherwise there will be no histogram and the whole interface will be pointless. It needs a network effect.
- Discoverability is hard - it would require that users actively share links to it on other platforms.
- What if YouTube/Spotify cut it off & disallows embedding their players & using the APIs?
- Unclear if it should try to be its own platform or just a (browser) plugin to other platforms:
- The platform way is more ambitious but requires a ton more work & vertical integration: direct messages, a social graph, notifications, a feed & recommendation systems, etc. Would it need to compete with YouTube & Spotify at some point? The likely outcome.
- The plugin way is a much more limited experience. How would users share links to comments & timeline ranges to others that don't have the plugin installed? How will users be notified for comments & replies? You'd be completely beholden to the platforms.
Contrast that to a web built around Headjack:
- The amount of work for this UI would be minimal - reusing components already present:
- Identity & single sign-on, DMs, notifications, progress bars, preferences & connections will all be handled by IDMs.
- The heavy lifting (processing & indexing all broadcasted events, perhaps moderation & even ad serving) will be handled by infrastructure services which will charge the application just the right amount for the sets of API calls & indexes that it needs - pay-as-you-go. There will be different competing infrastructure providers and applications will be able to migrate to the one with the best service or it may even utilize multiple ones at the same time - offering users the choice which indexes & filters to use.
- The costs & team required to implement this UI will be minimal and focus would be on delivering value to users. The barrier to entry would be lower and better UX & functionality would be unlocked - many more niche needs could be addressed.
- Application discoverability - the moment someone with a following posts a comment through it that comment would immediately be visible to their audience on applications like Twitter and the URI for the comment will contain the name of the application that was used for its generation - serving as application attribution & advertisement of the alternative application. No need for influencers to explicitly share
"hey! check out this platform where I made a comment and make sure to follow me there"to their audience - it'll be automatic & implicit.
- No risk of platforms cutting access to their APIs to third-party apps & changing their ToS because in this ecosystem everything is a third-party app around unified identity and data is no longer host-certified - addressing is data-centric. There are no MOATs & lock-in - everyone focuses on their niche and competes on competency & offering the best possible service.