Avatar
Kirpy
ff2bfabafea9d5c3b00fe6a285139239012680f3cbf43ac5532a8736a95f8070
Open source freedom tech is the way to true sustainable liberty. Love sailing, camping and music festivals.

Would be nice to have a toggle to turn on notifications for when a follow starts streaming too :)

I see Yakihonne requested notification permission when I installed it but I haven't gotten any.

Wow, all posts today look like this. my WOT is set to 1. Tis a dark day.

I was interested in the Fedi but then instances started banning each other. I fear those doing this attack may want us to go the the fediverse. There you're either in a echo-chamber of deep-state propaganda or your instance is blocked by many.

Not that I think all the instances are paid off, but they happen to be what elites want. To be block happy and divided. I want to see both sides.

On top of choosing my relays, which should stop spam, something I can configure like wot is great. Unfortunately I see much spam coming from filter.nostr.wine which was paid and doing good until today. :(

I think the concept of WOT is great but can't just stop at follows. One should be able to choose the WOT points that users must have, but also choose how many layers (follows of follows of follows) aggregate that score. WOT isn't the one solution but it's needed. and needs to be more configurable.

I like for something like this to be configurable. Like with wot I could mark it to 0 so if anyone with Relationship Status with me blocks the user, I don't see them. Or maybe I set to -1/3 to see more when I feel like it.

These bot attacks seem to be ever changing and many attacks aren't perminent. Right now I'd probably set it to 1 but maybe when it calms down i'd set it to -1.

I'd probably have had better luck if I did that! I just remember a couple years ago I couldn't get nginx to work for Nextcloud and I found Caddy which has been my buddy since. It's automated https by default.

Course I've had to do nginx for work more recently but systems gave me the trusted cert lol

Long as you complete step 6 it should. It reboots after leaving the chrooted environment.

I love the idea of nostr:npub126ntw5mnermmj0znhjhgdk8lh2af72sm8qfzq48umdlnhaj9kuns3le9ll, however thought of it as "mostly" useless to average individuals who aren't looking to tor everything.

While the new version is in developement to enable https external access to services using your domain, I found out a hack on how to do this in the meantime

Credit to remcoros on the nostr:npub126ntw5mnermmj0znhjhgdk8lh2af72sm8qfzq48umdlnhaj9kuns3le9ll for the original guide. Hopefully I made it a little more understandable to dumbos like me πŸ˜‰

As a prerequisite, you'll need to know Caddy reverse proxy (or use another, but Caddy simplifies cert stuff for me), and you'll need to know basic CLI, like how to navigate the filesystem, and create/save a text file.

This example uses the FreeGPT service but I've tested with nostr:npub1wyuh3scfgzqmxn709a2fzuemps389rxnk7nfgege6s847zze3tuqfl87ez, and nostr-rs-relay.

## Enable external access+HTTPS

1. pick a port and subdomain. add the entry to Caddy for automatic certificate/ssl reverse proxy:

```

https://subdomain.domain.com:443 {

header Strict-Transport-Security max-age=31536000;

reverse_proxy 192.168.1.111:50002

}

```

2. Install the service from start9 marketplace or sideload.

3. Go to the services management page and go to the Wrapper Repository URL listed there.

4. Arriving in Github, look for the file `scripts/procedures/healthChecks.ts`

1. possibly line 4? You should see a line: `"web-ui": healthUtil.checkWebUrl("http://free-gpt.embassy:8080")`, the part you need is `free-gpt.embassy:8080` which is the service and port it's listening on.

5. Now SSH into the Start9 server and switch to the root user with `sudo -i`.

6. Switch to the "chrooted" environment with `/usr/lib/startos/scripts/chroot-and-upgrade`. You should see a bit of syncing.

7. Create and open your service file `vim /lib/systemd/system/socat.freegpt.service` and give it a sensible name.

8. Paste the below text and:

1. Modify the description

2. Modify the port number after "tcp-l" to match the port you chose in your CaddyFile.

3. Modify the text "free-gpt.embassy:8080" to match the text for your service found from Github.

```

bash

[Unit]

Description=socat electrs forward

Wants=podman.service

After=podman.service

[Service]

Type=simple

Restart=always

RestartSec=3

ExecStartPre=/bin/bash -c "/bin/systemctl set-environment IP=$(ip route | grep default | awk '{print $9}')"

ExecStart=/usr/bin/socat tcp-l:50002,fork,reuseaddr,su=nobody,bind=${IP} tcp:free-gpt.embassy:8080

[Install]

WantedBy=multi-user.target

```

9. Save and quit.

10. Start your service with `systemctl enable socat.freegpt` or whichever service name you chose. That's the file name you created earlier.

11. exit the "chrooted" environment with `exit`.

12. That's it! if all's well you may reach your site on the clear-net with your domain.

The list of restaurants I go to have been decreasing steadily over the last few years. Fast food especially though. I don't know how people live on it. I can't stand the feeling when my foods wrong for the 3rd restaurant visit in a row.

I think they are telling people though. Their telling them they're open with the sign on the door.

In Amethyst I saw a dvm that popped up a charge for 10 sats to load. Seemed very smart contracty to me! For cool useful things like filtering all follows temporarily I'll fork it up.

Verifiable computations sounds cool but one good baby step would be for them to add more than 3-4 words describing what they do in the description. They're a mystery now.

Another spin. You posted the warning sign in agreement to the op as the content of their post was a warning (as some do on Facebook) and the clients posting as hearts used an icon that represents all reactions to be more friendly with users coming from Twitter.

Another thought maybe was there a simple like nip before the react nip? Maybe clients wanted to easily combine both nips together in the way Amethyst combines reports/reacts.

Replying to Avatar hodlbod

I have a question for #amethyst users. I'm not asking this to dish on nostr:nprofile1qyghwumn8ghj7mn0wd68ytnhd9hx2tcppemhxue69uhkummn9ekx7mp0qythwumn8ghj7anfw3hhytnwdaehgu339e3k7mf0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpqgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqss2dqr , but only because his users are my users, and I care about my users' (for lack of a better word) "safety" on nostr.

Currently, when you report something, Amethyst does two things:

- Publishes a kind 1984 report event

- Reacts on your behalf with a ⚠️ kind 7 reaction

TLDR; do you find the emoji reaction to be a problem? Full background below.

I've always been skeptical of public reports, because regardless of intent, they publicly and permanently associate your public key with objectionable content. This may be as harmless as reporting spam, which is fine to do publicly, or as sensitive as reporting directed abuse (sharing additional information about your associations), or reporting CSAM (which is a legal gray area in some jurisdictions, since it may constitute "advertising" the content).

I personally use nostr:nprofile1qyfhwumn8ghj7ur4wfcxcetsv9njuetn9uqsuamnwvaz7tmwdaejumr0dshsz8nhwden5te0dak8jmtsd93hxv3sxg6zumn0wvh8xmmrd9skctcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9nhwden5te0v4jx2m3wdehhxarj9ekxzmny9uqzqrezcph2cyqzdp80e35026z5p6p595tqn4gghn2rztqr3esef79kpu7u7y 's nostr:nprofile1qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshszymhwden5te0wp6hyurvv4cxzeewv4ej7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uq3qamnwvaz7tm99ehx7uewd3hkctcpzamhxue69uhhyetvv9ujumn0wvh8xmmrd9skctcqyptdfv7kxy86mdeffdlsgx4tg6w9llyfjxcmrve3nqdedgjx76hx2a33ch8 to anonymously and privately process reports in Coracle, because I want to protect my users as much as possible. But I'll admit that use of kind 1984 is nuanced and open to debate.

Much worse than using kind 1984 though, which semantically fits the concept of "reporting", is using reactions to signal reports. First of all, this doesn't really add any new information that kind 1984 doesn't already contain. It also has the effect of generating content on behalf of a user that they may not know they're consenting to.

In many clients (formerly including Coracle), "likes" are not filtered down by emoji, and so these kind 7 "reports" end up showing up as "likes". Completely fixing this problem is impossible, because it requires mapping a high-fidelity subjective medium (emojis) to a low-fidelity objective medium (up/down vote) in order to show likes. This can only be done with a reasonable degree of reliability for a very few emojis. This creates a problem for like-based clients in that lots of reactions can't be included in like tallies, resulting in lower social signal.

At any rate, I implemented the partial fix of whitelisting "obviously positive" emojis when calculating "likes" a long time ago, because reactions can be negative. I however didn't apply this to the "likes" tab on user profile pages, which was brought to my attention earlier this year when an Amethyst user asked me why a bunch of CSAM was showing up under his "likes". He wasn't aware that "reporting" in Amethyst created a public record of his consumption (unintentional or otherwise) of illegal porn.

This problem has since been fixed in Coracle, but likely still occurs in other clients that haven't yet addressed this problem, "trending" algorithms, and coracle custom feeds based on retrieving kind 7 (since kind 7 sentiment can't be filtered against on the relay side).

This is a Really Bad Thing, because it results clients advertising content as connected with the person who had intended to dissociate themselves with it. While clients processing reactions can mitigate this, the root issue is that a field for user-generated content is being overloaded for use in an application-specific context.

So, that's my opinion. What do you think? Do you find it surprising that reports in Amethyst may be treated as "likes" in other clients? Is it Amethyst's fault for creating the reactions, or other clients' fault for not filtering them out?

For more discussion, see the thread on github: https://github.com/nostrability/nostrability/issues/88

Recently started using Coracle and it's my fav for web. I prefer android though and Amethyst is my fav there. Yall are great thank you both for your work!

I'm by no means a pro but think if there's now a future universal reports kind we should move to it. A toggle in settings is always an option when there's differing opinions along with a warning on first use of the report function "heads up some clients will see this report as a reaction unless you disable in settings!"

On another silly note this reminds me of the debate between laptops having usb-a vs usb-c. Some are mad at laptop designers for not including the old a type. I'm mad at device creators for continuing to sell it. Quicker it stops being sold the quicker people won't need dongles!