1st a mini earthquake, then a solar eclipse, and tonight #AuroraBorealis?? The Northern US is getting spoiled with super cool natural phenomenon this year!
If you want to see a list of Nostr profiles that have bridged over to Bluesky so far, go to this search and tap on the "People" tab.
wss://relay.momostr.pink isn't my relay, I haven't been able to find the nostr profile of the creator/operator of that relay. On the main site, they do list this contact email: hhrjfshng@mozmail.com
and for those seeing this post from Mastodon, to bridge your Profile/Posts over to Bluesky and Nostr:
1. Follow @bsky.brid.gy@bsky.brid.gy
and for those seeing this post from Bluesky, to bridge your Profile/Posts over to Mastodon and Nostr:
1. Follow @ap.brid.gy:
To bridge your Nostr profile/posts over to the Fediverse/Mastodon 🐘:
1. Add wss://relay.momostr.pink to your relays
To bridge your Nostr profile/posts over to Bluesky 🦋:
1. Follow nostr:npub1pqr3g2gk3vsnrqk9kwfqqcxc6d5cwjr0hyc0nlzz9py5nf92vd9sn02sck
2. Add wss://relay.momostr.pink to your relays
What client are you using to load file blobs from relays like this?
Except they use Portuguese spelling so it would be Ramires :P
It seems you need to follow nostr:npub1pqr3g2gk3vsnrqk9kwfqqcxc6d5cwjr0hyc0nlzz9py5nf92vd9sn02sck for your nostr profile to federate to Bluesky
#Bluesky accounts have officially begun bridging over to the #Fediverse thanks to @Bridgy Fed for Bluesky , which means Bluesy accounts are now officially bridging over to Nostr thanks to @mostr and momostr.pink!
For example, here’s my Bluesky account bridged over to nostr:
nostr:npub1k4lkcd596rwmruw2axmyfvenm76t9s0y50lk4pyt73w8fpy8uk5s9w8sr6
This is built-in to nostr:npub16heelc6crh3ggnpmzwd97pcf4eeqewu9wak7hfe9fkh0f3p00cvq6xz8zz , meaning if you search someone's Bluesky handle (boles.bsky.social) it'll automatically load the bridged version!
Great work nostr:npub1ytxpw5ef4heklqnjma05fzc2gyunwp2q53dj2tu349r9vvmuvseslu28uf
and here's my Nostr account on Bluesky, so friggin cool!
You may need to connect to the relay:
wss://relay.momostr.pink
and it does indeed go both ways!
here’s your nostr profile on Mastodon: https://agorasocial.app/#/mastodon.social/a/112128150569511730
and your bridged profile on bluesky should have this handle:
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6.momostr.pink.ap.brid.gy
but it doesn’t seem to have federated over yet. i think you need to follow nostr:npub1pqr3g2gk3vsnrqk9kwfqqcxc6d5cwjr0hyc0nlzz9py5nf92vd9sn02sck for it to federate
Looks like ditto.pub is down?
#Bluesky accounts have officially begun bridging over to the #Fediverse thanks to @Bridgy Fed for Bluesky , which means Bluesy accounts are now officially bridging over to Nostr thanks to @mostr and momostr.pink!
For example, here’s my Bluesky account bridged over to nostr:
nostr:npub1k4lkcd596rwmruw2axmyfvenm76t9s0y50lk4pyt73w8fpy8uk5s9w8sr6
This is built-in to nostr:npub16heelc6crh3ggnpmzwd97pcf4eeqewu9wak7hfe9fkh0f3p00cvq6xz8zz , meaning if you search someone's Bluesky handle (boles.bsky.social) it'll automatically load the bridged version!
Great work nostr:npub1ytxpw5ef4heklqnjma05fzc2gyunwp2q53dj2tu349r9vvmuvseslu28uf
Quiet looks super interesting, it's like Discord/Slack but actually decentralized/P2P. Messages and content are synced between devices using IPFS/OrbitDB and connects made through Tor.
I made a Nostr community on it as an alternative to using Discord for Nostr dev discussions:
ah i see what you’re talking about, thanks for the heads up
Was thinking about this the other day, and it inspired me to start working on what I call VibeTag.
The idea behind it is to be able to tag any content on the internet with a “vibe”/“sentiment”, whether it’s a nostr post, something on Mastodon, Twitter, even entire websites.
This will initially focus on whether the sentiment of the content is positive (informative, funny, etc) or negative (misleading, rage-bait, vulgar in general) etc.
As more and more content is tagged in either direction, it learns what words/phrases are associated with positive content vs negative. The tags and info about associated content would be synced across content through the beauty of Nostr relays.
This essentially allows there to be a straightforward algorithm that you can take with you across the internet that automatically generates/updates a list of words associated with shitty content and hides it from view.
This is something I’ll be integrating into nostr:npub16heelc6crh3ggnpmzwd97pcf4eeqewu9wak7hfe9fkh0f3p00cvq6xz8zz but also will be a library anyone can integrate into their project! nostr:note19aldr26lyw2lqatcgqscyt3kpq76hcpwtwmglypvqqgx3m27fsaswa8rr6
Hmmm I find this part the most intriguing:
"Syncing: IPFS and OrbitDB, an IPFS-based CRDT, ensure that all data (messages, user data, etc) syncs between peers with eventual consistency.
Asynchronous messaging: because messages sync to all members, members can communicate without being contemporaneously online, provided that there is "continuous liveness", a continuous chain of online peers who each sync the latest updates, between the sender and the recipient."
This kind of sounds like how Scuttlebutt works, but using IPFS+OrbitDB so perhaps the performance would be much better?
things i realised while developing nostr:npub14a3s46a8mr8kar9duvfzd2gz8sntjxcykwslyx84dfnexfzfdzhqz4ejtd for last 8 months on nostr.
one thing i have realised.
- Not a lot of dev resources online other than GitHub read me and handful of very basic videos.
- Telegram groups are your most accurate source of information.
- By the time you get hold of NIPs and get busy developing your app, either new NIPs come out or previous implementations change without any major announcements. unless you are actively monitoring nostr social feeds, no specific newsletter you can subscribe to mentioning the changes in NIPs you are interested in.
- Help is hardly available. No volunteers, No major Sats contributions, cant run ads. Even if there is no backend, hosting relays or creating something meaningful is gonna take a toll on your pocket.
- Community is helpful. Some people really love to test your ideas and give suggestions (like nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac ) but otherwise, its you and your own vision of a service.
Overall, No guarantee of if its gonna work out in the long run or not.
Creating on nostr is supposed to be more fun. That’s why we are creating on nostr and not a centralised API driver another app like billion others. However that really seems to be getting tougher and tougher.
I do not wanna lose hope. Some apps really have made their names and i feel glad everytime i see a new app rocking on nostr and utilising its potential to build cool features. however, it seems i took a bite bigger than i could chew. I am not gonna stop though. Even if the chewing takes longer, i am in it for the long run.
When has it not worked in the end after all right?
#HappySundayNostr.
> By the time you get hold of NIPs and get busy developing your app, either new NIPs come out or previous implementations change without any major announcements.
Here's an RSS feed tracking closed issues in the NIPS repo:
https://openrss.org/github.com/nostr-protocol/nips/issues?q=is%3Aissue+is%3Aclosed
Very true. That’s why i think if this sort of thing is implemented, it should be in the form of specialized relays that accept file blobs, that way it can be an explicit decision of whether or not to accept those kinds of events.
What ever happened to these discussions around storing files directly on relays (those who choose to accept file upload events)?
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr:npub1l56z85xvaplh3033l8h2x9thypamu0d2hyqnxkw0ujuntqm8asaqh99sza nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj nostr:npub1skfmmcet2244yx8xn5xjfcmwg3u4mcjdndpd2gcjkq4qfycm6xtql0xa7d nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn