Snort.social requires header HTTP access to CORS Access-Control-Allow-Origin for Lightning tips / zaps. On NGINX add to `/etc/nginx/sites-available/yourdomain` `add_header 'Access-Control-Allow-Origin' '*';` See below:
```
server {
location /.well-known/lnurlp {
rewrite ^/.well-known/lnurlp/
add_header 'Access-Control-Allow-Origin' '*';
}
}
```
> Test nginx for errors with command (might need sudo): nginx -t
> Reload nginx (might need sudo): systemctl reload nginx
In Apache2 you need to enable mod_header on server side (a2enmod headers) and then add to .htaccess or apache config file appropriately:
In .htaccess:
```
Header set Access-Control-Allow-Origin "*"
```
> Test Apache for errors with command (might need sudo): apachectl -t
> Reload Apache (might need sudo): apachectl -k graceful
To test if CORS Access-Control-Allow-Origin * is added, you can use curl command in console.
> curl -I https://yourdomain.tld/.well-known/lnurlp/yourname
or you can use https://test-cors.org/, input the full URL as above and do a 'HEAD' HTTP response test. You should get 200 OK.
Snort.social requires header HTTP access to CORS Access-Control-Allow-Origin for Lightning tips / zaps. On NGINX add to `/etc/nginx/sites-available/yourdomain` `add_header 'Access-Control-Allow-Origin' '*';` See below:
```
server {
location /.well-known/lnurlp {
rewrite ^/.well-known/lnurlp/
add_header 'Access-Control-Allow-Origin' '*';
}
}
```
> Test nginx for errors with command (might need sudo): nginx -t
> Reload nginx (might need sudo): systemctl reload nginx
In Apache2 you need to enable mod_header on server side (a2enmod headers) and then add to .htaccess or apache config file appropriately:
In .htaccess:
```
Header set Access-Control-Allow-Origin "*"
```
> Test Apache for errors with command (might need sudo): apachectl -t
> Reload Apache (might need sudo): apachectl -k graceful
Glad you found it helpful 🤙🤙⚡️😄
I think I figured out the CORS issue on snort.social with LNURL/LNAddress tips with nginx. Looking into Apache now to help you out.
Here's what I did for nginx in the /etc/nginx/sites-available/mydomain.com file I edited it to add this `add_header 'Access-Control-Allow-Origin' '*'` within the location block in the server block:
```
server {
location /.well-known/lnurlp {
rewrite ^/.well-known/lnurlp/ezofox$ https://walletofsatoshi.com/.well-known/lnurlp/
add_header 'Access-Control-Allow-Origin' '*';
}
}
```
After that the CORS errors in the console went away and I was able to invoke it to pay the LN invocie.
If you're viewing this in astra.ninja ignore the , it's just parsing my paste wrong for the tab spaces.
I think I figured out the CORS issue on snort.social with LNURL/LNAddress tips with nginx. Looking into Apache now to help you out.
Here's what I did for nginx in the /etc/nginx/sites-available/mydomain.com file I edited it to add this `add_header 'Access-Control-Allow-Origin' '*'` within the location block in the server block:
```
server {
location /.well-known/lnurlp {
rewrite ^/.well-known/lnurlp/ezofox$ https://walletofsatoshi.com/.well-known/lnurlp/
add_header 'Access-Control-Allow-Origin' '*';
}
}
```
After that the CORS errors in the console went away and I was able to invoke it to pay the LN invocie.
Thank you! 😄🤙 Happy to help plebs with the information I know.
Thank you for the update and your work! 🤙🤙 Will test once 0.3.5 is out.
Same steps for nos2x https://github.com/fiatjaf/nos2x, download the extension folder from GitHub, and do same steps as above to install.
Also I recommend that you read this https://ungoogled-software.github.io/ungoogled-chromium-wiki/faq#:~:text=Open%20chrome%3A%2F%2Fextensions%20.,drop%20the%20file%20to%20install
Yes, go [github](https://github.com/getAlby/lightning-browser-extension/releases/tag/v1.24.0), download .zip file for alby-chrome, extract contents to a folder, open ungoogled-chromium, go to extensions, enable developer mode, load unpacked and select your Alby folder. It’ll install the extension.
Same steps for nos2x https://github.com/fiatjaf/nos2x, download the extension folder from GitHub, and do same steps as above to install.
Yes, go [github](https://github.com/getAlby/lightning-browser-extension/releases/tag/v1.24.0), download .zip file for alby-chrome, extract contents to a folder, open ungoogled-chromium, go to extensions, enable developer mode, load unpacked and select your Alby folder. It’ll install the extension.
To the following:
Good night Nostriches! 🌃😴
You’re welcome! 🤙
I guess most features like bookmarks, trending hashtags and lists will eventually be available even on Nostr social clients. It’s sad to see Twitter API having issues with clients.
You could go to about:config in Firefox, create a new profile and click launch profile in new browser. That Firefox instance will load a completely different Firefox profile with no extensions and is isolated from your primary profile and processes. You can then install those open source extensions on the new profile Firefox instance.
If you’re even more paranoid about that approach, just install another Firefox substitute like Librewolf or ungoogled-chromium and install one of those open source extensions.
Screenshot examples in Firefox and chrome to help you get it:
Hi! 👋 welcome! I assume you are already logged in to hamstr. They don’t currently have the feature in UI to copy your private key. To do so, Open your browser console (ctrl+shift+i).
On Firefox click ‘storage’ tab > local storage > you’ll see settings key and value > in the value you will find the private key > copy and keep it safe.
In Chrome click ‘application’ > local storage and do same as above.
warning: keep your private key safe and don’t enter it directly in web clients. Use nos2x/nos2x-fox or Alby extension to login to web clients.
Hey! 👋
So far, no clients I am aware of has that feature.