branle went with 280 char limit and I think i'm gonna keep it. eventually we could have different types of messages, short form and long form/blog, that can be viewed separately from user profile. so you can "tweet" and post long form pieces all on one platform.
I feel ya.... possibilities kinda seem endless..
exactly. you can control who you see but can't control who can see you (unless only using private relay and can ensure no mirroring). at least thats my understanding...?
generally i think this is the way to go for a more open and censorship resistant social media platform
i like that about nostr. also like that you can't block anyone (unless using private relay)
thats pretty good. thanks for sharing :)
how much storage is yours using right now? just curious
thats awesome and gives me hope haha. are you doing any local storage or just querying relays in real time for everything? i noticed that the slower pages on branle seem to be those querying the pouchdb
What are Ukarine doging? Accepted Bictoin donation during the war and now banned Bitcoin purchase with local currency?
https://bitcoinmagazine.com/markets/ukraine-bans-bitcoin-purchases-with-national-currency
well thats disappointing
woah extremely cool
yeah this is what I was thinking about. and also with interoperability, so the user can switch hosting services/domain without breaking all their past posted content. like a redirect address in their profile that all clients agree to reference..?
but i'm just starting to learn how to build on the web, beginning with the front end and working my way to the back end. so no clue if anything I said above makes sense/is possible
you got any ideas? after I get my client up and running I was gonna try tackling this next. like a hosting service specifically for your nostr data, that you can point to from your update-able public profile, and the client pushes/pulls content via the address in your profile.
branle fork client. i'm attempting a recursive/nested thread layout to see multiple replies in one view. i would share an image but haven't implemented that yet... and i think you need to set up a server to host the image..? right?
just a beginner dev here but have been pleasantly surprised to not have any issues with lack of M1 support so far