gleb-arestov

I use likes as bookmarks ("likes" used to call "favorites"). There are people who make things, research, stat/vis and tweet about it.

Here is few examples from my likes: https://twitter.com/TodePond/status/1593969648042663936 https://twitter.com/Mappletons/status/1538801464327426050 https://twitter.com/WilliamChyr/status/1592924106802204673 https://twitter.com/AdamMGrant/status/1584938446870573057 https://twitter.com/PuzzlingPlaces/status/143347521840055501... https://twitter.com/guycalledfrank/status/157193248187559117... https://twitter.com/dragonman225/status/1472998315805777920 https://twitter.com/anastasiaopara/status/156067389257403596... https://twitter.com/yiliu_shenburke/status/15366958009353707... https://twitter.com/NathieVR/status/1588988665564647427

In case you are concerned about twitter stability: I'm making tool to backup your likes/bookmarks https://news.ycombinator.com/item?id=33722663

I want to build a browser that captures everything I saw on the internet, allows me to search it, run graph algorithms (like PageRank). Improves navigation (by showing trails as tree instead of tabs). Heavily offline focused (Backend only for updates, maybe for analytics).

Difference with rewind.ai: linkkraft does not have funding, i'm solo, no apps & image/video/audio recognition. Focus on web, trails, research and using web copies, selections/highlights as part of your notes & whiteboards. Preserving all possible graphs.

My inspirations: https://pages.gseis.ucla.edu/faculty/bates/berrypicking.html, https://beepb00p.xyz/promnesia.html, Jeff Raskin (Global Search, Zoom UI) https://linkkraft.com/notes/backstory

I've built a prototype with trails tree & HTML snapshoting. For each my step even inside SPA linkkraft creates HTML snapshot. https://arestov.github.io/linkkraft-notes/comparing/linkkraf... https://arestov.github.io/linkkraft-notes/trails-tree-plus-o...

Across similar software ("too many tabs" solvers, snapshoters) combination of trails tree & snapshots that reinforces is unique in linkkraft.

To make snapshot it takes current state of DOM, current state of styles (to capture CSSinJS stuff), take resources like font/images from network storage (Chrome Dev Tools protocol) and saves it as HTML on disk.

I've been developing created frontend in-memory graph DB / state manager for 1) replication 2) incremental sync 3) fast rendering (without VDOM/react). Used in https://seesu.me & https://meetsidekick.com.

So, I have in memory db in main process of electron that send chunks to render process with replica. And to LevelDB to persist graph.

From user perspective, I also want to have a copy of all my bookmarks (Cause things disappear from internet and things are slow in internet). As special wish: twitter likes/bookmarks (because I use intensively for inspiration from other makers and Twitter is especially slow & unavailable for scoped search).

There are changes in twitter HQ, that looks reasonable to speedup ability to make backup for twitter likes/bookmarks.

https://youtu.be/yTpysdSM9WQ

I have 3 tech tasks for that: 1. Scan/scroll likes pages (actually it would be better to inject code in twitter page to make direct requests to API) 2. Fetch page HTML snapshot. I'm thinking to not fetch page from start, but instead reuse SPA. Something like push to history API, so without full reload I'll get renderer page and comments triggered to load. 3. Speedup resources fetching a) run everything as soon as possible (not when everything is ready) b) use key/value ( url+etag) cache for hash. Which is used to dedup images, fonts, styles.

For me it's not to escape twitter, but to speed up interaction and discover even more things on twitter

I've just looked into Mighty. It has delays for hover css effects & scrolling. Also it has "Debug > Enable H264 encoding" option. So Mighty streams video.

I think replicating DOM & sending diffs instead of video should 1) saves resources on encoding for server 2) saves decoding on client 3) send much lower data 4) feels much better since instant scrolling/hover (something like https://www.rrweb.io/)

I'm indie/solo making Linkkraft browser (to make a living from it). Browser to be effective researcher & collector. It visualizes your steps as tree and makes html snapshot for your each step (even steps in SPAs like twitter). https://arestov.github.io/linkkraft-notes/comparing/linkkraf... https://arestov.github.io/linkkraft-notes/trails-tree-plus-o...

As side effect of snapshots you can confidently unload documents & save CPU/memory.

Looking forward to grow that snapshotting part into DOM streaming. So you can run "browser server" on your own PC, while having laptop fast & cool. With almost 0 delays and without worrying about privacy.

1. You may find interesting https://beamapp.co/. Browser + hypertext note-taking tool (webkit based)

2. I was first engineer at https://meetsidekick.com you may find it interesting too. (as engineer with 14 years of experience in this area ready tell you about best way to architect js app in isolated environments like main/render process of electron, background/view pages in chrome extensions)

3. > I am a big fan of relatively-small websites, personal blogs, and any website that is free of the usual bloat. I'm indie/solo making linkkraft browser (to make a living from it). To let myself observe intensive web in a non-intensive way. It could be useful for someone who make decisions (and money) from processing a lot of information from mass of tabs. (product managers, hr head hunters?)

Linkkraft visualizes your steps as tree and auto-makes html snapshot for your each step. So, you can pause your research confidently (or part of it to free CPU/memory) and restore full context even offline. (Ping me if this would make you effective)

linkkraft tree vs chrome tabs https://arestov.github.io/linkkraft-notes/comparing/linkkraf...

offline snapshots for each step in twitter SPA https://arestov.github.io/linkkraft-notes/trails-tree-plus-o...

I think it's related by sharing desire to say "... it seems extremely overpriced" (as well as any tool that solves a problem that does not cause you pain)

Would you be amazed by the fact that someone pays that for https://roamresearch.com and https://reflect.app https://twitter.com/maccaw/status/1552697245933387776?

1. Chrome store policy (1 feature - 1 extension) 2. Chrome extension sandbox (a lot would still be possible, but hard) 3. Don't want to be trapped in Google platform (you can find a lot of stories of blocked extensions)

But, I'm thinking about making syncing extension that will allow you to open sites from linkkraft in chrome

Yes, I do consider option: lifetime + 1 year updates

I'm not making a living yet, but I'm (as indie/solo hacker) building app (electron based) to make a living.

Linkkraft is an offline-first browser that helps you process large amount of tabs when you're trying to extract useful pieces from them.

Problem known as tab clutter/ tab overload.

How does linkkraft help?

1. It saves (locally) history as a graph where your movements interconnected. New movement is new entry. Linkraft visualizes the graph as a tree instead of tabs.

2. Linkkraft creates snapshot of page state for each step (DOM/text/styles/fonts, removes js). That works for usual pages and SPA (like twitter)

There is GC for such snapshots and limitations. So, you don't have to worry about removing not necessary snapshots.

Tree & snapshots complement each other. You don't have to deal with finding html snapshot in your downloads. Snapshots are integrated in the trails tree. When you open snapshot, you will get all context.

Currently, I'm researching for product market fit and for first 10 paying customers. Going to ask $15 per month for that.

(Eventually it will be a tool for hypertext collecting, note-taking, thinking)

https://arestov.github.io/linkkraft-notes/trails-tree-plus-o... https://arestov.github.io/linkkraft-notes/trails-tree-plus-o...