Login to the OpenAI playground and none of those restrictions apply. Just for the public Chat.
It does.
NOSTRGRAM UPDATE - CUSTOM ZAP AMOUNTS
You can now set the default amounts of the Zaps in the ⚡ pop-up box. Watch this quick video to see how it works. Refresh the page for the update.
s/o #[0] for the suggestion
s/o #[1] for reminding me so I actually did it
I'm told it does. I've been using Kiwi but I've seen others say they use Brave + Alby.
You can use the Alby or Nos2x extension with either the Brave or Kiwi browsers on mobile (Android anyway).
Yes you can use an extension with both Brave and Kiwi on mobile. I use Kiwi + Alby (on Android) and it works great.
So in response to a reply by #[0] I added code into NostrGram to intercept a longpress on mobile, but I'm not sure what to use it on lol. His idea was to have a quick press of the ⚡ send a fixed amount of sats and the longpress bring up the pop-up for sending different amounts. Thoughts?
What do you think of an option in NostrGram to send a Zap of a fixed amount that you determine every time you Like a note? Alby lets you set a budget so if you have Alby you wouldn't have to keep approving each ⚡. Just thinking out loud.
You can see your zaps (if they were a true ⚡ of Kind 9735 and not just a Lightning payment) in the NostrGram filters. It at the bottom ("Zappers").
Nostr ⚡ Stats
109,541 ⚡ totaling 290,602,896 sats
Ok cool. Because the web socket server runs on a non-standard port (for now) every now and again a mobile connection won't like it. Refreshing the page should fix that.
Ok great. Thanks for giving feedback. It really helps.
Were you on your mobile connection or on wifi? I'm just trying to pinpoint if there was an issue on this side or if it was a mobile hiccup.
It hit me right after that last update that pinned notes should persist across refreshes (we're building here, after all), so now they do. You'll need to refresh the page to get the update, but now your pinned note in NostrGram will remain even if you refresh the page. That way you don't have to go hunting for the note again. It won't restore the video/audio to its previous location, but at least you won't have to search for the note! Very useful for rejoining Nests also.
Yes the sats figure is aggregated on the server side the moment the zap hits, which is how it knows the value sent to any given note. I need to add an additional indexed field for who sent the zap as well. Just haven't done it yet (it's a big change on a database of 20 million notes!)
🙏 for the ⚡ folks. They really matter when putting this much time into NostrGram. 💜
NOSTRGRAM UPDATE: Fix For Those Who Couldn't Connect (blank screen)
If you haven't been able to use NostrGram since I switched it to using a web socket server (if you were getting a blank screen with just a few icons on it), you should now be able to connect again.
NostrGram now automatically switches to the previous connection method (REST) if the web socket server is unavailable for any reason. It does this seamlessly, so if you're on mobile and end up on a network that won't connect to the socket server, it falls back to REST without you having to do anything.
This should greatly improve the connectivity experience with NostrGram while still maintaining better performance generally since most people, most of the time have no issues connecting to the socket server.
I also added a ⚡ notification on desktop that appears in the upper-right corner for about 10 seconds when you get a ⚡. Click on the icon to go to the note the ⚡ originated from.
As always, I appreciate your support via ⚡. It makes my work with NostrGram possible. Thank you for using NostrGram!
Hi, i made an unofficial Nostrgram android app with physical button (slide menu) .
It also comes with access to getalby wallet & nostrnests for a unified experience
Feel free to review it #[0]
https://drive.google.com/file/d/1KkzyaesHgwjUOIhQigb6qpQ2d8x79aeg/view?usp=drivesdk
Cool. Nice that it supports Alby!
😆 I can relate.
Ok, that means there's an issue with the extension injecting the code into the page. If you haven't tried it already, close the browser and re-open it. Then see if you can use the Extension button.
It always astounds me how huge the mov files Final Cut Pro (Mac) produce are. Handbrake takes them down to a fraction of the size.
Ok that's odd. The xlmhttp error is also Nip05 related and isn't a NostrGram error. In the console, at the prompt, type this and press enter:
window.nostr
If the extension injected the Nostr code into the page you'll see something like this image shows. If it didn't, you'll see "undefined".
Which one did you install?
If you wouldn't mind following these instructions it would help me figure out what's wrong: #[2]
Ok, if you could do this in Chrome it would help me:
1. Reload the page
2. Open the Developer Tools (see image below)
3. Click the "Console" tab (if it doesn't open in that tab already)
4. Click the icon to login
5. Click the extension button
6. Take a screenshot (or copy any red text) that appears in the Console. Red text means an error. Ignore the "GET" errors (those are related to people's Nip05 verifications and aren't NostrGram errors).
If you wouldn't mind doing that it would help me figure out what's wrong. If you're having the issue, some others are bound to also.
