> What would you, as an end user, do if someone stood up a yarn pod full of assholes who all collectively decided to twt at you all day every day?
Right now (without Activity Pub) I wouldn't know. It wouldn't hurt me, I don't follow those "assholes", I don't have to. I don't pull their feed(s).
However (which is the point ) if I have Activity Pub integrated and turned on, I have no choice now. Those same "assholes" can send me shit all day, every day, and there isn't anything I can do about it. My options then become to administratively block them at the server or OS level. What if I don't have administrative control?
> What would you, as an end user, do if someone stood up a yarn pod full of assholes who all collectively decided to twt at you all day every day?
Right now (without Activity Pub) I wouldn't know. It wouldn't hurt me, I don't follow those "assholes", I don't have to. I don't pull their feed(s).
However (which is the point ) if I have Activity Pub integrated and turned on, I have no choice now. Those same "assholes" can send me shit all day, every day, and there isn't anything I can do about it. My options then become to administratively block them at the server or OS level. What if I don't have administrative control?
> What would you, as an end user, do if someone stood up a yarn pod full of assholes who all collectively decided to twt at you all day every day?
Right now (without Activity Pub) I wouldn't know. It wouldn't hurt me, I don't follow those "assholes", I don't have to. I don't pull their feed(s).
However (which is the point ) if I have Activity Pub integrated and turned on, I have no choice now. Those same "assholes" can send me shit all day, every day, and there isn't anything I can do about it. My options then become to administratively block them at the server or OS level. What if I don't have administrative control?
> What would you, as an end user, do if someone stood up a yarn pod full of assholes who all collectively decided to twt at you all day every day?
Right now (without Activity Pub) I wouldn't know. It wouldn't hurt me, I don't follow those "assholes", I don't have to. I don't pull their feed(s).
However (which is the point ) if I have Activity Pub integrated and turned on, I have no choice now. Those same "assholes" can send me shit all day, every day, and there isn't anything I can do about it. My options then become to administratively block them at the server or OS level. What if I don't have administrative control?
If we decide that the benefits outweigh the risks and accept that differences (even though we'll do our best to bridge the gaps) -- we'll have to make "Enabling" / "Disabling" an actual thing. being an experimental feature flag is not enough, feature flags are designed to be short-lived until promoted, or decided against.
The question then becomes more along the lines of:
- Do we want a toggle for Activity Pub at the Pod level? (I assume yes)
- Do we want a toggle for Activity Pub discovery at the User level?
If we decide that the benefits outweigh the risks and accept that differences (even though we'll do our best to bridge the gaps) -- we'll have to make "Enabling" / "Disabling" an actual thing. being an experimental feature flag is not enough, feature flags are designed to be short-lived until promoted, or decided against.
The question then becomes more along the lines of:
- Do we want a toggle for Activity Pub at the Pod level? (I assume yes)
- Do we want a toggle for Activity Pub discovery at the User level?
If we decide that the benefits outweigh the risks and accept that differences (even though we'll do our best to bridge the gaps) -- we'll have to make "Enabling" / "Disabling" an actual thing. being an experimental feature flag is not enough, feature flags are designed to be short-lived until promoted, or decided against.
The question then becomes more along the lines of:
- Do we want a toggle for Activity Pub at the Pod level? (I assume yes)
- Do we want a toggle for Activity Pub discovery at the User level?
If we decide that the benefits outweigh the risks and accept that differences (even though we'll do our best to bridge the gaps) -- we'll have to make "Enabling" / "Disabling" an actual thing. being an experimental feature flag is not enough, feature flags are designed to be short-lived until promoted, or decided against.
The question then becomes more along the lines of:
- Do we want a toggle for Activity Pub at the Pod level? (I assume yes)
- Do we want a toggle for Activity Pub discovery at the User level?
Undo+Follow activities to actors you no longer want to follow (missing right now)Problem that I've found in practise however is that even for a tiny pod (used for development) I'm seeing interacting with servers I never interacted with (ever).
Undo+Follow activities to actors you no longer want to follow (missing right now)Problem that I've found in practise however is that even for a tiny pod (used for development) I'm seeing interacting with servers I never interacted with (ever).
Undo+Follow activities to actors you no longer want to follow (missing right now)Problem that I've found in practise however is that even for a tiny pod (used for development) I'm seeing interacting with servers I never interacted with (ever).
Undo+Follow activities to actors you no longer want to follow (missing right now)Problem that I've found in practise however is that even for a tiny pod (used for development) I'm seeing interacting with servers I never interacted with (ever).
You jsut need to configure it as per the description.
You jsut need to configure it as per the description.
You jsut need to configure it as per the description.
You jsut need to configure it as per the description.
https://www.youtube.com/watch?v=QOm1-PFsLv0
https://www.youtube.com/watch?v=QOm1-PFsLv0
https://www.youtube.com/watch?v=QOm1-PFsLv0
https://www.youtube.com/watch?v=QOm1-PFsLv0
> Freedom of speech / Freedom to shout
Basically every other social media platform really. All centralised ones like Facebook, Twitter, etc, and push-based ones fall into this category too 👌
Where what we have built with Yarn.social / Twtxt is really:
> Freedom to listen
Where we have full control of what we "pull", or not (Follow/Unfollow). I also like what we were talking about in the call where we describe the interactions as:
> I write something down on paper, and post it outside my mailbox/house.
> Someone drives by and reads it and is intuiged.
> That someone then writes down their own thoughts and replies on their own paper and posted it by their mailbox.
> You come along and see it one day, and decide to further erply.
In this way Yarn / Twtxt is _much slower_, but that's by design.
> Freedom of speech / Freedom to shout
Basically every other social media platform really. All centralised ones like Facebook, Twitter, etc, and push-based ones fall into this category too 👌
Where what we have built with Yarn.social / Twtxt is really:
> Freedom to listen
Where we have full control of what we "pull", or not (Follow/Unfollow). I also like what we were talking about in the call where we describe the interactions as:
> I write something down on paper, and post it outside my mailbox/house.
> Someone drives by and reads it and is intuiged.
> That someone then writes down their own thoughts and replies on their own paper and posted it by their mailbox.
> You come along and see it one day, and decide to further erply.
In this way Yarn / Twtxt is _much slower_, but that's by design.
> Freedom of speech / Freedom to shout
Basically every other social media platform really. All centralised ones like Facebook, Twitter, etc, and push-based ones fall into this category too 👌
Where what we have built with Yarn.social / Twtxt is really:
> Freedom to listen
Where we have full control of what we "pull", or not (Follow/Unfollow). I also like what we were talking about in the call where we describe the interactions as:
> I write something down on paper, and post it outside my mailbox/house.
> Someone drives by and reads it and is intuiged.
> That someone then writes down their own thoughts and replies on their own paper and posted it by their mailbox.
> You come along and see it one day, and decide to further erply.
In this way Yarn / Twtxt is _much slower_, but that's by design.
> Freedom of speech / Freedom to shout
Basically every other social media platform really. All centralised ones like Facebook, Twitter, etc, and push-based ones fall into this category too 👌
Where what we have built with Yarn.social / Twtxt is really:
> Freedom to listen
Where we have full control of what we "pull", or not (Follow/Unfollow). I also like what we were talking about in the call where we describe the interactions as:
> I write something down on paper, and post it outside my mailbox/house.
> Someone drives by and reads it and is intuiged.
> That someone then writes down their own thoughts and replies on their own paper and posted it by their mailbox.
> You come along and see it one day, and decide to further erply.
In this way Yarn / Twtxt is _much slower_, but that's by design.
There are still some outstanding issues that would need to be improved if we continued this regardless
Some thoughts being discussed:
- Yarn.social pods are more of a "family", where you invite people into your "home" or "community"
- Opening up to the "Fedivise" is potentially "uncontrolled"
- Even at a small scale (a tiny dev pod) we see activities from servers never interacted with before
- The possibility of abuse (because basically anything can POST things to your Pod now)
- Pull vs. Push model polarising models/views which whilst in theory _can_ be made to work, should they?
Go! 👏_
There are still some outstanding issues that would need to be improved if we continued this regardless
Some thoughts being discussed:
- Yarn.social pods are more of a "family", where you invite people into your "home" or "community"
- Opening up to the "Fedivise" is potentially "uncontrolled"
- Even at a small scale (a tiny dev pod) we see activities from servers never interacted with before
- The possibility of abuse (because basically anything can POST things to your Pod now)
- Pull vs. Push model polarising models/views which whilst in theory _can_ be made to work, should they?
Go! 👏_
There are still some outstanding issues that would need to be improved if we continued this regardless
Some thoughts being discussed:
- Yarn.social pods are more of a "family", where you invite people into your "home" or "community"
- Opening up to the "Fedivise" is potentially "uncontrolled"
- Even at a small scale (a tiny dev pod) we see activities from servers never interacted with before
- The possibility of abuse (because basically anything can POST things to your Pod now)
- Pull vs. Push model polarising models/views which whilst in theory _can_ be made to work, should they?
Go! 👏_
There are still some outstanding issues that would need to be improved if we continued this regardless
Some thoughts being discussed:
- Yarn.social pods are more of a "family", where you invite people into your "home" or "community"
- Opening up to the "Fedivise" is potentially "uncontrolled"
- Even at a small scale (a tiny dev pod) we see activities from servers never interacted with before
- The possibility of abuse (because basically anything can POST things to your Pod now)
- Pull vs. Push model polarising models/views which whilst in theory _can_ be made to work, should they?
Go! 👏_
