Show newer

@silverpill you can fork without any issue. The CLA is standard procedure in companies that need to keep track of copyright.

As for their frontend, it is only used for those that want to mint the locks. Those that want to buy the NFT/get access to a site don't need to visit it.

I'm trying to think what you'd do differently that would make the system "more open"...

@silverpill I agree about the "governance theater", but I'd say you are being too cynical about the rest... The frontend is open source, it is not their fault if "no one will make a different frontend". The important thing is composability anyway, frontends matter little: same with Uniswap and most of the main DeFi projects, users worry about contracts having bugs and locking funds. At this stage of development, having upgradeable contracts seems less risky.

@silverpill as for "how it could benefit from intermediaries"... my argument would be not that different from what guides my work on

In short: there are plenty of systems where people *want* to rely on a third-party to deal with the complexity and to work be their proxy. I've written about it on

@silverpill how is unlock centralized? IIUIC, it is just a system to mint NFTs and web3 libraries that check ownership, no?

@silverpill Hey, it's cool you checked this out. I've been following your work on Mitra and it's really impressive!

Re: payments and subscriptions, have you checked already the Unlock Protocol (

Re: the idea from the post, I wouldn't make with crypto/web3. First, because there is already a project doing something similar for crypto, gitcoin. Second, this would *benefit* from having intermediaries and build social trust. There is some clash with the crypto ethos.

I've finally connected my Mitra instance to a real blockchain and configured the subscription service. The blockchain is Polygon PoS which is EVM-compatible #Ethereum sidechain. It is fast and cheap - ideal for payments. Of course this comes at the cost of decentralization so it's not a good choice for storing large amounts of money.
This is my subscription page: It accepts payments in WMATIC token which is a ERC-20 version of MATIC, the native currency of Polygon blockchain.
Yesterday I successfully started a payment stream from my account on another Mitra instance. You can try that too. The server will recognize your payment if you have ethereum address in your profile (in the $ETH field). Then you will be able to see my subscriber-only posts, though I don't think I will use paywall for anything other than testing this feature.
The contracts can be found here: (I'm using AdapterMini variant).


I'll push for a bit more details, please... "integrated" in the sense of having the functionality in the Soapbox backend?

To me this is interesting because on communick I'm hosting Mastodon, Matrix and XMPP, and the "integration" is only at the account level (using LDAP for SSO)

@alex It's cool, but why not just stick with XMPP or matrix?

All these years of bull markets made the whole industry complacent. "Just throw more money at it", was the easy solution offered by anyone, including "senior" managers who never had to learn how to make do with the resources available - or not do at all.

Now that bubble finally popped is going to the time to see who can actually manage and who was just coasting around.

I got into a week-long discussion on Hacker News with someone who does "tech strategy consulting for a living" (his words), who insists that it makes no sense for a company to support development.

The same type of bizdev-bro who will happily parrot things like "companies should outsource everything that is not core to their business", and are simply blind to how that could be done by funding F/OSS projects.

⁦@k9mail_app⁩, a project I started way back in 2008 has found a forever home as part of the Mozilla family! Congrats to ⁦@cketti⁩ on making this happen!


The important thing by having decentralized identities is that it gives new *options* for whole new classes of applications that do not exist. No one is being forced to adopt a system just because it is now possible to do it on a blockchain, and we do not need to destroy the current systems if they work well - or at least if they work better than any alternative. There will be even plenty of cases where the status quo is totally fine.


In general, what upsets me with anti-web3 people is that they fall into the *same* trap as the maxis: they start from this ridiculous notion that "web3" is about creating a Highlander solution (there can be only one!) and that this solution needs to satisfy all constraints, otherwise it is rubbish that needs to be discarded.


2) "Security practices are hard, no one will do it properly, they will rather have some expert that can do it for them".

Well, if you don't want to deal with security hygiene, you delegate. Just like the majority of people will rightfully prefer to have a bank to manage most of their funds, one could still envision a future where service providers will act as a proxy to anything that requires "your" identity(ies).


I've posted this on HN, will replicate here.

1) The trilemmas do not need to be *solved*. They just need to be *acknowledged* when you are designing your application so that people can understand the types of trade-offs being made. When sybil-resistance is not a required, you focus on privacy and decentralization. When sybil-resistance *is* required, you choose if you'll sacrifice privacy or decentralization.

Depending on the use-case, one might be preferred over the other.

This is just the type of open source project that I would like to support, but *not* by buying the current iteration. What I'd like to see is some kind of sponsorship model that gives the sponsors the *option* to receive any of the units that come in the future. For example, I'd like to give $10 every month and if 3 years later they get a model that I'm interested, the money I already put in could work as a down payment.

the fully open source hardware RISC-V Precursor from bunnie studios is now shipping out to people. pretty insane this thing was actually made #OSHW

@alex that's *every* youtuber with more than 1M subscribers. I think there is a minimum 10 min length for a video to qualify for monetization.

Sponsorblock helps, but someday I will really work on a yt-dl plugin that not only downloads the video but clips it to have only the highlights.

Show older
Communick Social

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!