Firstly I think it's completely ineffective and unenforceable. The only way you're going to get this enforced is to somehow makes all the "big tech" companies oblighes, which some already are. But then you can just work-around it anyway. Okay if you start requiring things like state-enforced age verification like a driver's license or something, then things start getting even more weird.
Frankly I don't think it's the right approach. I think it will ultimately achieve nothing. It'll be just like the many numerous attempts at banning alcohol and drugs. Once you're addicted, there's no way you can stop people from indulging in stupid crap that may possibly kill them.
The only way out of this mess IMO is to educate people, educate the parents and to make it practices of targeting, categorization and the manipulation of content based on metadata either you or a 3rd-party questionable obtained illegal.
In other words. The very foundation of what "bit tech" social media companies thrive on. Make that illegal. Problem solve. But oh wait?! π€¦ββοΈ_
Firstly I think it's completely ineffective and unenforceable. The only way you're going to get this enforced is to somehow makes all the "big tech" companies oblighes, which some already are. But then you can just work-around it anyway. Okay if you start requiring things like state-enforced age verification like a driver's license or something, then things start getting even more weird.
Frankly I don't think it's the right approach. I think it will ultimately achieve nothing. It'll be just like the many numerous attempts at banning alcohol and drugs. Once you're addicted, there's no way you can stop people from indulging in stupid crap that may possibly kill them.
The only way out of this mess IMO is to educate people, educate the parents and to make it practices of targeting, categorization and the manipulation of content based on metadata either you or a 3rd-party questionable obtained illegal.
In other words. The very foundation of what "bit tech" social media companies thrive on. Make that illegal. Problem solve. But oh wait?! π€¦ββοΈ_
yarnd of late. Need to look into them...
yarnd of late. Need to look into them...
How am I suppose to know whether stuff like this (_sound serious_) is for realz or not? π
How am I suppose to know whether stuff like this (_sound serious_) is for realz or not? π
Hmmm π§
Hmmm π§
> That said, coming from platforms like X and Masto, where switching languages is easy, I naturally read content and write into my timeline in at least three languages. Changing my "account" is not a simple as switching languages, and in those platforms have another meaning ("I'm a different person"). Supporting that would be beneficial for some, though Iβm not sure how many would use it.
I _think_ this is more of a client concern in my opinion. Like @lyse said earlier though, sometimes he and @movq "Twt" in German. I don't (_nor anyone else I'm aware of_) have a problem with this. It seems to be that a "client" _could_ detect this and deal with this appropriately or give a user appropriately controls.
For me (_personally I've never found it a problem. I use extensions like "Simple Translate" anyway, so it doesn't matter a great deal to me._
> That said, coming from platforms like X and Masto, where switching languages is easy, I naturally read content and write into my timeline in at least three languages. Changing my "account" is not a simple as switching languages, and in those platforms have another meaning ("I'm a different person"). Supporting that would be beneficial for some, though Iβm not sure how many would use it.
I _think_ this is more of a client concern in my opinion. Like @lyse said earlier though, sometimes he and @movq "Twt" in German. I don't (_nor anyone else I'm aware of_) have a problem with this. It seems to be that a "client" _could_ detect this and deal with this appropriately or give a user appropriately controls.
For me (_personally I've never found it a problem. I use extensions like "Simple Translate" anyway, so it doesn't matter a great deal to me._
> Sure! From my research, Gemini (and likely Gopher as well) donβt have a similar header, so if a client is using those protocols, they wonβt be able to inform your server.
>
> So, itβs worth considering, would twtxt 2.0 only support HTTP/S?
I'm not sure how to standardize "Discovery" across different protocols for serving feeds, HTTP, Gopher, Gemini, etc. beyond what you initially suggested. But here's the thing, the
User-Agent HTTP Header isn't the only aspect to "discovery". Discovery in practise is more of an organic property of -mentions across feeds in the first place, something that crawlers take advantage of.
> Sure! From my research, Gemini (and likely Gopher as well) donβt have a similar header, so if a client is using those protocols, they wonβt be able to inform your server.
>
> So, itβs worth considering, would twtxt 2.0 only support HTTP/S?
I'm not sure how to standardize "Discovery" across different protocols for serving feeds, HTTP, Gopher, Gemini, etc. beyond what you initially suggested. But here's the thing, the
User-Agent HTTP Header isn't the only aspect to "discovery". Discovery in practise is more of an organic property of -mentions across feeds in the first place, something that crawlers take advantage of.
$ ./tools/inactive_users.sh 730
@thgie last seen 732 days ago
@will last seen 740 days ago
@shaneflores last seen 752 days ago
@magnus last seen 757 days ago
@nickmellor last seen 757 days ago
@birb last seen 763 days ago
@screem last seen 772 days ago
@servusdei last seen 774 days ago
@alex last seen 790 days ago
@andreottica last seen 801 days ago
@fox last seen 822 days ago
@anx last seen 829 days ago
@olav last seen 855 days ago
@caesar last seen 866 days ago
@jim last seen 869 days ago
@rell last seen 882 days ago
@readfog last seen 886 days ago
If anyone on this lists sees this post and wishes to preserve their feed/account for some reason (_beyonds backups I maintain_), please login at least once over the next coming weeks to get off this list. I will re-run this tool again, and then nuke blindly anything that matches >730 days of inactivity.
$ ./tools/inactive_users.sh 730
@thgie last seen 732 days ago
@will last seen 740 days ago
@shaneflores last seen 752 days ago
@magnus last seen 757 days ago
@nickmellor last seen 757 days ago
@birb last seen 763 days ago
@screem last seen 772 days ago
@servusdei last seen 774 days ago
@alex last seen 790 days ago
@andreottica last seen 801 days ago
@fox last seen 822 days ago
@anx last seen 829 days ago
@olav last seen 855 days ago
@caesar last seen 866 days ago
@jim last seen 869 days ago
@rell last seen 882 days ago
@readfog last seen 886 days ago
If anyone on this lists sees this post and wishes to preserve their feed/account for some reason (_beyonds backups I maintain_), please login at least once over the next coming weeks to get off this list. I will re-run this tool again, and then nuke blindly anything that matches >730 days of inactivity.