"The next big thing always looks like a toy at first"
Just say the word ✍️
nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc gave me the best shirt of the modern era
🤣 love this
Gen-z is now using deepfakes to teach each other calculus.
https://video.nostr.build/884ea61d8b479ffd4d5fef41112a947fce62d8acf693bb7107582c5478c976d0.mp4
I need more of this 😂
Doesn't say much yet indeed! Very curious about this, a loooot of unanswered questions that this could shine light on.
The baseband nor any other radio does not have access to the RAM on the devices. They are isolated components via IOMMU and they're explicitly part of GrapheneOS' device's security and hardware requirements:
https://grapheneos.org/faq#future-devices
Cellular radios have always been isolated in GrapheneOS supported devices, even down to the first two devices we supported (Galaxy S4 and Nexus 5). It's a misconception cellular radios have privileged access to the OS or memory.
A long time ago Broadcom Wi-Fi radios worked the same way it did on laptops without having proper isolation but that was resolved on the Nexus 5X, and was never an issue on Pixels to begin with. Cellular was never more privileged than Wi-Fi, and in fact on several of the early devices Wi-Fi was not properly isolated via IOMMU (such as the Nexus 5, Nexus 9 and Nexus 6P), but cellular always had been.
Thanks. Appreciating Graphene even more! 💜
Too much fun ecash talk. Wee hours of the morning and not sleeping yet.
💤 rugged 💤
nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8
nostr:npub1u8lnhlw5usp3t9vmpz60ejpyt649z33hu82wc2hpv6m5xdqmuxhs46turz
nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg
Great episode guys. ❤️
Noob question: Why exactly could the NSA have access to full RAM on Graphene phones?
"Zap me to get a share of my zaps"
And you've got a pyramid scheme 😉
Favorite bitcoin review so far. Insights:
- ecash = lightspeed-fast bearer token, can be useful at any project-scale
- pears.com = SDK and NOT an open protocol, hypercores are very useful P2P tech though #stealit
- npub = lightning address, whether you know it or not
- npub = no need for DNS
- JSON first for adoption, but binary = inevitable
- Coldcard Q + Satslink + ecash = Star wars
Maybe my favorite movie ever.
https://archive.org/download/the-fountain-2006/The%20Fountain%20%282006%29.mp4
Wait, this IS the movie!? Haha, awesome 🤣 thanks sir!
What about Long Press? Would that work for you? Or too weird/slow?
Long Press Maxi #prototype #nostrdesign
https://cdn.satellite.earth/38e06c7fffa1811ad5e660855b68e4475ffc738d08bbad8c6a2b569e9497c8b5.mov
First chapter sure is 🔥 ! Thanks
Teaseeeer! 👀 👀 👀
I'm asking because I've got a strong feeling these same questions will be asked about:
Login forms, Telegram-like chats, Profile pages, Modals for DVM selection, Videos, Image carousels, Settings pages, Modals for payment/subscription flows, Comment sections, Reviews, Skeletons, Icons, etc...
Knowing that:
1. They will all need to be responsive and look good together.
2. That few devs really want to spend time on these because it's not the core of their app.
3. That I would just get these right once, copy-paste them and change the accent colour and the logo. And I would then see 10 different people build 10 very similar components in a very sub-optimal way, using 10 different component libraries that don't really fit Nostr apps.
4. No dev wants to do all of this again for an android app or another platform.
5. I do not personally care if some apps look kind of similar in this bootstrap phase of Nostr. Especially if it makes them work better, be more beautiful and if it adds recognisability and usability for the users. If it for example has flows like this built in: nostr:nevent1qvzqqqqqqypzp22rfmsktmgpk2rtan7zwu00zuzax5maq5dnsu5g3xxvqr2u3pd7qy88wumn8ghj7mn0wvhxcmmv9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qqsw5wrq7wet9z3srlydj62jdqav6y0u9lymtls0pf327jhgawmkgwqnay5dl
So, all of this to say it might be time for me to get serious, find some collaborators and make this a thing.
(built on NDK for web, at first, and adaptable with Tailwind CSS, then Android)
I want to see guys like you, nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft, nostr:npub1arkn0xxxll4llgy9qxkrncn3vc4l69s0dz8ef3zadykcwe7ax3dqrrh43w, nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9, nostr:npub1gzuushllat7pet0ccv9yuhygvc8ldeyhrgxuwg744dn5khnpk3gs3ea5ds, etc... focus on what you do best instead of trying to get pixel spacings and slide-out animations right.
And more importantly I want apps like Nostrocket, Yondar, Zapstr, Highlighter, Zap.store, Vendata, CollabLemon, Nostree, ... to be badass asap.
I started laying the groundwork for the design system over here: https://www.figma.com/file/1bvslVfr7akG1C6Qo8dgWK/INK?type=design&node-id=0%3A1&mode=design&t=DBp2QsF4kmoGRmNm-1
Do you think this is a good idea? Or is this too #cathedral? Please devils-advocate me on this 😉
#nostrdesign
Don't just copy YouTube.
https://cdn.satellite.earth/269940b5122dc2ddddb2c590e39a4f0fcbe7f7a75a1f09b92e8094adbfcee951.mov
1. We have zaps 👉 Show them and give zappers recognition
2. Unlike on YouTube, you have friends 👉 Show the friends that commented
3. We have interoperable lists 👉 Showing what Lists the video is part of is huge for discovery. It's the main reason why I still go to sites like IMdB. And that's just random people making random lists shown in a random order. #nostrdesign #prototype #OnlyOnNostr
Is it for nostrocket?
Would a great looking Nostr UI component library for Svelte and built on NDK help, if you could just import { Article }, set it to "basic", provide the eventid and be done with it?