I am wondering if there is some HDR content here that is not rendering correctly π€
Do you see the low quality when you zoom? Or just in the regular feed? I can check the algo, but it is essentially scaling down to the number of pixels in the screen of the feed. When users hit the save button, it re-downloads to get the full res.
The UI on Amethyst does this automatically so save people's disk space. When images are downloaded, it reduces the size the the amount of pixels in the screen of the viewer's phone.
Yeah, MuSig is a thing. But the post will come from a strange pubkey that is the sum of all pubkeys involved.
This was a pretty good discussion on all things nostr, including Gif buttons.
Made an epstein file viewer because the governments website sucks
hosted for free at: https://epstein-files-browser.vercel.app/
#news #breaking #epstein #gov #btc #sats
https://blossom.primal.net/d2a9d3bfa727dde743d60fc13010f8db852f066538b1a04655347fdcf07824c9.mp4
Is it a nostr client? π
On the client, you can only delete your own things for now. But on your inbox relay, you can do whatever you want. That's why it is so important to talk to them.
We will develop features to hide events from others but if they are not erased from the relay, over time they will just consume more and more data.
Weird. Are you using the default privacy option? The default sends your posts to your relays outside of Tor, but if you changed, it might be a Tor issue.
I am guessing nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszythwden5te0dehhxarj9emkjmn99uq35amnwvaz7tms09exzmtfvshxv6tpw34xze3wvdhk6tc4uevew, nostr:nprofile1qqs8eseg5zxak2hal8umuaa7laxgxjyll9uhyxp86c522shn9gj8crspz9mhxue69uhkummnw3ezuamfdejj7qgjwaehxw309ahx7um5wgerztnrdakj7qgkwaehxw309a3x2an09ehx7um5wgcjucm0d5hsvlnggv also has some knowledge in this. We need:
1. Good images for specific relays to deploy
2. Easy deployment solutions.
I think we have some lightning-enabled VPS server providers around, no? We could start with those. I am guessing it would be beneficial to them to have an easy interface to set their own services up.
That's weird. It's not a lot. When you rebroadcast and icons don't show up, can you go to your relay list, open your outbox relay and see if there is an error message down below?
Yep, my current issue is with DM relays that auth. If it is a personal DM relay that the user wants to filter who can send them DMs (only follows for instance), I think auth is cool. But if it is a public/common relay, then it's not cool.
I don't know exactly how to determine when to auth or not.
This is weird, how many relays is the app connecting to?
Blindly asking for forward secrecy is my hint that the person is not a cryptographer and is just regurgitating words from the privacy media.
Nah, it's probably too complicated for the AI to figure out. It was a good interface though
nostr:nprofile1qqs2352kp44xgl2sz6v3vujx7gmmxma3y0ufz68a5ywuws6n8lk85zqprdmhxue69uhkwmr9v9ek7mnpw3hhytnyv4mz7un9d3shjqg4waehxw309aex2mrp0yhxgctdw4eju6t09uq3vamnwvaz7tmjv4kxz7fwd4hhxarj9ec82c30tjj4ma did
Maybe Amethyst can do this. π€ Can any server people help me with the best way to setup a DM relay (anyone can post kind 1059s, only I can download) for one click deployment?
Amethyst will then have to upload that image to a provider and change the key to the current user.
Somebody should make a Nostr client to deploy and manage ready-made relays for us using as many cloud providers as possible.
I'd like to easily run 2 DM relays is separate cloud providers.
Sign in with your nsec, select which relay to ship, select provider, done.
The app should watch for software updates and notify us to update, which should just be a single button.
Yep. Marmot is its own protocol because it is so complex.
"Mostly"?
You want to know, but I don't want to tell you.
It works for OBS, but not zoom
Lol, that's the old nip04. You are seeing 4% of my DMs. Only to people that don't a have Amethyst.
Lol, that's the old nip04. You are seeing 4% of my DMs. Only to people that don't a have Amethyst.
Playstore language. Blocks are for you. Reports for everyone to see
Yep, we call mutes -> blocks.
Nah. Next version will help you manage private follows. Nobody will see who follows who.
I can make an annoying category for reports. Either way this is not changing.
Then just report them. Reports are public, mutes are private.
True. But none of us have any social skills. We just pretend for as long as we can. :)
it's fine for regular sized events, but it's going to take a big whack out of performance of the database finding small events when it has giant blobs randomly scattered through the kv log structures.
and it's trivial to add a blossom server to a relay, my relay already has one. in theory, supports all of the BUDs too. ah yes:
here's a reasonable starting point for implementing one in Go:
https://github.com/mleku/next.orly.dev/tree/main/pkg/blossom
Nostr already has a bunch of very large blobs. People need to stop using KV bullshit and start building real databases because it is only going to get worse from here. Events are starting to become massive with all the tags we are adding already.