Email or username:

Password:

Forgot your password?
dansup's posts Post Back to profile
Top-level
Brian Hawthorne

@dansup I’m not sure what you mean by “your” thread. Once you have made a post, it is out there in the fediverse. It is still your post, as are any followup posts you make in reply. But it’s not “your” thread. They are just replies to your post.

Anyone who doesn’t want to see the argument can mute or block them, but it sounds like you are asking for the ability to block those comments for EVERYONE, not just yourself. Please let the rest of us make our own decisions as to what we see.

I mean if they are making comments that violate their instances rules, (e.g., racism) then by all means report them, but if you just don’t like their passion? Let it go.

23 Aug 2023 at 13:59 | Wall-to-wall | Open on infosec.exchange
3 comments
dansup

@bhawthorne if you make a "top level" post, you're damn rights it's "your" thread and I'm going to give the control to the owner of that thread.

I assume your American by your entitled viewpoint, just because data is available doesn't give you any rights over it.

23 Aug 2023 at 14:02 | Open on mastodon.social
Brian Hawthorne

@dansup Entitled? I think you have that backwards. The top-level posts and any comments you make are your data. If you choose to federate with my instance, and your posts are published publicly, then I have the “right” to read them, think about them, and refer to them. That’s what federation means. I do not have the right to copy them and have no ownership in your data.

The posts I make, whether or not they are replies are my data. And the above applies to my posts too. If one of my posts happens to include in its in-reply-to field the unique identifier assigned to one of your posts, that does not give you ownership of my data. I still own my reply. You still own your post.

So what is a thread? It is just the group of individually owned posts that are linked back to a common post by they in-reply-to fields. How that collection should appear is not defined by ActivityPub. Threads are an ephemeral and emergent property of ActivityPub objects. The word is mentioned just once in the spec (w3.org/TR/activitypub/).

So, you control all of your posts. I control all of my posts. You can control what you see. I can control what I see. You own the portions of a thread that are your posts. I own the portions of a thread that are my posts. Nobody owns the thread itself because it is not an entity in ActivityPub.

And no, just because people are replying to one of your posts, you do not get any ownership over their reply posts, nor do you have any ownership or control of how other people reply to your public posts.

If you want more control, then mark your post as “Mentioned People Only”, and then you can control who is allowed to reply to your post.

@dansup Entitled? I think you have that backwards. The top-level posts and any comments you make are your data. If you choose to federate with my instance, and your posts are published publicly, then I have the “right” to read them, think about them, and refer to them. That’s what federation means. I do not have the right to copy them and have no ownership in your data.

23 Aug 2023 at 16:10 | Open on infosec.exchange
Brian Hawthorne

@dansup And by the way, thinking that just because you started a public conversation that you therefore are entitled to control over what other people subsequently say in that conversation is the definition of entitlement.

I’m surprised at your response Dan. Up to know I’ve been a happy Pixelfed user, but being called an “entitled American” by the developer does not give me warm fuzzy feelings.

23 Aug 2023 at 16:19 | Open on infosec.exchange
Go Up