About a thousand lines of code re-written from NodeJS/Jest tests to Deno:
https://gitlab.com/rysiekpl/libresilient/-/merge_requests/19/diffs

About 1/5th towards the milestone:
https://gitlab.com/rysiekpl/libresilient/-/milestones/12

Rewriting all tests for Deno will mean I am able to completely remove NodeJS stuff from #LibResilient. Which I am very excited about!

#LibResilient got more #NLnet funding, and so there are new milestones!
https://resilient.is/blog/more-funding-new-milestones/

> Good news: NLnet Foundation decided to extend their small grant for LibResilient! That grant funded bulk of the work over the last year and a half. It will now continue to do so for the next year or so.

#LibResilient documentation is now more usable
https://resilient.is/blog/better-exposed-documentation/

It took me a good while but finally LibResilient's documentation (including that of its plugins) is available in one place:
https://resilient.is/docs/

🎉

There's an index, the whole thing is nicely browseable, and it's all a nice static site, because of course it is. :blobcatcoffee:

I'm hoping this will make it easier for people to engage with the project and maybe deploy it on their websites. 🤞

#WebDev

Wow, did two #LibResilient blogposts week after week. I wonder if I can keep this up next week.

#LibResilient got a CLI
https://resilient.is/blog/libresilient-cli/

It's a tricky beast to implement, mainly because most relevant functionality comes from plugins anyway, so the CLI necessarily also has to basically be a thin layer over the plugin code.

The nice thing is that it's implemented in @deno_land. Compared to NodeJS, the difference is like night and day. Deno has a built-in test system, and implements all the WebAPIs LibResilient uses natively.

Might have to re-write all my Jest tests in Deno! 🤔

New in #LibResilient — two #DNSLink based transport plugins:
https://resilient.is/blog/new-dnslink-based-transport-plugins/

DNSLink makes a lot of sense in LibResilient: DNS is often more reliable than web, and DNSLink offers a way to make certain information — here: where to fetch content from — available in case the main site is down without having to put that in the configuration.

This means more flexibility in case main site is down. Easier to push out updates related to alternative endpoints or current IPFS CID.

@esi @libreleah indeed I do, kinda. Here's the relevant talk from #MCH2022:
https://media.ccc.de/v/mch2022-198-trusted-cdns-without-gatekeepers

Project website:
https://resilient.is/

It relies on Service Workers, so it's not a perfect fit for some of these use-cases, but it's a start I think.

#LibResilient

Writing tests in #Deno :dinosaur: is positively *pleasant*.

No clue how they achieved that, but compared with Jest, and especially if you're testing stuff that relies on WebAPIs, Deno is a clear improvement.

Much recommend:
https://deno.land/manual@v1.28.3/basics/testing

Looks like I might be able to tear all the NodeJS/npm crap from #LibResilient after all. Fantastic. 🎉

Guess who's got two thumbs and is re-writing #LibResilient CLI from scratch? :blobtoofast:

https://gitlab.com/rysiekpl/libresilient/-/commits/wip-cli

What is LibResilient you ask?
https://resilient.is/

Here, have a talk from #MCH2022 about it:
https://media.ccc.de/v/mch2022-198-trusted-cdns-without-gatekeepers

@meave

Actually, for the tech-savvy experimentalists out there, @rysiek just posted about a possible alternative he's been working on, #LibResilient .

Can you create a services that runs entirely #p2p and only on low power, unreliable devices, like mobile phones and #raspberrypi s?

#mobilephone #libresilient