Awesome! Do you have any plans to support kind 1111 show comments and publish comment as kind 1111? Or can I configure arbitrary another Blossom image uploader?
jb55's avatar jb55
Build 1341 is out! https://testflight.apple.com/join/urLbziKc Thanks to @npub1hs52...5rx4 , @npub1ktnh...7kn3 , @npub1aeh2...4nwx for reporting some of these issues from the last build. Also thanks koteitan for fixing a long-time bug in the composer. • Fixed cursor jumping to the end of the text when pressing the iOS keyboard-switching button in the post composer (koteitan) • A private reply received from another client no longer names its sender as the person it was sent to • Copy note JSON is available on private replies and DMs again, in developer mode • Fix search result highlights making matched hashtags unreadable • Fix the wallet setup screen and the Zap explainer rendering on top of each other • Shrink the tab bar unread indicator to a small dot • Use damus purple for the tab bar unread dot Only 325 testers on this testflight, gotta pump these numbers up folks.
View quoted note →

Replies (6)

AFAIK the whole point is to decrease traffic when on shitty/expensive internet when scrolling over a feed. If that's not an argument, then the point is just to show the comments sent from those clients that have already adopted this.
Yeah, but what happens when most people will start posting kind 1111 only comments and kind 1 only root posts?—It'd be possible for clients to load comments lazily.
You both are replying to my kind 1 root post but it didn't showing up. Mixed kind 1 note and comments are making any client difficult to render them. Attached is my screenshot that didn't showing your kind 1 replies. image
↑