#eeee — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #eeee, aggregated by home.social.
-
Contact, Eleanor Swordy
I don't wear contacts and this moment is really strange, I can't believe people do it. I don't like using eyedrops, either. I was just looking at this artist's website for a minute and really enjoy her unusual style and subject matter 👀
-
Contact, Eleanor Swordy
I don't wear contacts and this moment is really strange, I can't believe people do it. I don't like using eyedrops, either. I was just looking at this artist's website for a minute and really enjoy her unusual style and subject matter 👀
-
Contact, Eleanor Swordy
I don't wear contacts and this moment is really strange, I can't believe people do it. I don't like using eyedrops, either. I was just looking at this artist's website for a minute and really enjoy her unusual style and subject matter 👀
-
@blogdiva - I know the feeling. I blogged for a time years ago and subjected myself to small-town gop events, which are identical and creeeeeeeppeeeeee
-
@blogdiva - I know the feeling. I blogged for a time years ago and subjected myself to small-town gop events, which are identical and creeeeeeeppeeeeee
-
The 3rd argument for defederation:
➡️ To defend against being Embraced, Extended, and Extinguished.
This is a real risk, and others point to Google and Facebook and XMPP, or Google and RSS Google reader. Where a big entity takes over, then rug pulls or extends an open standard slowly into an non-standard, non-interoperable functionally siloed service.
This is a real risk. But you don't - and can't - defend against this by defederation. I'll explain why next. #EEEE
🧵 3 of N
-
The 3rd argument for defederation:
➡️ To defend against being Embraced, Extended, and Extinguished.
This is a real risk, and others point to Google and Facebook and XMPP, or Google and RSS Google reader. Where a big entity takes over, then rug pulls or extends an open standard slowly into an non-standard, non-interoperable functionally siloed service.
This is a real risk. But you don't - and can't - defend against this by defederation. I'll explain why next. #EEEE
🧵 3 of N
-
The 3rd argument for defederation:
➡️ To defend against being Embraced, Extended, and Extinguished.
This is a real risk, and others point to Google and Facebook and XMPP, or Google and RSS Google reader. Where a big entity takes over, then rug pulls or extends an open standard slowly into an non-standard, non-interoperable functionally siloed service.
This is a real risk. But you don't - and can't - defend against this by defederation. I'll explain why next. #EEEE
🧵 3 of N
-
The 3rd argument for defederation:
➡️ To defend against being Embraced, Extended, and Extinguished.
This is a real risk, and others point to Google and Facebook and XMPP, or Google and RSS Google reader. Where a big entity takes over, then rug pulls or extends an open standard slowly into an non-standard, non-interoperable functionally siloed service.
This is a real risk. But you don't - and can't - defend against this by defederation. I'll explain why next. #EEEE
🧵 3 of N
-
The 3rd argument for defederation:
➡️ To defend against being Embraced, Extended, and Extinguished.
This is a real risk, and others point to Google and Facebook and XMPP, or Google and RSS Google reader. Where a big entity takes over, then rug pulls or extends an open standard slowly into an non-standard, non-interoperable functionally siloed service.
This is a real risk. But you don't - and can't - defend against this by defederation. I'll explain why next. #EEEE
🧵 3 of N
-
The 2nd argument for preemptive defederation:
➡️ To defend against poorly moderated P92 users & ad spam.
We have all the tools for that now - as users & as admins, and deal with exactly this from poorly moderated servers EVERY. SINGLE. DAY. And if we find ANY server not responsive THEN we block. Protecting our users is our 1st job but we have all we need - WITHOUT first strike defederation.
The third argument I'll look at next is to avoid #EEEE - "Embrace, Extend, and Extinguish."
🧵 2 of X
-
The 2nd argument for preemptive defederation:
➡️ To defend against poorly moderated P92 users & ad spam.
We have all the tools for that now - as users & as admins, and deal with exactly this from poorly moderated servers EVERY. SINGLE. DAY. And if we find ANY server not responsive THEN we block. Protecting our users is our 1st job but we have all we need - WITHOUT first strike defederation.
The third argument I'll look at next is to avoid #EEEE - "Embrace, Extend, and Extinguish."
🧵 2 of X
-
The 2nd argument for preemptive defederation:
➡️ To defend against poorly moderated P92 users & ad spam.
We have all the tools for that now - as users & as admins, and deal with exactly this from poorly moderated servers EVERY. SINGLE. DAY. And if we find ANY server not responsive THEN we block. Protecting our users is our 1st job but we have all we need - WITHOUT first strike defederation.
The third argument I'll look at next is to avoid #EEEE - "Embrace, Extend, and Extinguish."
🧵 2 of X
-
The 2nd argument for preemptive defederation:
➡️ To defend against poorly moderated P92 users & ad spam.
We have all the tools for that now - as users & as admins, and deal with exactly this from poorly moderated servers EVERY. SINGLE. DAY. And if we find ANY server not responsive THEN we block. Protecting our users is our 1st job but we have all we need - WITHOUT first strike defederation.
The third argument I'll look at next is to avoid #EEEE - "Embrace, Extend, and Extinguish."
🧵 2 of X
-
The 2nd argument for preemptive defederation:
➡️ To defend against poorly moderated P92 users & ad spam.
We have all the tools for that now - as users & as admins, and deal with exactly this from poorly moderated servers EVERY. SINGLE. DAY. And if we find ANY server not responsive THEN we block. Protecting our users is our 1st job but we have all we need - WITHOUT first strike defederation.
The third argument I'll look at next is to avoid #EEEE - "Embrace, Extend, and Extinguish."
🧵 2 of X
