Someone tipped this client-side javascript lib that could be useful to web clients.
The classifications are hilarious. It could display a warning if your profile pic is too hot.
*so the nip05 address is displayed on your profile
The address works, but you need to add glow@getalby.com to your profile so it works :) Now you have just "getalby.com"
Nip05 record always points to only one nostr account. If multiple nostr accounts point to the same nip05 record, only one of them will validate.
Yes, it should work if you save it into the nip05 field in your profile.
The username that you can change in "edit profile" is not unique. However, nip05 names such as sirius@iris.to are unique.
Scroll bar should be removed now
Added Spotify, Tidal and IG embeds
https://open.spotify.com/track/4i9lLQkiseKbBFg9JBBkld?si=cb214e09778b495d
Spotify embed caused Brave to ask to install some Widevine DRM BS extension. If that's bothering users, I can disable Spotify embeds.
Idk, I'm doing my own iframes
const spotifyRegex = /(?:https?:\/\/)?(?:www\.)?(?:open\.spotify\.com\/track\/)([\w-]+)(?:\S+)?/g;
replacedText = reactStringReplace(replacedText, spotifyRegex, (match, i) => {
return (
class="audio" key={match + i} width="650" height="200" style={{ maxWidth: '100%' }} src={`https://open.spotify.com/embed/track/${match}?utm_source=oembed`} frameBorder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowFullScreen /> ); });
Added Spotify, Tidal and IG embeds
https://open.spotify.com/track/4i9lLQkiseKbBFg9JBBkld?si=cb214e09778b495d
It retains the position if you use back / fwd functions. But yes, it could be changed so that menu navigation also retains.
Iris.to still accessible from China
Some small fixes:
* Remove original post from feed, if original+reply is added
* Fix follow button for newly created users (didn't work before refresh)
* Keep follow suggestions visible until user clicks "Done" or follows 10 users
* Remove https:// and trailing / from urls in notes
* Highlight urls in profile bios
* Don't parse note & npub if they're part of an url
* Same style for youtube & other videos
* Handle iris.to links internally without refresh
lightning:sirius@getalby.com
Iris now supports urls in the following formats:
https://iris.to/sirius (sirius is an iris.to username, not publicly available yet)
https://iris.to/sirius@iris.to
iris.to/example.com works if you have nip05 _@example.com
True, it only works if you have a browser extension or other handler for lightning: urls. I guess it could present a QR code, payment url and instructions otherwise.
Iris now supports urls in the following formats:
https://iris.to/sirius (sirius is an iris.to username, not publicly available yet)
https://iris.to/sirius@iris.to
Nip05 of course
Iris now supports urls in the following formats:
https://iris.to/sirius (sirius is an iris.to username, not publicly available yet)
https://iris.to/sirius@iris.to
Actually, because Iris uses the webcrypto api, it might not work over plain http at all 😬
Should I make the adjective list friendlier? 😆
Actually it doesn't limit the hops — that's why you sometimes still see spam. But maybe we could set the "follow distance" filter on the feed UI level and see what works best.
A bit more quiet on the development front today:
* Fixed invalid note ID queries. You should see less "Looking up message..." now.
* Your replies to notes are now shown first.
* Added missing translation strings, updated some translations by contributors
* Restored different styles for "follow" and "following" buttons
Iris already has a dockerfile contributed by @truxton: https://github.com/irislib/iris-messenger/blob/master/Dockerfile
I can add custom imgproxy and libretranslate endpoints to settings. Then would just need the umbrel packaging.
Pushed a change that shows your replies to posts first, then the original author's replies to self, then other replies oldest first
What started this recent influx of Japanese users?
Oh, and I'll make encrypted paths use hash(path + secret) so it's deterministic, instead of encrypt(path) which has a random component
2018年朝日新聞のインタビュー。
Thank you! I think native apps might have better screen refresh rate so the feel more fluent. But is there any other reason to go native? Native keystore could be implemented to the wrapped apps even if the UI is a web view. Personally, I don't think I would have time to maintain separate web and native codebases.
Copilot makes adding new translation strings a breeze btw. I just add a new key to csv and it makes a suggestion on all languages.
Some of the difference might be due to Iris rejecting events from authors that your social network has no interaction with. It helps limit spam and other unwanted content, but the tradeoff is less liveness.
I just had some essential missing strings like "Global" and "Messages" etc
Can add columns as well! Just use the correct language code in the first row.
Yeah, I have the free version and translations.csv was too much for it. I tried in parts, but then it stopped replying altogether.
Iris translation sheet, please feel free to contribute. Let's see how this goes.
https://docs.google.com/spreadsheets/d/19VSmmqqq5zpOcKIS2H8bHcVeG3Bby5aW8Q_4LykPUao/edit?usp=sharing
I could add the choice of translation service in settings like Damus, and support also non-libretranslate options.
Different relays. Iris also discards content from unknown authors, which is useful to limit spam.
It tries to keep the max number of 10 connections. If one relay disconnects, it reconnects to a random relay from the list.
Are you sure you pasted private key, not public?
It's true that this login flow could be improved.
Looks good on mobile
Light theme is here. Please feel free to pull request improvements: https://github.com/irislib/iris-messenger/blob/master/src/css/style.css
Or search_term, search or query?
Actually nip33 with my own key-value API that could be added to nostr-tools if #[4] wants it https://github.com/irislib/iris-messenger/blob/master/src/js/lib/nostr-tools/path.ts