# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 23
# self = https://watcher.sour.is/conv/npmef2a
Good News πŸ₯³
Good News πŸ₯³
To all existing Poderators around the globe, I would love your help in testing our the App please πŸ™ cc @mutefall @ullarah @darch @eldersnake
To all existing Poderators around the globe, I would love your help in testing our the App please πŸ™ cc @mutefall @ullarah @darch @eldersnake
@prologic that is so fucking cool! Congratulations!

So how would I go about testing it? πŸ˜…
@prologic @ullarah launch a vultr machine from the marketplace :-)
@prologic Congratulations!
@mckinley Thank you! πŸ™
@mckinley Thank you! πŸ™
@prologic with the vultr yarn app, do I still need a reverse proxy like Træfik?
@darch No, the idea of the "App" in the Vultr Marketplace is:

1. You deploy the app.
2. You point your domain at it.
3. Done.

When you go to deploy it, it will ask you for the Base URL of your Pod that you expect to run on. This is the only required mandatory input you must supply ahead of time. Then you point that domain/subdomain at the Vultr VM's IP.

There is no Reverse Proxying required because the yarnd instance itself runs directly on the system and listens on port :443. It also automatically acquires TLS certificates from Let's Encrypt automatically.
@darch No, the idea of the "App" in the Vultr Marketplace is:

1. You deploy the app.
2. You point your domain at it.
3. Done.

When you go to deploy it, it will ask you for the Base URL of your Pod that you expect to run on. This is the only required mandatory input you must supply ahead of time. Then you point that domain/subdomain at the Vultr VM's IP.

There is no Reverse Proxying required because the yarnd instance itself runs directly on the system and listens on port :443. It also automatically acquires TLS certificates from Let's Encrypt automatically.
@prologic ah so I guess I missed the :443 port thingπŸ€” I need to add the port number to the IP in my DNS (i.e. cloudflaire), right?
@darch Umm no, if you were trying out the new Yarn app in Vultr, you just create a record in Cloudflare and point it at the Vultr VM's IP. That's all.
@darch Umm no, if you were trying out the new Yarn app in Vultr, you just create a record in Cloudflare and point it at the Vultr VM's IP. That's all.
@prologic hmm that's exactly what I tied but it didn't work... That is the IP without the port number πŸ€”
@darch Example:

- https://demo.yarn.social
- It's Vultr IP is: 104.207.128.236
- When I created the instance I set it's Base URL: to https://demo.yarn.social
- I created an A record in Cloudflare (Orange cloud) th point to 104.207.128.236

That's it.
@darch Example:

- https://demo.yarn.social
- It's Vultr IP is: 104.207.128.236
- When I created the instance I set it's Base URL: to https://demo.yarn.social
- I created an A record in Cloudflare (Orange cloud) th point to 104.207.128.236

That's it.
@prologic so it shoud be set to "Proxied" and not "DNS only" in cloudflare?!
@darch Try setting SSL in Cloudflare to "Flexible".
@darch Try setting SSL in Cloudflare to "Flexible".
Actually turn off "Orage cloud" on that A record.

Example:
Actually turn off "Orage cloud" on that A record.

Example: