Anyways, let me know if I should bother you with Mlkut news again when it is ready to deal with your usecases... well that also includes that if you want, you can contribute with a want-list of features for apps you are gravitating towards lately.
The unit that is really incentivezed is the unit that enough individuals incentives, either with money or relationships.
Peergos.net has been running on fumes for more than a decade because on person cares enough and charges enough and gets enough grants. Ente's CEO had his first salary after 5 years.
My point is, the Web solved hosting incentives long ago, and #Pkarr whole point was to allow for credible exit as reliably as DNS.
#mlkut is basically porting Peergos privacy and Pkarr credible exist to one place, and hopefully if enough people like it I can donate to Peergos because their dedication for privacy is legendary.
I thought Solarpunk is just Mediterraneans building robots before Siesta.
Imagine if the "fs" library was encrypting everything and backing it up to a dumb host and any file you make public is available with URl where your public key is the domain, and the host is entirely transparent and replaceable... that is only the start of Mlkut.org
By the end of this month I should have the first usuable implementation of Cryptree in Rust, as a crate abstract enough to be used by anyone ... then I will go hard on the opinionated layer; identity, key management, host api etc. #Mlkut
I hope you are getting paid for making these UI elements an open source standard.
You can always open https://relay.pkarr.org to check on Mainline DHT and see an estimate of the current nodes count, it makes me smile usually.
You don't have to wait, you can ask them directly; do you have plans to open source the app?
You wanted to restrict the CI's access to parts of the repo?
They have no intention of doing so.
If you were using Github as an alternative to Google Drive or Proton Drive, would you miss being able to grant access to subfolders and files? Or is the coarse access control by Repository enough for your needs?
What if Github can let you share single files in private Repositories? Would you still wish for sharing subfolders too?
Iroh, and write whatever logic you want.
What do you think about Urbit names? Something like "ravmel-ropdyl" ... a name that is readable and maybe memorable, at least as much as phone number, but we can do it so that it is "unmonetized", meaning you can't choose it, you can't sell it, you don't need to renew it, just a random name that you get if you pay the Bitcoin fees to the miners.
If you are interested in that, let me know, I am working on a spec for that to compliment my work on Pkarr.org, for the occasions that short readable names are necessary.
I am the maintainer of pkarr.org, and I designed and implemented most of pubky core (the protocol that the app is built on).
I no longer work at Synonym, so I don't have privileged insight on when they will allow users to try the beta.
If anyone can answer you it would be nostr:nprofile1qqsgeksa4tajm7x673gq2v7t56dkgkh6pjhhzdhrgxlpke4za8jmmkqpz9mhxue69uhkummnw3e82efwvdhk6qgjwaehxw309ac82unsd3jhqct89ejhxjylycj
Something will give sooner or later. The status quo is not sustainable and Lightning is increasingly disappointing everyone, so unless Bitcoiners will turn custodial shills, they will have to give something.
Good for them.
Nostr could do some of the things Alex says Bluesky does better:
1) We can create a new kind that replaces kind 1 which has spans (or facets) indicating bold, or url, or anything else. I wanted to do it that way since years ago when we had the '[0]' replacements (I thought it should just be a span in a tag with no placeholder in the content)
2) If we think a chain of events is needed to prove that none of your events were censored (so we can properly claim censorship resistance), we could add another kind where authors publish their chain of events as a list of IDs. If it needs some kind of mergeability to fix race conditions, I've talked about how to do that with a last-write-wins (LWW) conflict free replicated data type (CRDT) in https://github.com/nostr-protocol/nips/pull/1630.
nostr:naddr1qqgxymr4v4ekk7fdweej6mn0wd68yqgwwaehxw309ahx7uewd3hkctcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsxpqqqp65wq3qq3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws2fkr4c
You are effectively saying that Nostr can be anything, but it can't, not unless the clients with most market share options in, but if that is to be taken for granted, then Nostr can have Pkarr IDs and Peergos data model etc. I wish that was true, but you can't have both decentralised development and agility at the same time, the more independent clients the more ossified the development becomes, this is an old story since Email failing to get any end to end encryption, while Signal doing it in few years.
The issue isn't privacy, it is scaling. Although with Drivechains you can have chains that are private. Monero does not solve scaling it adds one more token you have to worry whether it will be acceptable or not. That goes against adoption.
Bitcoin is not ready to serve everyones needs with no kyc, and Bitcoiners who care about this are bullied away.
Please let's get Drivechains over with, or OP_CAT or something.
Or fuck it let's monetize Signet.
You have the correct diagnoses, DeltaaChat areived at the same conclusion with their Webdx or something... the only question is if that is enough or if we are in a local minimum and users won't have enough reasons to move from current browsers.
But at least I think this is the correct way forward, for reasons I explained in earlier post about the many things that apps can't do in fragmented way and need a platform to manage them.