Nuh

Working on https://mlkut.org, designer and maintener of https://pkarr.org.

https://nuh.dev

Public Key

npub1jvxvaufrwtwj79s90n79fuxmm9pntk94rd8zwderdvqv4dcclnvs9s7yqz

Profile Code

nprofile1qqsfxrxw7y3h9hf0zczhelz57rdajse4mz63kn38xu3kkqx2kuv0ekgppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7azakzc

Publishing to

nos.lol

relay.damus.io

Author Public Key

npub1jvxvaufrwtwj79s90n79fuxmm9pntk94rd8zwderdvqv4dcclnvs9s7yqz

Show more details

Last Notes

2025-05-14 02:07:14

- reply

If by "technically" you mean according to consensus rules, I hope you realise not a soul cares about that, not users and not regulators.
Just because people send sats to custodial LN providers addresses, doesn't make that a donation.
You designed this contract (I presume because that is the best you can do with Bitcoin smart contract), but you didn't design it to enable time bomb donations to operators... that is bug not a feature.
Unless of course you do advertise Ark as a time bomb donation to operators, then good luck with adoption and actually good luck with regulators still.

2025-05-13 13:19:26

- reply

Yes I mean this requirement to deal with expiration of vtxos.
I have a server, but I don't want to trust it, I want it to help me keep my vtxos safe if I didn't open my phone for long time (actually happens, I haven't opened Pheonix for ages and forgot battery mode on for weeks), but I don't want the server to be able to steal, or more importantly I don't want to run a server for others that is legally a custodian of money.

2025-05-13 08:23:22

- reply

Lazy question (promise to read more later); is there any way for a non custodial server to deal with the "remixing" of vtxos on my behalf?
Asking because if that is at all possible, I would like to add that as a native function or a plugin to the same Homeservers hosting users private data and republishing their Pkarr keys to the DHT.
Or in Nostr terms, user's paid relay.

2025-04-20 08:02:28

- reply

All blockchain scalability solutions do is to compress history to almost nothing, then post the state diff to the chain every now and then.
Well, that means the l2 state can only increase in size by how much state diff you can fit on the blocks of l1.
So you can't onboard a million user in a single state diff, nor can you update the accounts of millions of users in a single state diff.
The account model is absolutely impossible to scale. Unless you bait and switch, using the l1 chain for timestamping and then dump the actual state on another layer.
But now we are back to the Interplanetary filesystem bullshit.
In practice only you and few others are incentivezed to store your state... but now congratulations you just invented client side validation.

2025-04-20 07:53:58

The reason client side validation is perfect for scalability, is that we can compress history with zero knowledge proofs, but we can't compress stuff like utxos.
This also means we can infinitely scale digital cash, but the "world computer" (usually means rich public statefulness) can't scale.
Again, indexers (search engines, feed curators, matching engines, etc..) will never be decentralised and censorship resistant as Bitcoin... for the same reason; too much state.

2025-04-16 16:54:06

This can and will (if worth it at all) happen to any Pubky indexers or Nostr relays that capture majority of eye balls. And when they comply, because they must, it will be effectively the same as shadow banning.
Play search engine games, win censorship prize.
If you don't want to deal with censorship, don't get big, and don't work on problems that requires big servers to solve them, or build a blockchain and make each post cost $20.
There sincerely no third options.
#nevent1q…acpr

2025-04-04 07:23:15

- reply

That is a gamble with >90% chance of failiure, that you can only make after you have your finances in order, to some degree at least.

2025-04-03 08:39:59

I agree with this, but as a non-billionaire I would like to tell young folks; take care of your finances first.
#nevent1q…3f7p

2025-04-02 04:57:07

I think there should be an option to Mute someone on timeline but not on replies, and maybe an option for the opposite. People are not equally annoying in both realms.

2025-04-01 13:35:29

- reply

I actually don't mind then being new Twitter, what boils my blood is that they popularised a centralised PKI server as the solution to decentralised sovereign identity... and that will hurt way more than the social media use case.

2025-04-01 13:34:10

- reply

No it is not a hard problem, the key rotation problem is simply impossible to solve without reinventing Bitcoin, and the user on boarding problem is trivial solved by web fingers.
They just decided to pretend to be doing something they either knew impossible to do, or worse.
The user adoption wouldn't have been affected if they just gave users usernames ... unless you mean the smoke and mirror of decentralised identity helped adoption, but I suspect no body really gives a shot about that.
Which is why I don't fuckin understand why are they confusing everyone.

2025-04-01 13:17:40

- reply

You literally posted him lying by ommission, he is pretending that people Mirroring the centralised directory means anything different from just a TLD. That is a LIE. If you sit down and analyse it you should be able to see why this key rotation and DID is just a circus without a Blockchain like Bitcoin.
But the real issue here is, no matter what I say, it won't matter, because everyone decided to believe this bullshit no matter what and pretend that the nice people because they are nice achieved the impossible.
Ok fine.

2025-04-01 12:57:33

- reply

By the way Twitter is also fine since we don't care if something is centralised or not. And indeed it is the only thing worth wasting time on it at the moment.

2025-04-01 12:56:07

- reply

I didn't say they are not fine, but Farcaster is honest about what they are doing, Bluesky made something that is not different from a TLD and insists that it is, and confuses a lot of people.
I wouldn't have any problem with them if they just said this is a centralised PKI. But they keep saying that it is not. That is a lie, no need to worry about it beyond just knowing that this is a lie.

2025-04-01 12:44:04

- reply

Then why didn't Bluesky just register a TLD instead of pretending to have made a decentralised identity?

2025-04-01 12:43:19

- reply

Being decent and being dishonest is not mutually exclusive... people just love to lie to themselves

2025-04-01 12:09:22

- reply

We already have ICANN, did:plc offers nothing new only worse, but the intellectual dishonesty about this fact should tell you what you need to know about Bluesky dedication to digital sovereignty.

2025-04-01 07:59:41

I have to admit, every time I see a screenshot or link from Mastodon I get envious of the quality of people and conversations there.
This can very well be a selection bias, but I might cave in and create a Mastodon account.
I just wish Mastodon was using Pkarr, so I neither have to setup a server nor worry about who is the first server I sign up to.

2025-04-01 07:03:49

#asknostr
#nevent1q…w7gm

2025-04-01 06:29:03

- reply

Can Block employees, and contractors get paid in Bitcoin?

2025-03-31 22:54:37

- reply

I am trying to build just that at Mlkut.org but don't hold your breath I am working on that in my free time now.
If you want to try something now, try Peergos.net

2025-03-31 17:30:20

- reply

The reason to stick with Nostr is getting grants from Nostr enthusiasts... but if you need that more than flexibility to address your market, then you are doomed anyways in my opinion.

2025-03-31 17:28:23

- reply

No Nostr isn't the most simple thing possible not by a long shot, and you might as well define your own spec, I promise you using Nostr events will bring you nothing but limitations.
Just invent your own thing, you won't regret it.

2025-03-31 17:26:38

- reply

I think you are ignoring the fact that you and everyone else is at the mercy of the most popular clients because that is where the users are at.
But regardless, even if you think of Lexicons like some sort of a gentlemen agreement... this shit have been done decades ago with schema.org ... it being a "Lexicon" is useless. It could have been a markdown file and that old have had the same damn result.
My general point is that Lexicons are super overrated and over sold and solve nothing.

2025-03-31 17:04:58

- reply

Wow... not sure what to tell you man. OK, I believe you, Bluesky now are physically incapable of updating the schemas they use because the older one propagated.
Honestly, I don't hate that people trust each other that much, good for everyone.

2025-03-31 16:54:24

- reply

Lol... i literally saw Bluesky making breaking changes to their API before... not sure what magic do you think Json schemas have to prevent breaking updates.
Man, people really buy these claims!

2025-03-31 16:52:29

- reply

I think you are thinking of the Matrix Protocol... which plenty of governments already using for what you are saying instead of relying on American companies like Slack.
If I were you I would start playing with Matrix sdk before reinventing this wheel.

2025-03-31 16:30:13

For anyone who cares, the reason I a argue for a sovereign e2ee filesystem, is because that is the only thing we can make interoperable between apps... just like POSIX and files in general are the only interoperability success story in history.
What I consider feasible is taking that and make it Web native without getting locked in platforms like Google Drive.
Once that is in place, let the best app developer win, and if one file format becomes very useful, we reverse engineer it like we always do, like interoperability always worked; forcefully.

2025-03-31 16:19:43

- reply

And of course, the moment Bluesky decides to change their API a little this integration will break.
So what was the point? If you are not going to have stuff as stable and stupidly hard to change as web api, then why pretend you have interop?

2025-03-31 16:13:52

- reply

No not via the lexicon, via actual literal code, someone had to write the code for this to work, the Lexicon, the absurd JSON schema offers absolutely nothing.

2025-03-31 16:12:44

- reply

Ok, I will bite, what does Nostr offer businesses? Because my basic bias is that it offers absolutely nothing, if anything the shitcoin Wallet Connect offers more because at least you know people who use that have money and likely to waste it on stupid stuff.
What does an npub and very unreliable relays and extremely small audience offer businesses?

2025-03-31 16:08:20

- reply

You will publish your specs mainly to say that they are open. But not a soul will bother implementing them, and for a good reason, you can break the spec at will, otherwise you are destroying your ability to iterate on your product, and suddenly the random zero users devs demand that you take their consent before you update your schemas.... Lol won't happen.

2025-03-31 16:05:42

- reply

Being able to embed stuff has nothing to do with interoperability or lexicons it just means open APIs for extensions/widgets.
Unix apps can be piped together with a common stdin/stdout interfaces... but they don't have to publish specs on how do they behave.

2025-03-31 16:02:30

- reply

Guys this is not interoperability that needs lexicon, this is just good old web components that only need code and a docs page.
Interoperability is you telling others how to implement what you already implemented, but not actually use your code..
Lexicon don't magically replace code, although I am aware they are sold as if they do, as many things Bluesky sells with false advertising.

2025-03-31 15:51:39

- reply

I am idealistic too, but I don't pretend that idealistic is a business plan, I get a job and build what I want to see in the world on my own dime if I have to.
But my point stands, and confirmed, interoperability;
1. Only matters to idealists, not businesses nor most users.
2. It is incredibly hard and don't scale, because it is too social, it is much simpler to iterate a product vs protocols.
My point here is we have a very very limited budget for interoperable protocols, and it can only be spent effectively on stuff like udp/tcp/http and the last one stretches that.
Everything more complex is a lost cause in my opinion, so all the fuss on Lexicons is really overrated.
Finally I want to point out that if you make a "X lexicon" your sense of mission can still be fulfilled if users have to download your app to get the X use case. You don't need other devs to buy in... you can generously write specs to help them replicate your feature, but all the time you put there is time and energy you don't dedicate to your customers and their needs.

2025-03-31 15:41:10

- reply

Why would you do all this work when you can just ... not? What is in it for you as a man trying to feed his family?
You have every incentive to reverse engineer Damus and Amythest schemas to attract their clients... but why would you make a new feature and tell Damus and Amythest how to implement it so their users never have a reason to use your client instead?

2025-03-31 15:38:40

- reply

I actually adopted this for Pubky, but I still think it is useless... no one has any incentive in detailing their schemas just so their competitors can steal market share easier.
Interoperability will never work, because there is no incentive.

2025-03-31 15:35:38

- reply

You should focus on Twitter and Facebook then, same centralised identity and much bigger market.
If did:plc became like ICANN, they would have spent too much time spewing bullshit just to become what they should have started with; registering a TLD and give people domains on signup, instead of this DID garbage.
And the 12 weirdos are not businesses by the way, businesses don't give a fuck, hell even presidents their didn't care enough to point their domain to the did:plc.
If you are in it for the business opportunity, make sure to not get high on this supply, if you have to sell it to business good for you, I am rooting for you, just don't confuse yourself.
Most importantly; don't ignore all the signs that Bluesky users don't give a shit about any of this, so if you build a business assuming there is a market for digital sovereignty enthusiasts... you are going to lose your shirt.

2025-03-31 09:08:30

- reply

It is an asymmetrical key that can be associated with a web2.0 account to log in without passwords by signing a challenge.
The often not discussed aspect of it, is that it is meant to be device bound, so services may only accept keys that are themselves signed by a trusted party, to prove that it was generated in a secure environment where the key can't be extracted by scripts or extensions or what not.
It is not bad honestly, just doesn't work for sovereign identity as nicely.

2025-03-31 07:10:48

- reply

I sincerely want everyone and their mothers to be writing software, I just want to hear about the software and I want to hear about it from a confident proud owner.
When you say "I vibe coded this" the signal you are sending is "If this is good I did it, but if it is shit, don't blame me blame the AI" ... this is a weak ass voice and I don't respect it.

2025-03-31 07:07:08

Devs celebrate "vibe coding" for the same reason CEOs celebrate funding... because if you can't celebrate results, you gotta celebrate the process.

2025-03-30 22:52:41

"I think we can only truly create when we truly understand what we have to create with."
https://moxie.org/2024/09/23/a-good-engineer.html

2025-03-30 15:19:38

- reply

Yeas that was my best effort suggestion ll, but I am not aware of the latest state of the frontend so they might have added that, if not, it is a weekend project.
I just suspect that no one will give a shit.

2025-03-30 15:16:51

- reply

Writes go to the homeserver, but reads indeed are all from the indexer, since you rarely if ever reading static posts, most of the team you need rich metadata so might as well get the data in the same roundtrip.

2025-03-30 14:58:03

- reply

As I replied earlier, you can't sign everything that the indexer serves, so the only option here is that you go read the original post from the homeserver if you care.
Sure signatures might have made that slightly better, but again many or most of the data the indexer serves simply can't be signed by the author.
Anyways, if you showed the team that signatures can materially improve Pubky, nothing in the protocol will prevent them from adding signatures, but they may still choose to not bother because the juice is not worth the squeeze.
I am happy that i didn't force my personal opinions of signed merkle trees and end to end encryption from the get go, as that would have delayed the app at least a year.
Now the team can do whatever they want. But at least the app is already here and ready to prove its design thesis which is entirely orthogonal to this conversation.

2025-03-30 14:50:03

- reply

I don't want to speak for the team, but since this design was mine I will take the "blame" ... yes the indexer returns the data.
The reasoning here is that while it could just give you a URL, that is not going to be enough for this app requirements, namely;
1. Data availability and latency shouldn't be subject to the variance of homeservers availability and latency.
2. Some transformations are needed, for example inlining rich text things like showing the ID as the current name of the user in a mention, or for example compressing images.
3. Some data, in fact the most important data can't be deduced from the homeserver at all, for example backlinks and replies and counts of tags etc.
So honestly you have to trust the indexer to get the quality and features the app required from us.
There are room for improvement, most importantly falling back to the homeserver if the indexer is forced to censoring something or someone.
I want to note here that if the client was signing the data before sending it to the homeserver, none of these limitations would go away, which is one of the reasons I didn't invest in client side signing and the key management that that entails.
The protocol (client-homeserver)can get more sovereign and more private and more encrypted... but that won't change the nature of pubky app.
If the first app was private chat, i would have made different choices, but these choices weren't worth the time investment if at rhe end you have to trust the indexer to serve you things that can't be signed anyways.

2025-03-29 18:18:18

- reply

Too obscure and cultural specific expression to translate, but it is a personal note anyways don't worry about it :)

2025-03-29 17:34:57

أصلا عادي

2025-03-29 05:45:25

- reply

No, you can't derive an ed25519 key from nsec in a way that is drivable from your npub. Meaning you will still have to tell people what is your ed25519 key, but if they know that, they can also know what are your relays, so not much reason to use the DHT.
The catch is the same catch as Nip05, you have to support it at client side.

2025-03-29 05:42:59

- reply

You don't need a whole new protocol, just support a different identity entry point, which can point to your npub and relays, Relays don't need to know about that change at all, only some clients could opt in.
As for bootstraping a new DHT, small DHTs are extremely vulnerable to Sybil attacks, and i have never seen any DHT succeeding at growing to anywhere near Mainline size (thanks to torrent).
However if you think you can do it, go for it, so far none of the folks who said they can do it actually put in the work to grow a secp DHT.

2025-03-29 05:21:42

- reply

Hello, the author of Pkarr that uses Mainline DHT here, you can go to app.pkarr.org and put your npub and relays and whatever you want to put in a DNS packet (because that is what it is).
The only problem that prevented Nostr from adopting Pkarr despite my constant advocacy for it for almost two years; the root identity HAS to be ed25519 key, this is not my decision this is what the biggest DHT in the world decided to use decade ago (see estimate of number of nodes here relay.pkarr.org).
So yeah I would love it if Nostr supports Pkarr as a root identity or at least as much as it supports ICANN with Nip05... but that is up to client developers.

2025-03-29 04:57:03

- reply

Great summary, I just wanted to emphasise that the homeserver doesn't know anything about the app indexer, nor does it do any work to help this specific app other than hosting data as you expect from WebDav.
Thanks for your work on BitVM by the way.

2025-03-28 14:06:49

- reply

It is a centralised public ledger, the premise is that people can monitor it and hold the issuer accountable, but if it is free as it is now, then it is open to spam until it is too expensive to mirror, so while they are pretending to have solved the problem that Blockchains need fees for, we can call them out on their bullshit, ans have fun while we are at it.

2025-03-28 13:51:19

- reply

Just create an npub, put it in Pkarr or the homeserver and do whatever you want... using the root secret key will only result in losing it, and encouraging people to do that will only result in bad reputation for Pkarr and keys in general

2025-03-28 13:48:12

- reply

As far as I remember the JS client had a method or function to decrypt recovery files, if not it should be easily exposed.
I however strongly discourage treating the root key this way, as it risks losing it, but it is your key and you are free to risk it.

2025-03-28 13:27:36

- reply

What is in it is what is in all recovery files, and encrypted secret key.
Also, there's a whole mobile app to sign into things with QR codes.

2025-03-28 13:24:57

- reply

I worked so freaking hard to get rid of this 12 words awful UX, please don't tell me you don't know about the recovery file!

2025-03-28 04:00:45

The Bitcoin white paper forever inscribed on the Bluesky free and open blockchain
https://plc.surge.sh/#did:plc:a2uf5uxhgznzzplom2qzgz6g
#nevent1q…vk63

2025-03-28 00:36:28

- reply

You should upload that to https://plc.surge.sh

2025-03-27 23:00:44

- reply

Share it around :)

2025-03-27 22:44:35

Bluesky identity system claims that it solved public ledgers without the need for any censorship or fees ... let's test that.
You can upload any file that allegedly will stay on the persistent ledger and will be mirrored by every audit service in the future
https://plc.surge.sh/#did:plc:trzxqotcyog2mmuxq7ab2vs6

2025-03-26 18:12:34

- reply

Urbit was 100% designed with cloud in mind, listen to the inventory... he just hoped that "confidential computing" would solve the trust issue... which at least Signal agrees with, but if you want to be a purist, it doesn't help that much, you need to trust the chip designers and other assumptions.
Laptops get closed often, fighting the cloud is not viable, but we can make all data E2ee so that the compute happen on your machine but data availability is handled by the cloud.

2025-03-26 14:50:31

Merkle Treap is my favorite data structure, it is a mutable sortable merkle tree.
Sortable means you get perfect locality of pointers, instead of the randomisation of hash maps.
Mutable meaning you can add or remove elements while changing Only the nodes on the path from the changed element to the root.
Every update happens from the top bottom, as opposed to bottom up as usual in Merkle trees like the one used in Git.
It is just a joy.
The only downside is if you are using it for set reconciliation with multiple writers, a bad writer can mine keys such that the treap degenerates into a linked list.
So for set reconciliation from multiple untrusted writers, you should use RBSR like Negentropy.

2025-03-26 09:16:35

- reply

😅

2025-03-26 08:58:39

- reply

The only downside is identity being tied to a host... but I don't think that applies to link aggregation.

2025-03-26 02:17:54

Periodic reminder that Signal FUD harms people, especially as all practical alternatives are much less tust worthy, some not encrypted at all.
Nothing is completely secure, least of all whatever obscure alternative the FUD wants you to switch to, if they offer anything at all.
Unless you know what you are doing, ignore this.
#nevent1q…a7nk

2025-03-25 16:23:35

- reply

https://t.me/mlkut_org

2025-03-25 15:10:19

- reply

Not yet, currently trying to port the Cryptree to Rust... everything depends on it.
But I welcome conversations and mind storming always... I have a Matrix room, and I can setup one on Telegram if anyone cares
https://matrix.to/#/!hGPtFLAsWWlCxxoDqo:matrix.org?via=matrix.org

2025-03-25 15:08:01

- reply

Try to explore Peergos.net for now, it has the e2ee but not the sovereign identity yet, and it is written in Java and quite old, and never accepted VC money, so cut it some slack.

2025-03-25 15:05:38

- reply

Peergos is an open alternative to Proton Drive offering end to end encrypted filesystem where the server is entirely a dumb host/storage. Put so far it relied on a centralised identity layer similar to Bluesky.
Mlkut.org is my personal effort to port that e2ee filesystem to Rust, simplify it, and replace the centralised identity with Pkarr.
As for why is that helpful, it is because Pkarr tells every client exactly who hosts your data at any moment in time giving you unbroken URLs and strong consistency, while the rest of Mlkut gives you full control over who can read and/or write to any folder or file in your filesystem.
That allows you to use wide variety of open source apps to author and share and publish, but it also allows for collaboration and you can compose these folders to build an emergent community, like forums or groups with moderation etc... there are things that you can't do with only these primitives, but for small world usecases, you can go so far with only this.
Let me put it this way; if you can imagine building it with Proton Drive / Google Drive, you should be able to build it with Mlkut, but also no vendor lock.

2025-03-25 13:49:03

- reply

Meaning J O B, work for income, this way you won't be so anxious for adoption ... if it is a passion project, you can persist for decades AND enjoy your time with no pressure.

2025-03-25 13:38:57

This requires that we get jobs though, this can't be the job, otherwise we will burn out.
#nevent1q…nmux

2025-03-25 13:37:44

Let's start ove, and start small, from the minimum viable digital sovereignty and grow from there, worst case scenario we achieve something really good but not popular... Social media is an all or nothing, when it fails to take off, it crashes and burns, with absolutely nothing left standing.
Let's ratchet progress on digital sovereignty, we already have miraculous foundations (Bitcoin, Mainline, and Cryptrees) all of which was invented around the same time for some reason!
It is our turn to make the new wave of tech and products, and we should build them with soundness and care, that they can germinate and survive to be passed on to the next generation, even if this one simply never gave a fuck.

2025-03-25 13:10:40

- reply

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.

2025-03-25 13:08:38

- reply

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.

2025-03-25 13:03:07

Yes AND things that last needs to be useful even if used by one or two people.
Early adopting Signal was easy as fuck, and I spent years talking to only one person their before anyone else joined, I don't mind care about Signal DAU, all I care about is that they don't go out of business because I can't run my own instance.
This applies even more to private cloud storage where you literally need yourself and your data, and the rest is bonus.
#nevent1q…p9cd

2025-03-25 12:59:09

- reply

Been saying this for years and it is why I keep arguing that the "next web" or whatever should be built from the smallest unit (personal storage) outwards... doing the opposite sacrifices what Proton Drive does and we can easily do, all for chasing the layers that are least probable to be fixed at scale.

2025-03-25 07:14:25

- reply

That's the holy grail, quantum keys, that you can only use once,, you just have a token, and when you transfer it once you can't double spend it because the signing keys were lost while signing.
But this also means that you can't really backup your keys with redundancy, so if your hardware wallet loses its quantum state, you lose your money.
So we better work with what we have now and figure out how to prevent double spending at scale, even if we have to accept gradient of confidence, just like we have confirmations number and 1 confirmation is not as final as 6 or 100.

2025-03-24 19:00:35

- reply

Actually this is most likely a grift from a EU regulations shill, most of that money will go to him I am sure.

2025-03-24 18:12:49

- reply

Git

2025-03-24 17:54:50

- reply

I thought Solarpunk is just Mediterraneans building robots before Siesta.

2025-03-24 17:45:34

- reply

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

2025-03-24 17:45:21

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

2025-03-23 15:28:34

- reply

You should be able to update your data on the sovereign web, kinda thought that was obvious from the sovereign part.

2025-03-23 15:23:29

There is absolutely nothing wrong with that, the indexers still tell you the dates they first saw these updates, there is nothing wrong in users publishing an update to anything they authored, this is how the Web works and it is how it should.
And by the way Nostr can do that too if clients cared to support that, not sure why do we dunk on Bluesky for the wrong reasons? did:plc is already bad enough.
#nevent1q…9crh

2025-03-23 10:16:55

So many apps would benifit from an open source alternative to Proton Drive, and while we are at it no vendor lock and you can migrate servers while keeping all your URLs and shares functional.
And if that took off, everytime an app refuses to integrate with it, an open source app would fill the void.
For a lot a lot of apps, you only need one reliable backend dumb storage so developers can focus on their app as if it was a local app writing to disk, but get the sync and availability for free.
#nevent1q…lfu2

2025-03-22 16:17:41

Private conversations are more free conversations.
#nevent1q…zyxa

2025-03-22 07:07:36

If you are in the market for a free and open source alternative to Proton Drive, you should check peergos.org the founder have been working on this for 11 years with no VC money as a matter of principle.
And if you would rather have these features in Nostr apps, I started working on a Rust library (Peergos is written in Java) that can be embedded in any client with no opinions on the identity layer.
Of course I will use it with Pkarr in Mlkut ... but it will be available for all ecosystem, offering E2EE filesystem with granular access control, while trusting the cloud to only provide availability.

2025-03-22 06:59:36

- reply

I hope you are getting paid for making these UI elements an open source standard.

2025-03-22 02:50:06

- reply

Pretty slick. I also love how the images are stacked

2025-03-21 10:43:45

- reply

It is a good one.

2025-03-21 10:17:52

- reply

Ok that escalated quickly.
I didn't suggest malice, but I don't respect it even if it comes from well intentions, and think people shouldn't invest in stuff designed by committees.
RemoteStorage is as simple as it could be, and Peergos is as private as it could be, the academic pedigree is worthless to me.
And the only way to stop running headless looking for self worth, is to just impress yourself, I don't think PhD will do you any better than learning to do a backflip.

2025-03-21 07:20:26

- reply

Except they keep giving their private keys to every device and app they want to try, or they give their private keys to nsec bunker, which most often is a trusted custodial.
You can't twist people arm, if they want delegation they will and do delegate, the question is whether they can recover from that delegation or not.

2025-03-21 05:07:01

- reply

Solid doesn't deserve much attention, it wasted so much if its complexity budget on weird stuff like linked data, if anything RemoteStorage.io is much better, but even better than both is Peergos as it actually tackles privacy and minimizes trust needed for the host.

2025-03-20 18:11:47

- reply

What? 😅

2025-03-20 16:14:59

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.

2025-03-19 10:13:01

- reply

You don't have to wait, you can ask them directly; do you have plans to open source the app?

2025-03-19 08:11:19

- reply

Chat apps are special since they can actually work with relays that only keep media for few days max with rate limiting.
But of course, if we can build an open version of Proton Drive, then chat can be just an app on top of more general purpose private storage.

2025-03-19 08:04:30

- reply

You wanted to restrict the CI's access to parts of the repo?

2025-03-19 08:03:05

- reply

They have no intention of doing so.