That's the way!
nostr:nevent1qqs9y85kcafguv7g6dkzr5q60uk6vjg46c9ty3ah0mn3ckl3jmjxmscppemhxue69uhkummn9ekx7mp0qgsre75pdw6gjtaxh6vn43e2nlxmkzymm6svtkgprlfqf52523069kgrqsqqqqqp9qs9ca
Removing READ MORE should be easy with code injections - try this:
<style>
.post-footer .post-more {
display: none;
}
</style>
It's much harder to add reaction/zap counts - existing themes don't support that. I understand that it's a pretty common feature that people would expect to have eventually, so it's on the roadmap, but we haven't figured out an elegant way to achieve that yet.
Thanks!
Relays only search for exact match. So for us to find a post, general rule is would need to specify exact unicode string. But there might be exceptions - some clients would add uppercase and lowercase version of the tag you post, which distorts the picture and makes you think that things work some times but not others.
It's a complex problem across apps, so for now please include exact tags.
Yes that's possible! Although zap splits are only convenient when you have extension or NWC wallet connected. In the future we plan to experiment a lot with zap splits and built-in ecash wallet, there are many things to explore including creating incentives for curators with zap splits etc.
Hi, I understand. It's awesome how you're experimenting with the collaborative blogs!
I agree that content management there can be a challenge and it's not even clear how to do it right:
1. You might want to specify included hashtags per author - different for every npub.
2. You might want to "map" some hashtags to others on the site - your proposal above.
3. You might want to be able to edit metadata of each post to "reassign" it's hashtags etc.
4. You might want to just manually add all the posts you need without relying on hashtags for filtering.
The last 2 points seem like the most versatile - you can achieve anything that way. But it's a manual process.
And automated options usually have limitations - eventually you'll want even more customized filtering.
I'm happy to explore these options with you to figure out the best way to build collaborative blogs!
15 seconds might be for the self-hosted client-side-rendered version. I agree it's very slow, and it can and will be improved, it's just not our priority at the moment.
Our architecture is quite different from Nostrudel, our pages need the full data set loaded to generate proper HTML using a theme, vs Nostrudel that has no themes and can update parts of the page while receiving new events and thus can start showing you stuff much faster. We also have much higher expectations for coverage - if Nostrudel misses some events you won't notice and won't be too mad, if we don't show one of your posts on your site - you will 100% notice and report a bug. So we can't just copy what Nostrudel and others do, we have to figure out our own way of loading the necessary data as fast as possible.
We'll get there, but it will take a while.
Great question! We could do that right now selectively manually using code injections. Ghost themes do have some support for internationalization, but we haven't used them and will take a while to figure things out here. That's on a longer-term roadmap.
If there's a production site that needs translation please reach out, will try to help with manual translation.
Right now there's no way to exclude hashtags, you'd need to manually mention included hashtags. But exclusion hashtags looks like a pretty simple feature, adding to the todo list, thanks!
You can create any number of sites from 1 npub, just start from homepage by choosing a theme. There's just no "create site" button in admin panel yet, will add :)
Looks like your site should be there at atyh.npub.pro and hashtags work fine for everyone afaik. Please let me know if the issues persist when you try it next time. Thanks!
Could you please try clearing the cache of npub.pro in the browser, go to homepage, click get started, click "preview" on some theme, then when it opens click "log in". Does it work this way? Thanks
Which app gonna get a nostr website next?
nostr:nevent1qqsr6kjj26rkkdurwsy5k6nxzq6udv4gtjccwl2jlmwyrq62nfv4mcspr9mhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv9upzq0mhp4ja8fmy48zuk5p6uy37vtk8tx9dqdwcxm32sy8nsaa8gkeyqvzqqqqqqy8wjflv
It's actually not trivial to get right, so using an off-the-shelf component could make sense until you build your own solution. I wrote some thoughts on nip46 and nostr login options at nostrconnect.org and nostrlogin.org
I'm not sure what is meant by cache hijacking.
Re. session hijacking we might be talking about at least two things:
- vulnerability inside nsec.app such that someone gets access to your "session" in nsec.app
- vulnerability inside nostr app connected to nsec.app that exposes the app's session/connection info so that hackers can access keys on behalf of the app
The first part doesn't have much surface with nsec.app - we only use server to store encrypted keys and to subscribe to notifications for the signer to wake up. There's basically no "session". And any server-side auth is based on nip-98 which requires a new token signed by your nostr keys for every request, so again there's no "session" - you can only sign those tokens if you steal the main key.
The second part doesn't depend on the signer (online or offline) - no matter which signer you use, it's the app that's connected to the signer that needs to be hardened against session hijacking. That's why it's super-important to not give excessive permissions to any (even trusted) app in your signer, so that potential hackers' access to keys was as limited as possible. Also when connection is established using bunker-url or nostrconnect url we use a one-time "secret" so make sure the connection can't be spoofed and url can't be reused.
I'm not a security specialist, and I agree that a formal security audit would be beneficial. We'll get there eventually.
You can create a file /.well-known/nostr.json on your site and put your pubkey there:
{"names":{"_":"your_pubkey_hex"}}
Pubkey must be in hex, not 'npub' form - use nak.nostr.com to convert.
Then you put _@yoursite.com to your profile into NIP-05 field.
Please welcome Npub.pro!
This is a tool to make yourself a beautiful Nostr-based website.
It's been long in the making, and we're thrilled to launch it on this special day!
Here is a short demo of how you can make yourself a website right now:
https://v.nostr.build/kZG9O.mp4
It's free for anyone getting started, it's open source and self-hostable.
Why get yourself a nostr-based website?
- beautiful themes (any Ghost theme could work)
- great looking shareable links to your content
- works like an app, add to homescreen, useable offline
- SEO-optimized
- attach your custom domain or host yourself
Try it at https://npub.pro
Learn more on our Nostr-based blog: https://blog.npub.pro/post/npub-pro-is-live
P.S. If you like how it looks, that's because @Karnage designed it. Thanks man, it's a pleasure to work with you!
I see "Survive & Thrive in Orange". And it should be "Loving Girlfriends ⚡Zaawaadi & Angelika Grays".
Parse naddr and check that d-tag doesn't match the event you're showing.
Oddbean new post about login | logout
Notes by brugeman | export
Removing READ MORE should be easy with code injections - try this: <style> .post-footer .post-more { display: none; } </style> It's much harder to add reaction/zap counts - existing themes don't support that. I understand that it's a pretty common feature that people would expect to have eventually, so it's on the roadmap, but we haven't figured out an elegant way to achieve that yet. Thanks!You can create a file /.well-known/nostr.json on your site and put your pubkey there: {"names":{"_":"your_pubkey_hex"}} Pubkey must be in hex, not 'npub' form - use nak.nostr.com to convert. Then you put _@yoursite.com to your profile into NIP-05 field.