91
page394
9110fe860a5e40a41e03d52d306a7b337ecf32d1090812ceaf423ec9b94954c8

Custom filters on feeds all throughout the app is a better approach. I should be able to filter out any posts by x npub(s) that include whatever keyword I choose. For example if I want only short form #[6]​ content I could set up a filter on his npub hiding ‘lopp.net’ so all his article posts aren’t shown. Or could do same for #[7]​ and ‘meat’ or ‘walk, walking’

What are the ingredients?

Any way to include some data that ‘timestamps’ a note to the current block height? Sounds like something ZK proofs (aka magic) could do, prove a block height timestamp was the maximum block height at the time the proof was computed? Maybe requires these timestamps to be rolled-up and the proof included in that block tho? Time is so…relative.

Maybe use SFSafariViewController instead of sending users out of your app entirely to Safari proper?

!!! I was wondering why sometimes I’d not be able to see what a post was replying to

#[0]​ “Twitter threads are already pretty hard to follow because they aren't nested very well. One feature I like about Reddit, for example, is that I can collapse entire subthreads with a single click if I want to look for other discussions on a given post. The whole threading system could benefit from an overhaul rather than just slapping a naive prioritization rule on it.” -https://blog.lopp.net/a-critique-of-twitter-changes/

Hear hear. Nostr needs help here too. #[1]​ I think this should be a higher priority! Can make the world of difference on actually making conversations and the network stronger.

Agree, why isn’t it simply a user choice, even if the default is on

Replying to Avatar jb55

🤔

Decentralized timestamps are a tricky thing tho.. any way to put decryption info into bitcoin block but can only be read at a future block height? #[4]​ timestamp scholar, thoughts?

Replying to Avatar jb55

shit lol

Lol but this could be a cool automated raffle program if you ‘sold’ fixed denomination zap entries and chose a random one to win. Say you need to submit the zap on a particular relay to enter, find some cryptographically random way to select a winner from among the zaps, could be built into the app open source like a poll or any other type of unique note… but if I were you I’d not build or operate this except as a nym; see history of satoshi dice

Paid for with your own money no matter the size or up to the amount gained from non winning zaps? This is like a lightning powered raffle drawing!

This is certainly not optimal and I hope it doesn’t stay this way