It seems a lot of nostr adjacent apps have gone the route of creating a service that uses nostr. What we need are more tools to host your own content at your own domain that uses nostr. Instead of zap.stream and flare.pub we should have an app that the user can run and when hosting it, they can place their own content in their own webserver and the program handles nostr events for them. Sorry but if you're using zapp stream or uploading videos to flare.pub you are trusting those services to store your content. nostr will not protect you if the servers hosting your content goes dark. Put it on your own computer.
Nothing against these apps in particular. Just examples. We need them too and I'm very greatful for everything nostr:nprofile1qqspwut66nfqu2jztndq5gv4vf9q5jnncnmfwhckk9vnljrl53hj6kqppemhxue69uhkummn9ekx7mp0qy88wumn8ghj7mn0wvh8w6tw9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tc0rh42p and nostr:nprofile1qqsx8lnrrrw9skpulctgzruxm5y7rzlaw64tcf9qpqww9pt0xvzsfmgprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshssfnq7m have contributed.
Ps...fuck we still need a good solution to Icann DNS registry. I guess everyone can have jumbled onion links...
True facts.
I thought Microsoft backpeddled on recall after its userbase made known that there is a limit to the type of privacy violations they're willing to take.
#GM, #Nostr.
Hey thanks for reaching out, there's install instructions here:
https://simplifiedprivacy.com/vpn-install/easy-one-command.html
The same info is on docs.simplifiedprivacy.com in a more "formal" format
Thanks. Do you have plans to also make a windows version?
With GrapheneOS? (the icons up top look familiar). Were you able to get rid of the AI they try to push on all new phones now?
I think so! I'm testing the zaps now an it seems to work now that I've changed it. I just wish there were an error message or something to tell you what's wrong. But if it times out, I guess the error can't be too detailed. Glad i figured it out tho.
No my site will create the nostr notes. I host my own rmtp server and my site converts any stream to it into an old stream so I can record live and broadcast the hls stream myself which is what the nostr live event points to when you're streaming. Zap stream lets you use their server and they make the events for you and you sign. With this I just hit start streaming on obs and boom my site goes live with metadata that I can change on the flu. Next up, I just have to throw making the nostr events in the same flow. nostr:nprofile1qqsxua0hju3e0j3jjhs0fjs0h3htnnreh6zm4lw4d0fhsgsv4rhwwnspzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxmhwden5te0wfjkccte9ehx7um5wfcxcetzwvhxxmmd9uggh9ef
It also archives the streams on the site so I'll make a component for those too.
SWEET!
Public service announement: If your zaps look like they don't complete in Amethyst but on Coinos sometimes they do sometimes they don't: Re-create the connection and increase the max-routing fee. #fix #workaround #zap #Amethyst #coinos #bug
Going to make this auto stream to nostr next
https://happytavern.co/live/view
All self hosted and open source
Are you going to use zap.stream or stream it a different way?
Ok, now it worked. I just re-did the connection but I increased the max routing fee. I wonder maybe that was the issue? Originally it was the default 1%, so maybe it took it a long time to "find the route" and sometimes it failed? (Idk how lightning works at all, I just now some of my transferers from wallet to wallet faiiled because of too low routing fee.
Well, idk. I tried to zap you, it didn't show up on my transactions. AFTER that, I zapped two people, the Amethyst progress circle looked the same (as if the zap didn't finish or work), but those two transactions did make it into coinos.
Myth: Browsers can Fool AI by “Spoofing”
Reality: Spoofing is just lying with your words.
Even back in 2016, Google could detect spoofing:
Google gives your client a challenge to draw. This image is from their (now ancient tech) 2016 whitepaper: [12]
Then these drawings are analyzed at the pixel level,
And compared to what that browser, OS, and hardware can normally produce,
This is why the Chameleon Browser Extension whitelists Google and Cloudflare [14]
Because their app, and those like it, just LIE with “user-agents” (their words)
You can’t hide the fundamental nature of browsers,
For example, when someone asked if they should block the specific type of JavaScript (that hides your screen size), the GrapheneOS dev said: [10]
In other words, they fingerprint you based on what you choose to block,
And if you turn off JavaScript,
Enjoy the rest of the fun meme slideshow or get sources:
https://simplifiedprivacy.com/myths-of-privacy/fake-or-unrealistic-solutions-smashed.html
Want! Where can get, pls? (also Qubes is not that bad. I don't play 4k videos, tho. And the fact that you can't hook up a modern android to the USB is annoying af. But for day to day development, I don't find it slow at all. All other USB tasks seem to work ok)
Is it 381? If so yes. I'll try to send it back. Let me know if/when it gets there.
Nah. I never placed a corporate microphone in my house to begin with.
I tried the connection several times. Idk whats going on. Just tried to zap someone. Amethyst is acting the same but I don't see the charges appear on the coin os side (yet?)
See if creating a new one and pasting into amethyst solves it. Don't forget to hit SAVE on Amethyst.
Mine expired, I created several new ones and it still looks like it's not working. No error meesage. Zaps look like they dont complete, even though the money is subtracted fom my coinos wallet. Confused me big time yesterday.
I use ChatGPT as a thinking partner—not to write code, but to shape ideas, explore options, and stay productive in the margins of a busy life.
It’s not magic. Just useful—when you stay in control.
My pragmatic take: https://sleepingpotato.com/a-pragmatic-developers-take-on-chatgpt/
#ai #chatgpt #development #buildinpublic
It's also good as a second pair of eyes when there's a bug but you're overlooking the obvious cause (like forgetting a dependency in a useEffect or useCallback).
