nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft hmmm it seems the formatting or the url is not quite correct here? I published this highight from highlighter.com as a note (repost if I'm correct)
https:://highlighter.com/e/nevent1qqs2mmkmvggqpr0vdfye26lujc7utmtqr7prxjraq4ssxe6mg5x96nspzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtczyqrx8x3cdjwpq9ppwc3ve085pyyvfudqcvlz87xk668540m9t78hzx5gfzv
Took some time this morning to build a preview of the note you could cross-post when you submit a link on nostr:npub12pj5g0370uz3f49flpz8scs85p8s9c7l6ueutjhkyc3jnggrlafsmmljva 
The description is missing here, I still need to work out that element but it's cross-posted as you can see here in the note:
Meet Me On Nostr
This is an (web) app for sharing Nostr with your friends.
Being build by nostr:npub1manlnflyzyjhgh970t8mmngrdytcp3jrmaa66u846ggg7t20cgqqvyn9tn
If you would like to learn more about this project, you could listen to this Hatching Ideas podcast episode: [https://wavlake.com/episode/441d2d08-1886-4535-a89e-927897b1c3ad](https://wavlake.com/episode/441d2d08-1886-4535-a89e-927897b1c3ad) where ManiMe is sharing his thoughts on onboarding friends in the Nostr ecosystem with nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424
🔂 cross-posted from https://ccns.nostrver.se
Debugging the CCNS crosspost feature from my local dev environment here, rewriting some NDK stuff #NostrDev
🔂 cross-posted from https://ccns.sebastix.dev
Don’t forget to sleep!
[nak](https://github.com/fiatjaf/nak) is an awesome command-line tool written in Rust (jk, written in Go) for doing Nostr stuff. I use it on a daily basis to talk to relays and gather events.
Using nak, you can sync your data between one relay and another like this:
```sh
nak req -a
```
For example:
```sh
nak req -a 0461fcbecc4c3374439932d6b8f11269ccdb7cc973ad7a50ae362db135a474dd wss://gleasonator.dev/relay | nak event wss://slime.church/relay
```
This downloads all data by the **author** (`-a`) from relay 1, and pipes it into relay 2.
Most relays only return about 100 events at a time, though. To sync _everything_ you will need to implement some sort of pagination with `since` and `until` filters.
Most commonly I just need to sync my profile data to a new relay, which can be done with the `-k` (kind) flag. You can pass multiple `-k` flags, eg:
```sh
nak req -k 0 -k 3 -k 10000 -k 10001 -k 10002 -k 10003 -a 0461fcbecc4c3374439932d6b8f11269ccdb7cc973ad7a50ae362db135a474dd wss://gleasonator.dev/relay | nak event wss://slime.church/relay
```
This will migrate your profile, your follow list, your relay list, your mute list, pinned posts, and your bookmarks to the new relay.
If you find yourself doing this often, you can drop a little alias in your bashrc/zshrc:
```sh
alias nsync="nak req -k 0 -k 3 -k 10000 -k 10001 -k 10002 -k 10003 -a 0461fcbecc4c3374439932d6b8f11269ccdb7cc973ad7a50ae362db135a474dd wss://gleasonator.dev/relay | nak event"
```
Then you'll just `nsync
NAK is really cool indeed
And this sync options reminds me of the drush sql-sync command I use very often to sync db data between Drupal instance 🤓 https://www.drush.org/12.x/commands/sql_sync/
An amazing video showing how you can sign notes cooperatively on nak using musig2, now with 4 signers instead of the boring 3 from the previous video:
https://cdn.satellite.earth/4ca2815dfe2c4f21506e36b1c1c294ef3d372d7b2f846c69a4954e54fdd2a2ea.mp4
Nice work sir, this could be handy in some community consensus models
Nostr is mentioned here quite often, in a very neutral friendly way
Tomorrow my oldest daughter will celebrate her 5th birtday. So we're quite busy... Quickly worked out a stamp card with the activities for her friends she will do at her party 
in #PenPot (selfhosted Figma alternative) 🤓
👇🏻
nostr:note1r98kdztussnt3elj0rpu6v5gr0386dutp48ue5hmnzzny5mgfzvq4vvt06
nostr:npub1f4faufazfl4cf43c893wx5ppnlqfu4evy2shc4p9gknfe56mqelsc5f7ql has a really good article about nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m’s leaving the Bluesky board, support of Nostr, and the recent interview.
I mostly agree with the article but I think there’s more than just that Bluesky is taking on a corporate platform prespective with the roll out of the atproto. It’s that Bluesky is engaged in a kind of closed protocol design that feels heavy like xml and java. It’s open source like Android is…
My hope is that nostr:npub1pu3vqm4vzqpxsnhuc684dp2qaq6z69sf65yte4p39spcucv5lzmqswtfch can be the super easy to use for normies app for Nostr. We’ve got a much bigger and more interesting ecosystem of apps. Nostr is a lot easier to work with than atproto for developers. But it’s also super confusing to new users. Wallet setup is hard, registering a username is hard, understanding how to login to nostr web apps with browser extensions is hard. We can solve these problems, but it takes work.
We’re about to launch the creator and journalism residencies to help bring a diversity of content beyond our core bitcoiner community which is sustaining Nostr.
Take a read:
Techdirt article on Jack, Bluesky, mentions nostr a wee bit - written by a bluesky user.
I think Jack commenting that bluesky has attracted a 'very very common crowd' comment gets unfairly interpreted whenever I've seen it mentioned. I think he assumed a bit of reading between the lines? Well, I'm interpreting it as meaning the very very common 2010s Tumblr / Left Twitter positions and posturings - a pastiche kitsch protest punk rock sanctioned by HR departments. The mandatory positions you have to adopt to get art grants. Very very commonplace?
Eg:
nostr:npub1wmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqhjg240 nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m
(Maybe I've got this wrong lol)
#asknostr
It's a great written article. I still don't exactly understand why BlueSky perse had to build a Twitter alternative as the author nostr:npub1f4faufazfl4cf43c893wx5ppnlqfu4evy2shc4p9gknfe56mqelsc5f7ql states. I think that's something I agree with nostr:npub1p7fw7hcnf2sff3gvjjxdxc8utfr4fg3qvh5jedgffe6ggjczdh8ss7vf3w. They better focused on building the protocol. Now with the protocol and the service (bsky.app client) it will face the same problem as happened to the mastodon.social instance by the founder of Mastodon Eugen Rochko. It's kinda the same problem we see nowawadays with the biggest relays coupled to the most-used clients like Damus, Primal and Snort. I predict many new bigger relays will popup in the future coupled to yet to be build clients with unique killer features.
My love for Nostr is still the strongest. The most open, easy to use and community built protocol. We're very very early. Both protocols are walking their own paths, so I rather not try to compare them. I don't like to 'fight' or debate too much on these topics, as we're all following the same purpose on the long term. Just let us build the change we would like to see.
Techdirt article on Jack, Bluesky, mentions nostr a wee bit - written by a bluesky user.
I think Jack commenting that bluesky has attracted a 'very very common crowd' comment gets unfairly interpreted whenever I've seen it mentioned. I think he assumed a bit of reading between the lines? Well, I'm interpreting it as meaning the very very common 2010s Tumblr / Left Twitter positions and posturings - a pastiche kitsch protest punk rock sanctioned by HR departments. The mandatory positions you have to adopt to get art grants. Very very commonplace?
Eg:
nostr:npub1wmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqhjg240 nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m
(Maybe I've got this wrong lol)
#asknostr
Going to read all this in a moment! 🤓
https://bsky.app/profile/rabble.nz/post/3ksgqh537os2i
https://bsky.app/profile/mmasnick.bsky.social/post/3ksfhvpvdyc2h