HNHacker News
TopNewBestAskShowJobs

vitriolum

24 karma · joined November 5, 2018

submissionscomments
vitriolum··on Show HN: Zero cost abstractions in web development
Thanks! I guess an example would be really cool, give the amount of FE devs who already use React.
vitriolum··on Show HN: Zero cost abstractions in web development
That's very interesting. I have pretty much all my components in React. How can you use React / jsx with constexpr?
vitriolum··on Show HN: Quantleaf – A virtual assistant for web browsing
That is cool. But what do you mean with "based on a machine learning based programming language"?
vitriolum··on Show HN: Vitriol – distributed, serverless publishing platform
Exactly. It's not a community, it's more a tool for publishing content that other people consciously decide to follow. The point being that this content can't be shut down by a central organization, but will disappear if nobody cares about it.
vitriolum··on Show HN: Vitriol – distributed, serverless publishing platform
They're stored as HTML, because of the WYSIWYG nature of the editor. I guess Markdown was the other obvious choice, but editing MD is not so immediate on mobile.
vitriolum··on Show HN: Vitriol – distributed, serverless publishing platform
It comes from "Visita Interiora Terrae Rectificando Invenies Occultum Lapidem", an alchemical motto. No reference to hate intended.
vitriolum··on Show HN: Vitriol – distributed, serverless publishing platform
You can download the code from here: https://gitlab.com/vitriolum/vitriol-web and serve it from whenever you want, even localhost.
vitriolum··on Show HN: Vitriol – distributed, serverless publishing platform
More like Medium, but distributed.
vitriolum··on Show HN: Vitriol – distributed, serverless publishing platform
You can download the code from here: https://gitlab.com/vitriolum/vitriol-web and serve it from whenever you want, even localhost.
vitriolum··on Show HN: Vitriol – distributed, serverless publishing platform
You can download the code from here: https://gitlab.com/vitriolum/vitriol-web and serve it from whenever you want, even localhost.
vitriolum··on Show HN: Vitriol – distributed, serverless publishing platform
Sorry, IPFS bootstrappers are still a bit unstable. Should work now.
vitriolum··on Show HN: Vitriol – distributed, serverless publishing platform
IPFS bootstrappers out there are still a bit unstable. Sorry about that - please retry.
vitriolum··on Show HN: Vitriol – distributed, serverless publishing platform
Visita Interiora Terrae Rectificando Invenies Occultum Lapidem
vitriolum··on Show HN: Vitriol – a distributed, serverless web publishing platform
Thanks! I hope it will evolve and become something useful.
vitriolum··on Show HN: Vitriol – a distributed, serverless web publishing platform
Luckily it isn't any of the two!
vitriolum··on Show HN: Vitriol – a distributed, serverless web publishing platform
Yep, two bootstrappers were timing out, as explained here: https://news.ycombinator.com/item?id=18385587

Thanks for checking the site out!

vitriolum··on Show HN: Vitriol – a distributed, serverless web publishing platform
Sorry for the 43 seconds of your time, two bootstrappers are timing out and that slows down everything. Lesson learned, I will fix the app.

Regarding JavaScript: I don't think there's a good way of doing distributed web docs with HTML only. Very sorry about that.

vitriolum··on Show HN: Vitriol – a distributed, serverless web publishing platform
Thanks!
vitriolum··on Show HN: Vitriol – a distributed, serverless web publishing platform
So, the article is coming slowly or not coming at all because two of the four bootstrappers are timing out and, if you're unlucky enough to hit one of them, it might take minutes to replicate the article content. Bug has been reported to the js-ipfs guys and a pull request has been merged: https://github.com/ipfs/js-ipfs/pull/1693

That was instructive and I'm glad the experience has resulted in people getting interested, questions being asked and bugs being fixed. Sorry if it didn't work perfectly, distributed stuff is hard. I don't understand the flagging but hey, HN will be HN, I guess :)

I will fix the issue in the next days and will keep on developing Vitriol. Obviously any help is appreciated. Thanks to everyone for your comments!

vitriolum··on Show HN: Vitriol – a distributed, serverless web publishing platform
It is. I'm using OrbitDb, so the data structures in the ipfs node are not the ones you'd expect. Also, it needs to load at least three nodes to get to the article - that's a necessary trade off to have user metadata and user feeds. If it wasn't for the bootstrappers timing out it would have worked almost instantly. That's cool, bug has been reported.
vitriolum··on Show HN: Vitriol – a distributed, serverless web publishing platform
Yep, by extension it now means "hatred", in certain contexts. I'm aware of it, but on the other hand I like the alchemical connections of the name. BTW, I view this project as a tool that anyone could use to publish content in a distributed way. There arw no political or social intentions behind it.
vitriolum··on Show HN: Vitriol – a distributed, serverless web publishing platform
That's strange... Could you please show a screenshot?
vitriolum··on Show HN: Vitriol – a distributed, serverless web publishing platform
About the intro article not coming up

Sometimes the bootstrapping server seem to be overwhelmed. I suspect HN's "hug of death" could be possibly responsible. This will be resolved when js-ipfs implements DHT and relay:

> Please read this: DHT (automatic content discovery) and Circuit Relay (pierce through NATs and dial between any node in the network) are two fundamental pieces that are not finalized yet. There are multiple applications that can be built without these two services but nevertheless they are fundamental to get that magic IPFS experience. If you want to track progress or contribute, please follow:

DHT: https://github.com/ipfs/js-ipfs/pull/856 Relay: https://github.com/ipfs/js-ipfs/pull/1063

This stuff is alpha at this point, and sometimes there are still fires to extinguish. Sorry about the inconvenience, I suggest to try again later :(