Thread

Sharing this directly on Nostr. Let's hope it works this time. This essay builds on the last one I wrote (As Nostr as Possible), but focuses specifically on some ‘sacred cows’ in the space whose time for slaying may have arrived. It's not shitting on Nostr (far from it). It's about a different perspective and relationship to the protocol. I hope this kicks off a few discussions. image https://highlighter.com/a/naddr1qvzqqqr4gupzq6ksswfdrw4r7mlh49qfu2k9u4zrtpextk955kquvpna3r4rq9vyqy88wumn8ghj7mn0wvhxcmmv9uqp7nn0wd68yt24decx7ur4d3shyt20wp5ku6t0deej6up4xd6xxwgmazesl
View quoted note →

Replies (21)

I think satlantis has a really good potential and on the right track with nostr. So I will share just a feedback of what I want it to be able to get done and usable as satlantis itself will promote nostr and will do it great, the nostr apps will be what promotes the protocol. 1. Login with nostr is great, login with just nsec could benefit with other nostr login options. 2. I find it much more appealing and easy to navigate and find merchants on it per place than btc map which is great. That said it needs more coverage. 3. The comment section display needs some Wot as the bots spill a lot of nonsense per hashtag so a new nostr user just visiting there will be wtf (see Dubai for example, world news are for elsewhere). 4. When I first checked satlantis sometime ago I actually thought that it could be some sort of combination with nostr airbnb. It is a huge deal to run but users may be more interested in organising events with accommodation (lets all of us go to @fiatjaf 's hostel shed first 🤣). There is a huge difference in bitcoin adoption for these few years so a lot of places will have more to offer. On a practical note what I want to see is place tab with wot feed > scores (possibly including rates from your nostr wot)> Accommodations with btc (same full info) maybe developed in a booking through nostr system > Merchants (that tab is great) > Events (dont worry about that one, when people start to book and organise, they would want to share that travel and clients will be obliged to implement in a compatible way unless there js a radical nip change or something). Btw apart from Nostur thats the first other usable nostr app that shows who followed you as notification 🔥 In short satlantis is not lacking on nostr, nostr is not lacking on satlantis, both need more practicallity. Just only in recent months I see more focused specific app development that concentrates on a specific target market and aims to do it well. That is a nostr business model and leverages above the tool label.
↩ replying to Cocktus 🌵
Thankyou for all the feedback. We have a BUNCH in the works, including a few of the things you highlighted there. As of April, we’ll roll out a new version with some of those improvements. June is the “official launch” and by then, you’ll see what we have in store for the “base product” with the “base functionality”. One question I do have for you.. How would you like to learn about product updates? Essays by me? Posts on Nostr by me? Posts from the Satlantis account? Each have their pros and cons Curious to hear from you on this
↩ replying to Svetski
The three of the above as you have a circle that follows you already, use all of your marketing skills, plus maybe do a bit of zapvertasing through wot as well to avoid every bot out there and hit real nostr users. Also when you put out the message, zap for reposts of the long and short forms as well, I have noticed that for better or worse that spreads like fire 🤣🤙These are at least the methods that I have seen working so far.
↩ replying to Svetski
Also a similar bot that runs on the Satlantis npub and explains things to userd may kick things off. Updates or whatever you want to be known similar to the Ditto one but for Satlantis and business. Ai could or not be an overkill for that depending what you want to do.
Dittobot's avatar Dittobot
Absolutely, I can help guide you through the installation of Ditto. Here's a summary of the steps you'll need to follow: 1. **System setup**: First, ensure your server is updated and install necessary dependencies. You can do this by running the following commands, depending on your Linux distribution: - For Ubuntu: ``` sudo apt update sudo apt upgrade sudo apt install git curl unzip nginx postgresql-contrib certbot python3-certbot-nginx ``` - For Fedora: ``` sudo dnf check-update sudo dnf update sudo dnf install git curl unzip nginx postgresql-contrib certbot python3-certbot-nginx ``` - For Arch: ``` sudo pacman -Syu sudo pacman -S git curl unzip nginx postgresql-contrib certbot certbot-nginx ``` 2. **Install Deno**: This is crucial as Ditto runs on Deno. Install it with: ``` curl -fsSL https://deno.land/x/install/install.sh | sudo DENO_INSTALL=/usr/local sh ``` 3. **Create Ditto user**: For security, create a separate user for running Ditto: ``` sudo adduser ditto ``` 4. **Download and configure Ditto**: - Clone the Ditto repository: ``` git clone https://gitlab.com/soapbox-pub/ditto /opt/ditto chown -R ditto:ditto /opt/ditto ``` - Switch to the Ditto directory and user: ``` cd /opt/ditto sudo su ditto ``` - Run the setup task to create a `.env` file and follow the prompts: ``` deno task setup ``` 5. **Install Soapbox (optional)** if you want to use it with Ditto: ``` deno task soapbox ``` 6. **Database setup**: Exit the `ditto` user shell and create a Postgres user and database: ``` exit sudo -u postgres createuser -P ditto sudo -u postgres createdb ditto -O ditto ``` 7. **Start Ditto**: - Copy the systemd service file and start Ditto: ``` sudo cp /opt/ditto/installation/ditto.service /etc/systemd/system/ditto.service sudo systemctl daemon-reload sudo systemctl enable --now ditto ``` 8. **Configure Nginx and SSL**: - Edit the Nginx configuration to reflect your domain: ``` sudo cp /opt/ditto/installation/ditto.conf /etc/nginx/sites-enabled/ditto.conf sudo nano /etc/nginx/sites-enabled/ditto.conf ``` Replace `example.com` with your domain. - Obtain an SSL certificate: ``` sudo certbot --nginx ``` - Restart Nginx: ``` sudo systemctl restart nginx ``` 9. **Additional configurations**: You might also want to promote a user to admin or add relays for data ingestion. You can find more details on these steps in the full installation guide. If you need any more details or encounter issues during installation, please let me know! You can also refer to the full guide here: https://docs.soapbox.pub/ditto/install
View quoted note →
One thing I’d take issue with is the BlueSky example. Users did not flock there because they were being censored on X and needed something permission-less; they flocked there because they had LOST the power to censor others on X and wanted it back for themselves. The promise they see in BlueSky is not greater freedom, but that their faction has enough concentration of power to limit the freedom of others. So there’s no mystery as to why they didn’t turn to this platform. It’s everything they didn’t want.
↩ replying to npub129tv...5ll6
That’s a very good point. And I agree with you in general. That being said… 1. It doesn’t really answer why (one of) the biggest increases in BlueSky user growth happened when X was banned in Brazil (not sure wtf explain that tbh 😂). 2. I still don’t think “censorship resistance” is an appealing enough narrative to create a meaningful enough network effect. That doesn’t mean censorship resistance shouldn’t be “baked into” Nostr as a standard (IMO that’s SUPER important), but I don’t think it’s going to appeal to a lot of people outside of whoever is mostly already here & gets it. I think we need to Trojan horse it into larger audiences via other means. Or who knows - maybe we shouldn’t even talk about it at all? I’m not sure what the exact solution is. Still experimenting
↩ replying to 🇵🇸 whoever loves Digit
ATProtocol does use keys, k256 key pairs by default. The PDS just puts a nanny password layer between the user and the keys, the same as the pseudo password thing that some Nostr clients once experimented with going back. ATProtocol you can start off self-hosted and have full control of your DID and your keys. Or you can start off with their hosting and later pull out your repo and your keys.
↩ replying to Garbage nsec
No I can't dipshit, they banned me before "opening up federation" And even if they've got my posts archived somewhere to let me have them back later, there is no longer any chance for me to keep up with the network's growth in maintenance of my mute lists and stuff. At protocol lost me by having me banned during that period of growth to stop me from keeping up on mute lists and stuff
Bumped onto this post and the 'as-nostr-as-possible' substack. Great reads! Please take my sats. From your blog post I am trying to solve the slowness + crawl ability with a server/client model. I've been told (by Nostr purists) that if the app is not using outbox/relay model/OSS it's not truely Nostr. So glad to read about the concept 'as nostr as possible' approach which is the model i've been applying prioritising user features/speed/UX over ideology. And while the eco-system gets better more parts of the app(s) can be ported to be pure Nostr.