# 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 107
# self = https://watcher.sour.is/conv/x7e73va
Hey @jack π I like reading f your blog posts at https://www.baty.net/ π Do you feel like cross posting links to them at least on your Twt.social pod? π€ π
Hey @jack π I like reading f your blog posts at https://www.baty.net/ π Do you feel like cross posting links to them at least on your Twt.social pod? π€ π
@prologic @jack "@https://twtxt.net/user/jack/twtxt.txt>" - for a second I thought it was the other jack! πππ
@prologic @jack "jack" - for a second I thought it was the other jack! πππ
@prologic @jack "jack" - for a second I thought it was the other jack! πππ
@prologic @jack - I aggee with @adi here. Also the DM feature seems superfluous. For me the scope of the twtxt-ecosytem is a way to make publish post and have discussions in the open. There are plenty of DM/IM and blog services/system out there, and it should be up to each person to chose which of these they want to use instead of having another inbox to keep an eye on.
@prologic @jack - I aggee with @adi here. Also the DM feature seems superfluous. For me the scope of the twtxt-ecosytem is a way to make publish post and have discussions in the open. There are plenty of DM/IM and blog services/system out there, and it should be up to each person to chose which of these they want to use instead of having another inbox to keep an eye on.
@adi @darch you most misinterpreted what I meant π€£ I _only_ meant to cross-post (_as in Twt_) the announcement of the blog posts. I'm sure Ghost has some kind of "hooks" that could be used here? π€
@adi @darch you most misinterpreted what I meant π€£ I _only_ meant to cross-post (_as in Twt_) the announcement of the blog posts. I'm sure Ghost has some kind of "hooks" that could be used here? π€
@adi @darch you most misinterpreted what I meant π€£ I _only_ meant to cross-post (_as in Twt_) the announcement of the blog posts. I'm sure Ghost has some kind of "hooks" that could be used here? π€
@prologic @darch I understand we misinterpreted the twt, agree it's a good idea to twt his new blog posts but my opinion about the blog feature still stands.
@prologic @darch I understand we misinterpreted the twt, agree it's a good idea to twt his new blog posts but my opinion about the blog feature still stands.
@prologic @darch I understand we misinterpreted the twt, agree it's a good idea to twt his new blog posts but my opinion about the blog feature still stands.
@adi Can you share what those concerns are? Is this something we can address? I _still_ feel like its missing a few important features that are hard to get right, but yeah.
@adi Can you share what those concerns are? Is this something we can address? I _still_ feel like its missing a few important features that are hard to get right, but yeah.
@adi Can you share what those concerns are? Is this something we can address? I _still_ feel like its missing a few important features that are hard to get right, but yeah.
@prologic For now me and @darch agree that the blog feature is out of scope, that's the current issue. We're not sure about the DM system.
@prologic For now me and @darch agree that the blog feature is out of scope, that's the current issue. We're not sure about the DM system.
@prologic For now me and @darch agree that the blog feature is out of scope, that's the current issue. We're not sure about the DM system.
@adi @darch So what? You'd want to drop the blog feature altogether? π€ Drop the DM feature too?
@adi @darch So what? You'd want to drop the blog feature altogether? π€ Drop the DM feature too?
@adi @darch So what? You'd want to drop the blog feature altogether? π€ Drop the DM feature too?
@adi @darch Why? It's less than ~6% of the codebase. It's just a "long-form" way of, yeah it's not _quite_ twtxt, it stores the content differently, that's true. But why remove it entirely?~
@adi @darch Why? It's less than ~6% of the codebase. It's just a "long-form" way of, yeah it's not _quite_ twtxt, it stores the content differently, that's true. But why remove it entirely?~
@adi @darch Why? It's less than ~6% of the codebase. It's just a "long-form" way of, yeah it's not _quite_ twtxt, it stores the content differently, that's true. But why remove it entirely?~
@prologic @adi @darch Interesting. Looking forward to more details on your reasoning. I'm planning on twt.social being the only way I can interact with some users of my pod; in that case, I can see the utility in both features (even if they're out of scope, in spirit, maybe).
@prologic @adi @darch Interesting. Looking forward to more details on your reasoning. I'm planning on twt.social being the only way I can interact with some users of my pod; in that case, I can see the utility in both features (even if they're out of scope, in spirit, maybe).
@jlj I feel the same. Today twtxt.net is the only place where I Twt (short form) and Blog (long form)
@jlj I feel the same. Today twtxt.net is the only place where I Twt (short form) and Blog (long form)
@jlj I feel the same. Today twtxt.net is the only place where I Twt (short form) and Blog (long form)
@prologic @adi Yes, for me it makes more sense to get those features elsewhere. It is not about making the codebase more lean, but about making the core feature stand out. And insisting on the simplicity. Like you said no to polls. If you need polls you make a twt with a link to doodle.com or similar. It would still be good to have a way of knowing how to contact people directly. You can use the tagline for a the contact info you feel comfortable to sharing. Removing DM will also remove the potential issues of harassment and spam, that this channel could be used for.
@prologic @adi Yes, for me it makes more sense to get those features elsewhere. It is not about making the codebase more lean, but about making the core feature stand out. And insisting on the simplicity. Like you said no to polls. If you need polls you make a twt with a link to doodle.com or similar. It would still be good to have a way of knowing how to contact people directly. You can use the tagline for a the contact info you feel comfortable to sharing. Removing DM will also remove the potential issues of harassment and spam, that this channel could be used for.
@jlj @prologic @darch I *personally* would remove them because exactly that reason, it's not twtxt and less code is better I believe even if it's just 6%. I agree that maybe for some there's utility in that but @darch said it well:\n\n> For me the scope of the twtxt-ecosytem is a way to make publish post and have discussions in the open. There are plenty of DM/IM and blog services/system out there, and it should be up to each person to chose which of these they want to use instead of having another inbox to keep an eye on.
@jlj @prologic @darch I *personally* would remove them because exactly that reason, it's not twtxt and less code is better I believe even if it's just 6%. I agree that maybe for some there's utility in that but @darch said it well:
> For me the scope of the twtxt-ecosytem is a way to make publish post and have discussions in the open. There are plenty of DM/IM and blog services/system out there, and it should be up to each person to chose which of these they want to use instead of having another inbox to keep an eye on.
@jlj @prologic @darch I *personally* would remove them because exactly that reason, it's not twtxt and less code is better I believe even if it's just 6%. I agree that maybe for some there's utility in that but @darch said it well:\n\n> For me the scope of the twtxt-ecosytem is a way to make publish post and have discussions in the open. There are plenty of DM/IM and blog services/system out there, and it should be up to each person to chose which of these they want to use instead of having another inbox to keep an eye on.
@jlj @prologic @darch I *personally* would remove them because exactly that reason, it's not twtxt and less code is better I believe even if it's just 6%. I agree that maybe for some there's utility in that but @darch said it well:\n\n> For me the scope of the twtxt-ecosytem is a way to make publish post and have discussions in the open. There are plenty of DM/IM and blog services/system out there, and it should be up to each person to chose which of these they want to use instead of having another inbox to keep an eye on.
@adi @jlj @prologic @darch Here, I'm referring to the blog feature in @darch's twt. I'm still not sure about the DM system, I'd leave it for now.
@adi @jlj @prologic @darch Here, I'm referring to the blog feature in @darch's twt. I'm still not sure about the DM system, I'd leave it for now.
@adi @jlj @prologic @darch Here, I'm referring to the blog feature in @darch's twt. I'm still not sure about the DM system, I'd leave it for now.
@jlj @prologic @adi In a way there is no need to remove the blog and DM feature. Just give the pod admins an option to turn it off. That is what I would do the the day I set up my own pod.
@jlj @prologic @adi In a way there is no need to remove the blog and DM feature. Just give the pod admins an option to turn it off. That is what I would do the the day I set up my own pod.
@prologic @darch I personally, being also a techie would remove the code also.
@prologic @darch I personally, being also a techie would remove the code also.
@prologic @darch I personally, being also a techie would remove the code also.
@prologic @adi @darch I think having long form blog posts can drive discussion in the twts. Especially if you can reply to the blog posts using a twt.
@darch @prologic @adi Re harassment: Oh, I hadn't thought of that. And the pod administrator wouldn't have any oversight of that. That's concerning, outside of its potential utility. And public contact details in a tagline would be a decent substitute, I guess. π€
@darch @prologic @adi Re harassment: Oh, I hadn't thought of that. And the pod administrator wouldn't have any oversight of that. That's concerning, outside of its potential utility. And public contact details in a tagline would be a decent substitute, I guess. π€
@thewismit @prologic @adi Being able to use twtxt as a way to comment on other blogs is also a dream of mine. It would be a lot lighter than what the indiewebbers are doing. And it could be a blog hosted on your pod or elsewhere. The important thing is to give the user and/or admin options to chose the features the would like to use or not.
@thewismit @prologic @adi Being able to use twtxt as a way to comment on others blogs is also a dream of mine. It would be a lot lighter than what the indiewebbers are doing. And it could be a blog hosted on your pod or elsewhere. The important thing is to give the user and/or admin options to chose the features the would like to use or not.
@thewismit @prologic @adi Being able to use twtxt as a way to comment on others blogs is also a dream of mine. It would be a lot lighter than what the indiewebbers are doing. And it could be a blog hosted on your pod or elsewhere. The important thing is to give the user and/or admin options to chose the features the would like to use or not.
@jlj but if one user is harassing another user for direct messages donβt they have the ability to report them as violating the abuse policy? As the pod owner you donβt have the option of either talking to the abusive user and or removing their account entirely right?
@jlj but if one user is harassing another user for direct messages donβt they have the ability to report them as violating the abuse policy? As the pod owner you donβt have the option of either talking to the abusive user and or removing their account entirely right?
@jlj but if one user is harassing another user for direct messages donβt they have the ability to report them as violating the abuse policy? As the pod owner you donβt have the option of either talking to the abusive user and or removing their account entirely right?
@thewismit I agree re your comment on long form. I quite like the integration myself and would love to make it even more seamless myself.
@thewismit I agree re your comment on long form. I quite like the integration myself and would love to make it even more seamless myself.
@thewismit I agree re your comment on long form. I quite like the integration myself and would love to make it even more seamless myself.
One thing to keep in mind is that as a user of any pod there is no personal information stored whatsoever. We donβt even store to use this email address only a hash of it. so the utility of direct messages becomes important for cases like when the pod owner Hass to reach out to them because perhaps maybe theyβre violating the abuse policy and need a gentle reminder before being booted from that pod...
One thing to keep in mind is that as a user of any pod there is no personal information stored whatsoever. We donβt even store to use this email address only a hash of it. so the utility of direct messages becomes important for cases like when the pod owner Hass to reach out to them because perhaps maybe theyβre violating the abuse policy and need a gentle reminder before being booted from that pod...
One thing to keep in mind is that as a user of any pod there is no personal information stored whatsoever. We donβt even store to use this email address only a hash of it. so the utility of direct messages becomes important for cases like when the pod owner Hass to reach out to them because perhaps maybe theyβre violating the abuse policy and need a gentle reminder before being booted from that pod...
@prologic @adi @darch I like the blog feature. itβs not intrusive and if itβs not of interest it can be easily ignored. The blog feature is well within the original scope of the project, a way to freely share ideas. \nI have enjoyed reading many of the blog posts from community members
@prologic @adi @darch I like the blog feature. itβs not intrusive and if itβs not of interest it can be easily ignored. The blog feature is well within the original scope of the project, a way to freely share ideas.
I have enjoyed reading many of the blog posts from community members
@prologic @adi @darch I like the blog feature. itβs not intrusive and if itβs not of interest it can be easily ignored. The blog feature is well within the original scope of the project, a way to freely share ideas. \nI have enjoyed reading many of the blog posts from community members
@prologic Yeah, I guess I was -- spiralling out, I'll be the first to admit -- thinking about a scenario where the victim didn't feel comfortable reporting the harassment. Grounding the conversation once more, I _am_ happy with the current state of features and policies.
@prologic Yeah, I guess I was -- spiralling out, I'll be the first to admit -- thinking about a scenario where the victim didn't feel comfortable reporting the harassment. Grounding the conversation once more, I _am_ happy with the current state of features and policies.
@prologic Great point, re executing the aforementioned policies. Yeah, otherwise you have to have that conversation in public, which changes the dynamic completely: suddenly they can't simply step down gracefully, etc. And I love the long form too; want to use it regularly.
@prologic Great point, re executing the aforementioned policies. Yeah, otherwise you have to have that conversation in public, which changes the dynamic completely: suddenly they can't simply step down gracefully, etc. And I love the long form too; want to use it regularly.
Yup. l agree! π All good points all round πββοΈ Blog will stay and well continue to improve it.
DM is incomplete and lacks inter-pod capability, but the utility far outweighs not having a mechanism at all without adding additional PII on Users.
Yup. l agree! π All good points all round πββοΈ Blog will stay and well continue to improve it.
DM is incomplete and lacks inter-pod capability, but the utility far outweighs not having a mechanism at all without adding additional PII on Users.
Yup. l agree! π All good points all round πββοΈ Blog will stay and well continue to improve it.\n\nDM is incomplete and lacks inter-pod capability, but the utility far outweighs not having a mechanism at all without adding additional PII on Users.
Yup. l agree! π All good points all round πββοΈ Blog will stay and well continue to improve it.\n\nDM is incomplete and lacks inter-pod capability, but the utility far outweighs not having a mechanism at all without adding additional PII on Users.
@prologic Hey, thanks! Yes, I could certainly cross-post here. It would be manual for now but it's so easy, why not? :).
@prologic Hey, thanks! Yes, I could certainly cross-post here. It would be manual for now but it's so easy, why not? :).
@jack We did have a working twt CLI that _could_ have made this a breeze, but sadly it's broken at the moment (https://github.com/jointwt/twtxt/issues/340) π’ -- But you could just hit the API directly and cross-post when you publish a new blog post from Ghost?
@jack We did have a working twt CLI that _could_ have made this a breeze, but sadly it's broken at the moment (https://github.com/jointwt/twtxt/issues/340) π’ -- But you could just hit the API directly and cross-post when you publish a new blog post from Ghost?
@jack We did have a working twt CLI that _could_ have made this a breeze, but sadly it's broken at the moment (https://github.com/jointwt/twtxt/issues/340) π’ -- But you could just hit the API directly and cross-post when you publish a new blog post from Ghost?
@prologic Baty.net uses Hugo so I could look at adding a command to the Makefile I use to build/deploy it. It's hosted at Netlify so there could be something there, also.
@prologic Baty.net uses Hugo so I could look at adding a command to the Makefile I use to build/deploy it. It's hosted at Netlify so there could be something there, also.
@jack Oh cool! π LI like Hugo! For _some_ reason I _thought_ you were using Ghost π
@jack Oh cool! π LI like Hugo! For _some_ reason I _thought_ you were using Ghost π
@jack Oh cool! π LI like Hugo! For _some_ reason I _thought_ you were using Ghost π
@prologic My other, photography-centric blog, is using Ghost. (copingmechanism.com).
@prologic My other, photography-centric blog, is using Ghost. (copingmechanism.com).