kirubakaran's HN Upvotes
on
histre
kirubakaran
Highlights
Fast.ai and Karpathy’s youtube channel. I get some news/tools from Twitter mostly - bleedingedge.ai and @ai__pubTry running stable diffusion locally, tag your images with YOLO, learn how to use transformers library from hugging face or langchain libOne you get hang of it then Kaggle is probably good next step
#idea #histre
curate torrents (without piracy). perhaps i could release a purely decentralized solution, which would be a good learning exercise.
Show More
Highlights
The main thing that seems to be missing, in my experience, is moderation.If someone can manage to make a decentralized forum-like moderation list, then we wouldn't have any use for centralized trackers anymore.I think it could probably be done by using public GPG keys as identities, then keeping changes in a torrent-distributed git repo where user-generated data is saved in GPG signed git commits.Then the only centralization left would be what branch/torrent people introduce to new users
Highlights
Knative has solved most of those pod start time problems since it’s dealing with a similar scenario, unless 0.008s startup time isn’t good enough for you.
We actually initially built this on Kubernetes, twice. The MVP was Kubernetes + nginx where we created pods through the API and used the built-in DNS resolver. The post-MVP attempt fully embraced k8s, with our own CRD and operator pattern. It still exists in another branch of the repo[1]
Our decision to move off came because we realized we cared about a different set of things than Kubernetes did. For example, cold start time generally doesn’t matter that much to a stateless server architecture (k8s’ typical use), but is vital for us because a user is actively waiting on each cold start. Moving away from k8s let us own the scheduling process, which helped us reduce cold start times significantly
Collect and share the web
Get started for free