Things moving quick!
What did you think of https://habla.news ?
Discussion
First I heard of it. Will have a look.
It's fantastic; I'm 100% redoing my personal site using nostr and writing straight from habla.news.
I was wondering about trying something like that over the past few days. A Version III of The Spain Report. Still not convinced it's a place to do a whole site thing, vs. another place to publish some stuff thing. What is the key reason for doing it all on Nostr vs. just pushing some stuff you're already doing to the relays?
For me, it's about having all the content I want on my site.
After years of scattering my writing on places, I end up abandoning and have no easy way of taking the content back, I've recently decided to stop feeding other platforms.
Publishing to and serving from Nostr seems like a great way of making my writing interoperable with the broader ecosystem.
As in, if you want to comment/zap, you are creating a native nostr event that other people, in other clients, can interact with.
Right, that is a noble and practical and innovative aim, especially as you say after the last few years of platform nonsense and abuse. Also good for journalists and the public record, for example, anti-delition things. And that is kind of my point. If the innovation is creator-reader direct via Nostr at the protocol level, that would be wonderful because then people can do different sites that organise it all in different ways but whicheve one your note is found on, you as the creator can see the likes or zaps or comments from all of them. The other sites are just displaying them in different ways. But if we start building things in the middle of that, instead of incorporating them at the protocol level (zaps, paywalls, media files, whatever), then the middle bits become necessary to its functioning, not direct creator-reader-protocol for the whole network wherever the notes are found.
Right, no, everything goes down to the protocol level; clients should always be largely stateless (besides keeping a cache for performance optimization)
Wonder how that’ll impact seo. Habla would have to set up proper canonicalization
it's planned, will use the events metadata to serve proper OG tags for naddr URLs
NOICE
i also support human-readable URLs using nip-05 + d tag, so you can use d tag as the article slug https://habla.news/verbiricha@snort.social/references now i realize i need to support _ usernames 😹
yes, please! (see my nip-05) 😅
Right, this is kind of what I mean. You need a site to plug in to Nostr anyway (client, website, app, etc). And the clients send text messages arranged in a certain way to postgres databases around the world. You can do one (client)-to-many (databases) publishing with a click, which is innovative. Now people are quickly relating zaps to posts, which will be like rocket fuel and is very innovative. But we still needs lots of the existing Internet for it all to work (postgres, AWS, ligthning, etc, etc). So I am still wondering about the core of the Nostr idea, I guess.
You’ll have so many client options that the average person will not need to worry what to use to write on nostr. Even clients not catered to long form content will do a good job of displaying it. Already working on this.
yes, nostr doesn't negate the fact that we need internet infrastructure, like AWS and databases, etc.
what it negates is the siloing of content; you can't interact from twitter with content in facebook, because, even though it's all powered by the same infra (databases, etc), they are constrained to their own domain.
Nostr makes it so *all* content (not just social networks) can be interoperable.
Nostr superpower is distribution
Right, that's a good way of framing the question. What is Nostr's superpower compared to all of the other stuff that already exists on the Internet? Whatever the answer is to that question should be the focus. For me looking at it over the past few weeks, the answer would be something like protocol level + relays + zaps. That's it, that's core, the engine, the increased flow. All of the value exchange bits need to be hard coded as it were at the protocol level, so that no one client site, now or in the future, can control that either.
I’d add a 4th - experience. Each client can offer a very different experience with access to the same content. While “protocol level” covers it at face value, the impact of those experiences might be transformational in and of itself.
Right, but if it's a protocol level core superpower thing, we're talking about, the protocol level needs to enforce its core in some way across the whole, in whichever clients are built for whatever experiences along the way. I would argue the value exchange bit needs to be in that core, right alongside the content message bit. Otherwise different clients will own different ways of doing value exchange and if they have access to the content from one of the relays, perhaps in some manner unintended by the creator, etc, etc. If it is direct reader-creator with no intermediaries necessary across the whole network, that would be big.
Nah, the nostr superpower is peer pressure
Just look at zaps
Which wallet had the balls to say "nah, simple sats are more private and cannot be faked, we'll stick with that"?
Which user had the guts to say "nah, I'm good with my normal LN Address, no need to advertise the sats I send or receive"?
Few
Very few
Don’t strictly need those things, it’s the best tool for the job now. Lightning needs a ton of work but is super impressive, the level of improvement that can be done there means it will stay and be integral, clouds and dbs are irrelevant.
This is a hydra. It doesn’t matter what the DB is or where it’s running, you can’t chop off all the heads to bring it down nor can you corrupt the money.
No-one can censor your journalism here nor anybody else’s, and no-one can stop you getting paid.
Right, something like that. If the value exchange bit is coded in at the protocol level too, it will work. Maybe even some protocol level way of telling a client that you can't have this note/full note unless your client implements the value bit too. The protocol should enforce its core in some way.
yeah, that's coming
all these functionalities are being built at the protocol level, clients might choose to support them, or not; most clients will probably not support all features and that's a good thing.
hmmm, interesting; in this case, what is the canonical though?
Well, If you are using Habla to write and publish to your website, then Habla would have to be canonical to your “blog”.
There are all sorts of things to think about before we get to anything like Wordpress or Substack "on Nostr". It's just more entries in more postgres databases (with relays and clients on top). Publishers will want to control their content. If we're talking bloggers and new sites, most of it is already probably in a postgres database somewhere. They are going to be worried about controlling their content if it's going to relays run by other people, etc, etc. X on Nostr vs. X plugged in to Nostr.
Can anybody please explain to me how this works?
blog posts are stored on nostr relays, habla.news, or any client (like your personal website) can pull the data and display it there
So basically I could make a WordPress style blog, but via Nostr?
Still don’t understand where habla.news fits in the picture