themer VS ipfs

It doesn't support nearly as many programs as dracula theme does but I'd recommend giving https://themer.dev/ a try. Supports all the popular terminals, IDEs and then some.

themer - Generate themes for your editor, terminal, wallpaper, Slack, and more.

You could try this: https://themer.dev/

Might sound lazy but might I raise you themer.dev if you ever want to do this again? Also love the colorscheme

https://themer.dev/ is also pretty neat.

An alternative - not just for VSCode, but a whole range of software - https://themer.dev/

You could have a look at Themer: https://github.com/mjswensen/themer which also has a nice Web app at https://themer.dev It let's you generate your own palette or choose from some existing/ popular ones, then exports settings/configs for a growing number of applications, f.e. vim, tux, alacritty, web browsers, other terminals etc.

I don't mind pinning, but back in the day I was having issues using IPFS to transfer small files between devices. I admit I haven't investigated to see if the problems were ever resolved.

I've been watching https://github.com/ipfs/helia which is going to replace https://github.com/ipfs/js-ipfs and hoping they can get an IPFS node working in the browser.

I haven't tried https://js.ipfs.tech/ (js-ipfs) in a while, what is the state of it?

On the topic of IPFS, but also slightly tangential -- how has nobody written an Activity Pub client/server in Javascript and distributed it as a Browser Addon?

If IPFS can be literally hosted via a Firefox Extension[1], how has nobody done the same for an arguably easier protocol like Activity Pub?

1: https://github.com/ipfs/js-ipfs

If you can load them up in js-ipfs that might be better?

Store the content in ipfs and just put the hash in the URL? I haven't used https://github.com/ipfs/js-ipfs in this capacity but I'm under the impression that that's what it's supposed to do.

js.ipfs.tech

You need an import statement instead of require since Node has upgraded to the new module system. Use import * as IPFS from 'ipfs-core'. Read more here: https://github.com/ipfs/js-ipfs

Please take a look at https://github.com/ipfs/js-ipfs/blob/master/docs/core-api/FILES.md for more understanding

You could include js-ipfs[0] and fetch all your resources from IPFS without going through a gateway. However, this approach would make the site fully dependent on JavaScript.

A PWA with a Service Worker could perhaps implement its own client-side "gateway", translating public gateway URLs into direct IPFS access. Without the Service Worker (or without JS) it would fall back to using the gateway.

[0] https://js.ipfs.io/

Of course,You can try it out. You can create some Hash to IPFS from this link Adding data to IPFS https://js.ipfs.io/ and then browse the hash in https://ipfs-gateway.cloud/ It is directly connected to IPFS Node.