api.distributed.press VS multi-account-containers

I think the obvious match here is how IPFS can use a dnslink TXT file to point to the content-addressable top of an IPFS-distributed static web https://docs.ipfs.tech/concepts/dnslink/ . This is how a lot of dweb/web3 websites maintain and advertise a non-http mirror. It works out of the box for sites served using https://distributed.press/ (non-commercial, open source) or https://fleek.co/ (hosted).

If you use Brave, or have the IPFS browser extension, you can access sites like https://ffdweb.org/ as an option, or preferentially.

This should be a link to https://distributed.press/

There are several new and exciting decentralized web protocols. I am working on a tool to publish to all of them. Right now it publishes to IPFS and Hypercore, and will eventually serve signed plaintext so content can be shared to Scuttlebutt and Aether networks.

For example, this site is published using https://github.com/hyphacoop/api.distributed.press and it can be accessed over HTTP, IPFS, and Hypercore.

https://staging.compost.digital

Interesting!

My negative experience with Firefox was with this 6 year old feature request relating to container colors. [0] They have hardcoded some colors & icons (6 or 8 I think?) as possible options. The problem is: If you have more than half a dozen of Gmail accounts that you want to containerize (e.g. for client work), it is really hard to keep them apart at first glance. Compare this to Google Chrome, where you can choose the browser color for each associated Gmail account individually.

I tried to manually extend & build it for myself, but the codebase relating to that was just a mindfuck to work on...

[0] https://github.com/mozilla/multi-account-containers/issues/1...

TL;DR: https://xkcd.com/619

It is an extension for Firefox, but one created by Mozilla. It's official in that sense, but it does seem a little strange it's not included by default.

https://addons.mozilla.org/firefox/addon/multi-account-conta...

the opposite is true, too, since "Clear History" in Chrome Profiles behaves correctly and (AFAIK) is scoped just to that Profile unlike our container friend: https://github.com/mozilla/multi-account-containers/issues/3...

I still use them because combined with https://addons.mozilla.org/en-US/firefox/addon/open-url-in-c... ( https://github.com/honsiorovskyi/open-url-in-container ) is a game changer for my workflow but it does make me sad that issue has been open for so long

I have about 35 tabs open, some are work tabs, some are personal tabs and others are social tabs. About 1 week ago I started having the problem that while I have the Open Containers completely draining, my CPU is at 100%. While when I close them all my CPU returns to its normal state of use 20% I see that the problem is existing. https://github.com/mozilla/multi-account-containers/issues/572 any help? I have the latest version of Firefox on Windows 10

I've been googling around for a way to recover them and it seems like this is just... a thing hat happens? And it has for years? This is intentional? What the hell?

Firefox Containers - Only if you need to use two accounts from the same website at the same time. You can change groups names and colors. When you need to open another account simultaneously just right-click the tab -> open in new conteiner -> choose one and voilá. It took me time to understand how exactly this worked but I use a lot now. Ohh and never ever never set "Aways open this tab/site in this container" this got me nuts these days. Is hard to revert if you don't really need a certain website aways on a certain container.

Can I start Firefox from the (linux mint) terminal opening a website in a particular container (using the Multi-Account Containers extension. see https://github.com/mozilla/multi-account-containers or https://addons.mozilla.org/en-CA/firefox/addon/multi-account-containers/)