No DNS can see it right now, so bluesky can't detect it either.
If you are sure that both the record name is correct as well as the domain name, give it at least an hour and check then try again on bluesky.
If you are sure that both the record name is correct as well as the domain name, give it at least an hour and check then try again on bluesky.
August 18, 2023 at 11:13 PM
No DNS can see it right now, so bluesky can't detect it either.
If you are sure that both the record name is correct as well as the domain name, give it at least an hour and check then try again on bluesky.
If you are sure that both the record name is correct as well as the domain name, give it at least an hour and check then try again on bluesky.
I've compared mine with yours, and _atproto does return nothing on your domain.
Looks like it's either still updating and it might take a while, or you might have made a typo.
Looks like it's either still updating and it might take a while, or you might have made a typo.
August 18, 2023 at 11:09 PM
I've compared mine with yours, and _atproto does return nothing on your domain.
Looks like it's either still updating and it might take a while, or you might have made a typo.
Looks like it's either still updating and it might take a while, or you might have made a typo.
I just noticed that mxtoolbox.com doesn't detect all TXT records, so my initial reply may have been wrong and the _atproto record might have existed already, oops.
Either way, redoing the setup from scratch like you've said should solve it, I think
Either way, redoing the setup from scratch like you've said should solve it, I think
August 18, 2023 at 10:39 PM
I just noticed that mxtoolbox.com doesn't detect all TXT records, so my initial reply may have been wrong and the _atproto record might have existed already, oops.
Either way, redoing the setup from scratch like you've said should solve it, I think
Either way, redoing the setup from scratch like you've said should solve it, I think
Your domain doesn't seem to be configured properly. Double check to make sure you have the _atproto txt record set.
https://mxtoolbox.com/SuperTool.aspx?action=txt%3alivialamblet.com&run=toolpage
https://mxtoolbox.com/SuperTool.aspx?action=txt%3alivialamblet.com&run=toolpage
August 18, 2023 at 9:51 PM
Your domain doesn't seem to be configured properly. Double check to make sure you have the _atproto txt record set.
https://mxtoolbox.com/SuperTool.aspx?action=txt%3alivialamblet.com&run=toolpage
https://mxtoolbox.com/SuperTool.aspx?action=txt%3alivialamblet.com&run=toolpage
The blog post and proposals talk about different mechanisms that are still being discussed and don't yet exist.
As for the community guidelines for Bluesky social itself, they go into effect on July 14, 2023
As for the community guidelines for Bluesky social itself, they go into effect on July 14, 2023
July 6, 2023 at 11:56 PM
The blog post and proposals talk about different mechanisms that are still being discussed and don't yet exist.
As for the community guidelines for Bluesky social itself, they go into effect on July 14, 2023
As for the community guidelines for Bluesky social itself, they go into effect on July 14, 2023
As for labeling, I don't see how that's an issue unless the goal is to force some people to see content they do not want to see.
As far as I see it, bluesky's goal is to allow everyone to see (or not see) whatever content they desire; while providing a sensible default.
As far as I see it, bluesky's goal is to allow everyone to see (or not see) whatever content they desire; while providing a sensible default.
June 24, 2023 at 1:04 AM
As for labeling, I don't see how that's an issue unless the goal is to force some people to see content they do not want to see.
As far as I see it, bluesky's goal is to allow everyone to see (or not see) whatever content they desire; while providing a sensible default.
As far as I see it, bluesky's goal is to allow everyone to see (or not see) whatever content they desire; while providing a sensible default.
The first and fourth amendments apply to the government!
Also I don't understand the communication infrastructure point.
Nothing stops you or anyone from starting their own provider, while still participating in the network.
Also, DMCA *requires* providers to take down content ASAP.
Also I don't understand the communication infrastructure point.
Nothing stops you or anyone from starting their own provider, while still participating in the network.
Also, DMCA *requires* providers to take down content ASAP.
June 24, 2023 at 1:01 AM
The first and fourth amendments apply to the government!
Also I don't understand the communication infrastructure point.
Nothing stops you or anyone from starting their own provider, while still participating in the network.
Also, DMCA *requires* providers to take down content ASAP.
Also I don't understand the communication infrastructure point.
Nothing stops you or anyone from starting their own provider, while still participating in the network.
Also, DMCA *requires* providers to take down content ASAP.
Moderation tools, including both mandatory provider-applied labels (for i.e. csam) and user-configurable labels, are crucial for legal compliance and more.
Being federated/decentralized shouldn't mean ignoring essential features.
Being federated/decentralized shouldn't mean ignoring essential features.
June 24, 2023 at 12:43 AM
Moderation tools, including both mandatory provider-applied labels (for i.e. csam) and user-configurable labels, are crucial for legal compliance and more.
Being federated/decentralized shouldn't mean ignoring essential features.
Being federated/decentralized shouldn't mean ignoring essential features.
