With the reference gun implementation, clients would also replicate data and sync both ways by default.
nostr:note1gam822lz08ae252dstr3uc6ag3xkggzun4qj95wmg3a997ww0w8qzcl3za
I also had issues with performance and reliability.
But in the old Iris which used gun, you could easily delete messages, unlike and un-repost!
And you could follow / unfollow people without rebroadcasting your whole 100 kb follows list, which might even overwrite some old version and lose follows.
I'll take a look.
GunDB is a great idea, but the implementation was very difficult to work with when something didn't work and you had to look under the hood.
Also the protocol was such that making your own implementation was quite difficult. But definitely the concept is good.
I don't like new event kinds. They make building a nostr client more difficult.
I'd like to build a gundb-like universal database on Nostr where you write to filesystem-like paths such as group/[id]/messages or group/[id]/name instead of defining new event kinds for everything that could expressed as a path. https://github.com/gundb/gun
Nostr is not going to be an "everything app" if you need new event kinds for everything.
I'm quite busy improving the very basic features of Iris, but I'll try to find time for it at some point.
Not to forget
Coding music
It's an old Finnish folk song that was performed by Loituma
https://www.youtube.com/watch?v=nbAHzYQIf40
and made famous by the "Leek Spin" video:
https://habla.news/ttdr is a writer and journalist from Shangai. nostr gives her a platform where she can receive payments from readers all over the world and her speech is not censored.
Is there some way to get the user's public key from that url?
Oh, right, it's probably not visible in mobile size or low brightness screen. In the 2nd picture there's a subtle 1 pixel border on both sides of the middle column.
Better with or without the borders between columns?
So nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx gave an absolute masterclass on the problems with Musk's current Twitter approach on WBD, starting at the 17m mark. It's a great advertisement for Nostr and I recommend everyone watch it.
https://www.youtube.com/watch?v=-Ms-dE6aasA
I've been retweeting or reposting Odell's various observations on this topic for a while and so I'm happy to share this too, including on Twitter today, even as a filthy blue-check myself.
Where I disagree with Odell (slightly) is on tactics. He thinks people should give up blue checks in protest. And that's a very fair position. I don't disagree, especially for someone like Odell with a purist position and a generally cypherpunk audience.
But I think there are multiple successful paths on this. I have always been a Twitter fan, and my normie audience is there. I wanted to be able to pay for better UX and anti-impersonation defenses for years before they became available. Just because Musk is running it doesn't mean I won't pay for helpful services, especially if they protect my audience. Real people lose money to Lyn Alden impersonation scams if they can't tell my account from others, and I directly hear from them when it happens. It's always heartbreaking.
So, I'm on the offensive, not the defensive. The way I view it, unless or until someone censors me on Twitter, they're locked in there with me, rather than me being locked in there with them. If having a blue check reduces the success rate of impersonation scams and amplifies my reach at calling out Twitter's problems, I'll have the blue check. What I absolutely *won't* do is change what I say based on a blue check. If anything, I purposely overdo it to the opposite and exaggerate my criticisms on purpose to push back against platform incentives.
Two simultaneous approaches:
1) Call out the problem on Twitter. Don't give Musk a pass. Point out that a pro-freedom, pro-anonymity view doesn't match with what is going on there. Don't let his rhetoric disguise his inaction. If Twitter cares about freedom and anonymity then they will offer a paid option that doesn't require identity (e.g. the "orange check" bitcoin payment.) Until something like that, they are LARPing and are fair to criticize as such.
2) Have your foot here on Nostr and on decentralization technologies generally. In the long run, I think this is the future. And more importantly, I hope it is.
Episode sponsored by https://irisenergy.co/ ๐ช
Glacier National Park, Montana. I want to go there some day, looks like one of the most beautiful places in North America. Unfortunately the pic is not mine, it's from my "cool pics from the Internet" collection ๐
Just fixed a massive memory leak & performance issue I had introduced to Iris. My phone doesn't overheat anymore.
It's still not great, but thanks to the OpenSats grant, I'll be working on it!
ไพๅฏ
nostr:npub1wnwwcv0a8wx0m9stck34ajlwhzuua68ts8mw3kjvspn42dcfyjxs4n95l8 nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk
Hello! Why is lightning.gifts url:s broken in Iris?
Regex thinks it's a .gif image url ๐
Yes, you can select "Nostr extension login" in the login screen
Check out https://beta.iris.to . Featuring better content loading and option to turn off replies & reactions, images etc.
There's just some UI freezing that someone needs to fix before moving to production. Seems to not happen when you turn off "Ask events from relays" from https://beta.iris.to/settings/dev
#[0]
I'm a bit jelly to native app developers for SQLite. Yeah, there's sql.js but it doesn't persist anything. Juggling between storage and memory (and relays) is the difficult part.
That said, LokiJS, Dexie and Fuse are great javascript libraries with zero dependencies.
Backed by LokiJS, Iris now has some basic filtering tools, and will be adding more.
Also need to get a Tauri desktop & mobile version done at some point, so we can be independent of DNS, hosting or someone pushing a version that breaks the UX for everyone.
๐๏ธโ๐จ๏ธ
Added zaps to Iris. Thanks to #[0] and #[1] for letting us use code from Snort!
It's not quite polished yet and zap type selector is still missing. I'm also noticing that zaps don't appear in the listing immediately. Working on it.
I wanted to do fun things instead of useful things, so I added the option to view a profile feed as an image gallery.
Just pushed a data subscription update that should reduce bandwidth and CPU usage. Lmk if it works well or degrades content loading. #TestingInProduction
GM
Yes. Any xcode protips on how to enable lightning: link external handlers?
Following / posts feed jumping should be fixed now. Replies to posts were removing the replied post as a "duplicate" also from the posts feed where the reply wasn't visible. Sorry for the bad UX ๐
Zap listing and content filtering by follow distance are on the backlog. "Freedom of speech doesn't mean we have to listen."
PV! Just pushed a major refactor of the Iris codebase. Removed a big chunk of unnecessary code and depencencies, and broke down large files into more manageable pieces. Let me know if I broke something in the process.
There's not much visible change to the user except for the faster loading search box, but the codebase should be much less obscure for contributors now. https://github.com/irislib/iris-messenger
One issue I'm noticing is that Following / Posts feed starts pushing old posts after a while, looking into it. Also sometimes you get a black page when loading some url. That's because of StaleWhileRevalidate caching and needs to be fixed somehow.
Hoping to get zap listing done soon, then zapping, then some updates to the mobile apps. Then maybe user lists and custom feeds.
Thank you! Does it freeze when you click "settings" or on some specific view? Do you see some related error in the console? Haven't noticed that bug before.
Merged a pull request that lets you post messages by pressing ctrl+enter. In fact, I'm posting this message using it. Thanks for the contribution!
I think "zaps" is public listing of payments?
note1zrylky0hgtndcpwch0954aus53zn7x7qgmjqegd48pved33ajwaq8vgn4f
Sorry for the hideous dropdown layout btw, I'll replace btns with links some day.
Nostriches!
That was amazing! It took us less than 12 hours to complete fundraiser for @npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk !
#Nostrica will now be even more fun with https://iris.to represented!
Thanks to everyone that suppoted on backend: Bas, @npub1sa2aset30x2zs5dlgxaegcnlyg4sxtpd0u0p8gegzaphpxmnvmwszy6ced , @npub16vrkgd28wq6n0h77lqgu8h4fdu0eapxgyj0zqq6ngfvjf2vs3nuq5mp2va , @npub1z4m7gkva6yxgvdyclc7zp0vz4ta0s2d9jh8g83w03tp5vdf3kzdsxana6p , whole Chicago BitDevs crew, @npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 , etc, etc
And of course - the most importantly - thank all of you who donated! Keep your onchain/lightning receipts and show them to Uncle during nostrica.com as ticket for Rockstar parties ๐
See you all March 19-21 in Uvita โค๏ธ
Pura Vida!
Thank you so much! #Nostrica will be epic, really looking forward to it ๐
Block list sharing solves that
Thank you @npub1j8y6tcdfw3q3f3h794s6un0gyc5742s0k5h5s2yqj0r70cpklqeqjavrvg !