# 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 57
# self = https://watcher.sour.is/conv/bjjgk4a
@prologic I start my yarnd through command line, is there a way to enable the activitypub that way? or do I need to do it some other way? (I compiled the latest source)
@stigatle You'll need to enable both webfinger and activitypub
@stigatle You'll need to enable both webfinger and activitypub
@stigatle You'll need to enable both webfinger and activitypub
@stigatle You'll need to enable both webfinger and activitypub
@prologic Ah, thank you! I will test this after work today. Thank you!
@stigatle No problems! I'm still working on the feature so I'll keep updating y'all as I make further improvements and complete more of the work 👌
@stigatle No problems! I'm still working on the feature so I'll keep updating y'all as I make further improvements and complete more of the work 👌
@stigatle No problems! I'm still working on the feature so I'll keep updating y'all as I make further improvements and complete more of the work 👌
@stigatle No problems! I'm still working on the feature so I'll keep updating y'all as I make further improvements and complete more of the work 👌
@prologic Thank you for doing this! I'm really excited about this feature!
@stigatle No worries 👌 Gonna try and get the other side going tonight if I can 😱
@stigatle No worries 👌 Gonna try and get the other side going tonight if I can 😱
@stigatle No worries 👌 Gonna try and get the other side going tonight if I can 😱
@stigatle No worries 👌 Gonna try and get the other side going tonight if I can 😱
@prologic - when I start it I get this error:
ERRO[0000] error setting up ap error="error getting support feed: error: feed not found"
FATA[0000] error creating server error="error getting support feed: error: feed not found"
@stigatle Hmmm what da hell?! 😱 How does your pod not have the built in support feed? Hmmm 🤔
@stigatle Hmmm what da hell?! 😱 How does your pod not have the built in support feed? Hmmm 🤔
@stigatle Hmmm what da hell?! 😱 How does your pod not have the built in support feed? Hmmm 🤔
@stigatle Hmmm what da hell?! 😱 How does your pod not have the built in support feed? Hmmm 🤔
What's the admin user on your pod? You? 🤔
What's the admin user on your pod? You? 🤔
What's the admin user on your pod? You? 🤔
What's the admin user on your pod? You? 🤔
@prologic I do not think I have set up the admin user correctly.
I need to check that. But yes - I should be the admin either way.
The error I mentioned was on my development machine - not my VPS that I currently post from.
@prologic got the admin stuff sorted on both now.
@stigatle Interesting... I'll see what I can do about this...
@stigatle Interesting... I'll see what I can do about this...
@stigatle Interesting... I'll see what I can do about this...
@stigatle Interesting... I'll see what I can do about this...
@prologic Thank you.
What I did was to just pull the latest, build deps and the server, then enable the features as you mention through command line, as soon as I add activitypub it fails with that error when it starts up.
@stigatle Yup, because the activitypub features wants to build a default pod actor using the builtiin support feed, which doesn't seem to exist on your dev pod 🤣
@stigatle Yup, because the activitypub features wants to build a default pod actor using the builtiin support feed, which doesn't seem to exist on your dev pod 🤣
@stigatle Yup, because the activitypub features wants to build a default pod actor using the builtiin support feed, which doesn't seem to exist on your dev pod 🤣
@stigatle Yup, because the activitypub features wants to build a default pod actor using the builtiin support feed, which doesn't seem to exist on your dev pod 🤣
Bingo! There we go 🤦♂️ 
Bingo! There we go 🤦♂️
Bingo! There we go 🤦♂️
Bingo! There we go 🤦♂️
FWIW the feature will _probably_ work fine on your production pod. That's why its' feature flagged 😅 Just enable it through the UI and restart 👌
FWIW the feature will _probably_ work fine on your production pod. That's why its' feature flagged 😅 Just enable it through the UI and restart 👌
FWIW the feature will _probably_ work fine on your production pod. That's why its' feature flagged 😅 Just enable it through the UI and restart 👌
FWIW the feature will _probably_ work fine on your production pod. That's why its' feature flagged 😅 Just enable it through the UI and restart 👌
@prologic Running out of time for tonight, but I will test it tomorrow! :) I'll let you know how it goes tomorrow night.
@stigatle Meanwhile I'll fix the bug of course... But FWIW you cannot run activitypub or webfinger on a dev instance per se, mostly because it needs full DNS lookups, TLS, etc, for things to work properly.
@stigatle Meanwhile I'll fix the bug of course... But FWIW you cannot run activitypub or webfinger on a dev instance per se, mostly because it needs full DNS lookups, TLS, etc, for things to work properly.
@stigatle Meanwhile I'll fix the bug of course... But FWIW you cannot run activitypub or webfinger on a dev instance per se, mostly because it needs full DNS lookups, TLS, etc, for things to work properly.
@stigatle Meanwhile I'll fix the bug of course... But FWIW you cannot run activitypub or webfinger on a dev instance per se, mostly because it needs full DNS lookups, TLS, etc, for things to work properly.
@prologic aha, I see. no problem. Ill get it set up on my prod server tomorrow then 😀