dtonon

> in a fully decentralized context (which Nostr is not, for what it's worth).

May I ask you to elaborate on this point?

The typical problem of a centralized infrastructure.

Indeed:

> This means each user gets their own Timeline partition, randomly distributed among shards of our horizontally scalable database (ScyllaDB), replicated across multiple shards for high availability

Thank you for the feedback, I know there are still several rough spots to be fixed.

Nostr is a protocol that has a lot of potential, but there are tradeoffs, it now has a large ecosystem and requires learning some new paradigms, and being completely decentralized the terminology is also becoming more standardized and consolidated over time.

This onboarding system is meant to try to explain them, certainly not for people who want to quickly enter an email and a password and start using a specific app. For that one can precisely download an app and use the built-in onboarding, often apps create a profile without asking for anything and invite afterwards to save the credentials.

These are different paths for different needs, the good thing is that with Nostr you have a choice, and when you have created your digital identity, you can use it anywhere.

RSS is great, Nostr is potentially greater. A lot of work is being put in "transparent" and customizable algorithms for discoverability.

Cool tool, I have often thought about something like this, it is certainly very useful.

> Email us, or find us on Mastodon, Threads, or Twitter X. (Gosh, can we all just agree on one social media network already?)

Nostr!

A similar lady some time ago helped me with a different suggestion: stretch the edge a little near the side and blow in. Problem solved.

Forced to sign up with GitHub or Google? No, thanks.

Funny, a websockes hell! Can you port it to Nostr? Could be an interesting stress-test

Statics blogs are cool but you have to manage them uploading the content every time. The interesting aspect of this solution is that you can use whatever client that supports long format (https://habla.news, https://yakihonne.com, https://highlighter.com, etc) to write your post, and your personal blog is automatically updated. No fuss.

Fair objection, but if you don't need to modify the structure/behavior, you can just use the html template file I built for you :)

You should take it upon yourself to save your data, if it is really important to you, so that if all your relays fail, you can simply rebroadcast all your events to a new one and you will be fine. It's a problem solved in a collaborative and decentralized way.

I used Svelte for convenience, so you need npm (or equivalent), but only if you want to develop/extend the project. If you just want to use it, the html template is sufficient.

Not necessarily, the gossip/outbox model (NIP-65) tells clients which relays they should check:

https://mikedilger.com/gossip-model/

It is of course possible to combine this approach with undifferentiated access to well known relays, to fetch content from not followed people.

> or trying to find a coffee shop that will let you use its restroom

In Italy all the public business like coffee shops ("bars") have to let free access to the toilet by law, even if you don't buy anything.

This is not exact. Filecoin is built on the top of IPFS!

https://filecoin.io/build/

You can use any qrcode reader and simply concatenate the data streams. As usual if the specs are open source you are always able to recover the data, even without the original tools.

This was exactly the idea when I added the "self mode": https://github.com/dtonon/papiro

:)

So big that you cannot call it "card' anymore :)

Jokes apart here you can find an insight about qrcodes capacity: https://github.com/dtonon/papiro

+1

:)

The "Read the blog post" link is placed in the first highlighted box of the project's homepage :)

It is a service, because the bridge is a software that need to be keep operational 24/24h and sometimes this is not so trivial (if I don't get wrong WA need an Android emulator running).

I didn't test CalyxOS yet but I suggest you to try GrapheneOS, if you have a Pixel. I think it is really well done, the documentation is detailed and the team's attention about security, and so privacy, is rock solid.

They tried to insight this with the "bounce rate"

My fault: alphanumeric mode is not suitable for a GPG key, because it is:

> 0–9, A–Z (upper-case only), space, $, %, *, +, -, ., /, :

and so we miss the lowercase [a-z]. Therefore we need to use the 2953 bytes binary option.

You are welcome, great project :)

Maybe this could interest: https://divan.dev/posts/animatedqr/

On low error correction level you can save 2953 bytes in binary and 4296 in alphanumeric mode. The latter should be fine for a gpg key.

I'm experimenting for fun on this side: https://github.com/dtonon/papiro

Hi, Papiro author here!

I was thinking how to properly backup my passwords and 2FA codes offline, in the end I made this simple script. It is useful for saving files offline for backup and portability purposes, using a printer. I think it works well for password manager and 2fa codes backups, but you can use it in other creatives ways too, for example you can send a file, plain or encrypted, by old-style-mail :)

I would love to have some feedbacks from security and privacy focused people like you!