Avatar
Rik šŸ”„ šŸ” šŸƒ 🌊
ca447ffbd98356176bf1a1612676dbf744c2335bb70c1bc9b68b122b20d6eac6
Empower others, kill my daemons and perform together. šŸš€

Going to Malaysia next summer with my family. What are must goto places to visit, #nostr?

I think thats because you filled wss:// in relay url, if so please try ws://127.0.0.1 first...relay url env is only used in the agent so it can find the relay

I just added a brief readme with an outline on how to get the docker container running. I run it through portainer and put a caddy reverse proxy in front of it to make it public

What I was thinking next was leveraging all these php shared hosting as nostr cdn using php. That language is still used on many hosting platforms and that way you could set up some kind of content delivery network using that

If everything works it sends you a message that it is availble. Very curious if you can get it up and running and the amount of effort it took (and other fewdback)

I have it running on wss://nostr.rikmeijer.nl, just spin up the docker (with the env vars in env.example)

Also a simple platform connecting my nostr identity throught #openid or #oauth (preferably wrapping around #nostr connect)!

To facilitate companies switching over to #nostr, ms365, nextcloud and google workplace can provide good inspiration. What tools do we need:

- compatibility with ms office. Long or short, people are used to this software. In the short run this is vital to support. Perhaps it is possible to design a Entera/AD/Exchange proxy built

- realtime collaboration, maybe proxy'ing openoffice through nostr. A relay can provide the compatibility layer for this

- imap/smtp connector/proxy

- secure, shared disks like onedrive, google drive or nextcloud

- video conferencing with internal and external parties

Maybe underbuilding/extending nextcloud with nostr operability?

#asknostr