# 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 38
# self = https://watcher.sour.is/conv/4a2eiea
regarding the spam, bots and spam accounts, that we seem to be attracting lately⦠What if we build a feature where instead of just completely open registrations, we change this to accept an email address that sends an email to the pod operator with a link to accept or reject the registration?
regarding the spam, bots and spam accounts, that we seem to be attracting lately⦠What if we build a feature where instead of just completely open registrations, we change this to accept an email address that sends an email to the pod operator with a link to accept or reject the registration?
regarding the spam, bots and spam accounts, that we seem to be attracting lately⦠What if we build a feature where instead of just completely open registrations, we change this to accept an email address that sends an email to the pod operator with a link to accept or reject the registration?
regarding the spam, bots and spam accounts, that we seem to be attracting lately⦠What if we build a feature where instead of just completely open registrations, we change this to accept an email address that sends an email to the pod operator with a link to accept or reject the registration?
@prologic for my pod it'd be simpler: don't allow anyone to register with a username that ends in -zit. Problem solved!
if 100 people register for a pod that's 100x work for the administrator compared to having each user pass a non-user-hostile captcha and verify their email address. I'd advocate for filtering on the user side and equipping admins to mass delete spam and inactive accounts.
@abucci I'd like the pod to automatically nuke inactive accounts/feeds. Are you open to that? I _think_ internally there is enough data to go on (whether the user updated their avatar, whether the user updated their description, whether the user actually posted anything at all, etc) if you've seen a "Candidates for deletion" email, those cores are based on nthis. Anything above a 2000 are "sfe to nuke" in my experience.
@abucci I'd like the pod to automatically nuke inactive accounts/feeds. Are you open to that? I _think_ internally there is enough data to go on (whether the user updated their avatar, whether the user updated their description, whether the user actually posted anything at all, etc) if you've seen a "Candidates for deletion" email, those cores are based on nthis. Anything above a 2000 are "sfe to nuke" in my experience.
@abucci I'd like the pod to automatically nuke inactive accounts/feeds. Are you open to that? I _think_ internally there is enough data to go on (whether the user updated their avatar, whether the user updated their description, whether the user actually posted anything at all, etc) if you've seen a "Candidates for deletion" email, those cores are based on nthis. Anything above a 2000 are "sfe to nuke" in my experience.
@abucci I'd like the pod to automatically nuke inactive accounts/feeds. Are you open to that? I _think_ internally there is enough data to go on (whether the user updated their avatar, whether the user updated their description, whether the user actually posted anything at all, etc) if you've seen a "Candidates for deletion" email, those cores are based on nthis. Anything above a 2000 are "sfe to nuke" in my experience.
@abucci +1 on "non-user-hostile captcha"
@abucci +1 on "non-user-hostile captcha"
@abucci +1 on "non-user-hostile captcha"
@abucci +1 on "non-user-hostile captcha"
@abucci Regarding:
> verify their email address
Do we want this? Would it help? We can verify email addresses without ever storing it, like we do now. Just send the email, wait for the "token link" to be opened/verified, then activated account.
@abucci Regarding:
> verify their email address
Do we want this? Would it help? We can verify email addresses without ever storing it, like we do now. Just send the email, wait for the "token link" to be opened/verified, then activated account.
@abucci Regarding:
> verify their email address
Do we want this? Would it help? We can verify email addresses without ever storing it, like we do now. Just send the email, wait for the "token link" to be opened/verified, then activated account.
@abucci Regarding:
> verify their email address
Do we want this? Would it help? We can verify email addresses without ever storing it, like we do now. Just send the email, wait for the "token link" to be opened/verified, then activated account.
@prologic That's what I mean. Just to put an obstacle/slow down in between signing up and actually having an account.
@prologic I don't know what you mean by "anything above 2000".
I'm not sure I'm comfortable with automatically nuking accounts. I think I'd rather look over the list myself and have the opportunity to modify which accounts are deleted. It seems like good practice to me to not automate administrator decisions that affect people. Yes, the vast majority of these accounts are probably not backed by real people who want to participate in a non-spammy way, but I don't like the notion of accidentally catching a person up in an algorithmic purging.
@abucci fair, I feel the same, probably why despite good heuristics (which is what that value is) I've never done it π
@abucci fair, I feel the same, probably why despite good heuristics (which is what that value is) I've never done it π
@abucci fair, I feel the same, probably why despite good heuristics (which is what that value is) I've never done it π
@abucci fair, I feel the same, probably why despite good heuristics (which is what that value is) I've never done it π
Also you've either a) not configured smtp on your pod or b) never received a "Candidates for deletion" email (yet) π
Also you've either a) not configured smtp on your pod or b) never received a "Candidates for deletion" email (yet) π
Also you've either a) not configured smtp on your pod or b) never received a "Candidates for deletion" email (yet) π
Also you've either a) not configured smtp on your pod or b) never received a "Candidates for deletion" email (yet) π
@prologic nope, never received that email. Is that new?
I *think* I set up SMTP but I'll have to double check that.
@abucci Been a feature for a few years now π€£
@abucci Been a feature for a few years now π€£
@abucci Been a feature for a few years now π€£
@abucci Been a feature for a few years now π€£
@prologic lol, as you can see I'm paying very close attention.
@abucci That's okay π
You don't have to in order ot enjoy the software π€£ I just have to pay attention to you and the community and not build or break shit people don't want π
@abucci That's okay π
You don't have to in order ot enjoy the software π€£ I just have to pay attention to you and the community and not build or break shit people don't want π
@abucci That's okay π
You don't have to in order ot enjoy the software π€£ I just have to pay attention to you and the community and not build or break shit people don't want π
@abucci That's okay π
You don't have to in order ot enjoy the software π€£ I just have to pay attention to you and the community and not build or break shit people don't want π