flipboard.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Welcome to Flipboard on Mastodon. A place for our community of curators and enthusiasts to inform and inspire each other. If you'd like to join please request an invitation via the sign-up page.

Administered by:

Server stats:

1K
active users

Mike McCue

A thread on some tenets regarding open systems I feel compelled to relay:

- It’s extremely hard for open to ever compete with closed. It almost never succeeds.

- Every now and then open is given a chance due to unprecedented external events or pressures.

- In the rare event that open gains momentum, any actor can adopt it. That’s the point.

- The actors who adopt open will inevitably range from good to indifferent to bad.

1/

- There need to be mechanisms to prevent the bad actors from screwing things up, to reward the good actors, and to educate the indifferent so they appreciate their new found openness.

- Most people outside the tech industry don’t understand open and aren’t motivated to switch to something just because it’s open.

- If open looks and feels the same as closed, closed will win.

- If open is more confusing than closed, closed will win.

2/

- If those who have been working on open revert to closed in the name of preventing bad actors, closed will win.

- If open wins we get things like the web. Imperfect but far greater for humanity than most everyone being online via AOL.

- We’re at a precious moment in time for the fediverse. When it comes to social media, open has a real chance right now. And closed is on the ropes. Let’s not blow it.

@mike “If open looks and feels the same as closed, closed will win.”

Not sure I fully agree with this one. Definitely agree with all the others, but if the general look and feel of an open system looks like the closed one, the design and UX of it is probably quite good … as long as it’s not exactly like the closed system, because the closed system might have some dark patterns in there that work to lock in and retain users.

What are your thoughts here?

@mike Are you saying that if the two products are the same, then the closed system has business resources and other advantages that give them the competitive edge over the open system? Because that I generally agree with, but I’m not sure it’s always a cut and dry case.

@Brendanjones You make a good point that familiarity is helpful. i.e. I don't have to relearn something from scratch. The point I was getting at is that it's not enough for the open experience to be the same... it has to be fundamentally better to motivate people to switch.

This happened with AOL vs. the web. When really cool web sites emerged that were far better than anything AOL could do on their own, people switched. If the web was just a carbon copy of AOL, nobody would have switched.

@mike @Brendanjones re: "it's not enough for the open experience to be the same"
100% agree. I would add that closed has expensive & powerful resources that open often does not, such as marketing, sales, & connected partnerships that act as market movers. These aren't necessarily merit based drivers for adoption but - all other things being equal - can crush competition.

Open has to have a value differentiator that target customers/users recognize or it will be relegated to being an also-ran.

@mike preventing bad actors and promoting (or make the way easier)efor the good… isn't that a little bit opposed to being open ? Openess is based on liberties tu use/modify/distribute and some constraint (to respect/propagate the licence). It seems that any restriction to such openess would… make the software not open.

But I use "seems" since their may be smart ways to enforce some kind of good behavior policy (mastodon ability ban "bad instance" is a good exemple).

@mike

Interestingly, this also applies to things like resource management and community governance, regardless of the level of “tech” involved.

We humans need much more open, across the board.

@mike I think the big problem is that developers who understand open most of the times don't understand marketing.
To say it in another way: Basically EVERYTHING you mentioned comes down to money - and no, not the money the user has to spend, but about the money the developers (i.e. companies) spend on marketing and lobbying.
Marketing works - look no further than to Apple.
"Open" has the issue that there is no big marketing campaign, no lobbying money and no coordination - and as such loses.

@mike This is one reason why the most successful open projects are part of foundations. LF does a good job marketing things like CNCF.

@mike
So what can open do that closed can't?
Of those things, which will appeal to people and be easy to demonstrate?

@CassandraVert That is exactly the right question to be asking. At the moment open means access to a lot more people and content. And there are a lot of services like kbin, Lemmy, pixelfed beyond mastodon that work reasonably well together.

But that's just the start. Open versions of closed systems (Twitter, Reddit, Instagram, etc) are very useful to have but it'll be exciting to see what innovative new directions these services can go and what totally new services launch next year.

@mike
New technology first appears in relation to existing tech. For example, the first cars were designed after carriages and were called horseless carriages. Eventually they explored new designs.
But the open web has been around for 20 years, as people keep mentioning. Was it abandoned? Did no one beyond Gargron try to run with it? Are we going through the new adaptation phase again?

@CassandraVert Yes we are going through the new adaptation phase again for the social web which is the newest and most powerful part of the web. i.e. the web connects web sites. the social web connects people, web sites and posts. It is infinitely more powerful and the range of innovation and new opportunities is massive.

@mike

Completely agree we are in a moment in time that is precious and we will not easily get another chance at this. The real prospect of a broad based open social web is incredibly exciting.

For it to succeed, users will need explicit protections from surveillance and exploitation. Open will not work if users feel like they are just throwing open the door for all their thoughts and ideas to be hoovered up and processed into sophisticated personalized influence campaigns.

1/

@mike

It therefore becomes incumbent on those who are building the protocols and applications to communicate the value proposition. Not just the wonderful future that such interoperability will give users. Also, the comfort they can derive from technical features and legal terms, ensuring them that their personal data and content contributions will not be exploited without their consent.

@mastodonmigration I think there are some important actions to take in the coming months to prepare for the federation with threads. Has anyone made a list of key things we should focus on to protect people in the fediverse? For example @evan talked recently about the importance of being able to delete replies from a thread you started. I think people should also be able to opt out of quote posts as another example. Is there a group of people already talking about this?

@mike @evan

Technical features are one thing. Not familiar with any organized work, but that doesn't mean there isn't any. But the other area which would go a very long way to addressing user concerns is explicit public data use and privacy terms. Thinking of an opt-in/out-out framework that gives users explicit control over their content and personal data. Such frameworks, particularly in the EU, are now common for internet services. If we want open social to work, we should do it here too.

@mastodonmigration @evan great point. Mastodon already has a number of these built in which is a good start.

@mike @evan

Kind of. Actually, the Mastodon Privacy Policy is very limited. It really only gives the instance the right to republish content and not share personal data. When user information and content starts crossing commercial entity lines things get much less defined and potentially problematic. Corporate applications have much different terms and many include license agreements for various purposes, including commercial purposes, which of course users agree to when they sign up.

1/

@mike @evan

So, how do rights track content and personal data around this new open social web? If we can answer these questions and construct a satisfactory framework for both users and providers, before it turns into a mess and regulatory solutions start being fought over and mandated, we'd be way ahead and off to the races.

@mike @mastodonmigration @evan Blocking threads/meta *is* part of being the open social web, because it's a necessary act of defense to keep us from becoming absorbed into Facebook

like there NEEDS to be a part of federated social media that has no Facebook connection at all, in case Facebook tries some sort of buyout or copyright lawsuit or buying servers or incorporating proprietary tools or whatever

@mike @mastodonmigration @evan To use a capitalist/business comparison (ugh), it's like refusing to let Walmart carry your products being a defense of your business, because at some point you will either be beholden to Walmart supply chains or standards or such, or Walmart selling your products will mean *no one* is buying them from you anymore, etc

@mike @mastodonmigration @evan and then, your/your invention's/business's fate is entirely tied to Walmart, and that's worked out really poorly for people who've either sold out, been bought out, or been overwhelmed, because when the Walmart fails or goes out locally - they can't just pick up and start where they were before that

@mike @mastodonmigration @evan either way, the best idea is to keep Big Blue Corporation out in the first place, *before* they devour and engulf everything special, unique, local - and then either run away with it or implode

@mike @mastodonmigration @evan

This is a 5 months old list of PR’s for Mastodon I created when threads announced federation, over holiday break was going to look at which made it into mastodon 4.2 or which new ones should added or old removed. docs.google.com/spreadsheets/d

docs.google.comKey Features for Mastodon / ActivtyPub Prior to Threads Launch - Google Drive

@mike back in June or July @tchambers was collecting recommendations at the product level. Here's the ones I had via @thenexusofprivacy - infosec.exchange/@thenexusofpr there's a link out to the (draft) privacy threat model that goes into more detail.

@mastodonmigration

Infosec ExchangeThe Nexus of Privacy (@thenexusofprivacy@infosec.exchange)Recommendations for how Mastodon and other Fedivese solftware needs to evolve to deal with Threads @tchambers@indieweb.social, these are from the "Recommendations" section at the end of https://privacy.thenexus.today/fediverse-threat-modeling-privacy-and-meta/#developers -- the main text discusses the rationale (although, it's a draft). * "Privacy by default": Set defaults so that people start with stronger privacy protections, and can then choose to give it up. For example, make "Authorized Fetch" the default setting, and ensure documention explains it well. * Develop processes and tooling for blocking Meta instances and all instances that federate with them. For example, extend nodeinfo to have a field with an instance's policy towards Meta (transitively block, block but federate with instances that federate with Meta domains, federate with Meta domains). Investigate solutions for blocklists Meta and federating-with-Meta domains (taking into account that there are likely to be a huge number of them hosted on different domains), and for allow-lists for instances that don't share data with Meta * Investigate shifting to allow-list federation, and look at alternative approaches like "approval first" federation. * Reduce the number of public pages and the amount of data in them, including supporting private profiles, increasing use of non-public visibility like local-only posts, investigating new visibility levels like "viewable only to people logged into instances that don't federate with Meta", differentiating between what's shown at different levels of visibility, and (potentially) requiring login to view unlisted statuses * Provide a usable way for instances and individual users to protect all profiles, timelines, statuses, images, etc from anonymous access. * Provide control for individuals and sites to determine whether RSS feeds are available, and implement an option to remove unlisted statuses from RSS feeds * Educate people on (and potentially package) existing processes and tools for IP Blocking, integrate with suspend/limit federation-level processes and infrastructure, and potentially develop new tools and look for ways to address downsides. * Look at potential app-based dataflows and potential counter-measures, possibly including allow- and block-lists for apps as well * Pursue funding from anti-surveillance-capitalism companies, civil society groups, governments, and crowdfunding to allow more detailed analysis, design, and rapid implementation of privacy and safety features – and ensure that the funding is directed in a way that increases equity and diversity. * Press the project leaders to prioritize privacy and safety in their planning. If they don't, consider voting with your feet and creating a fork that prioritizes privacy and safety (as well as equity, usability, onboarding and all the other issues that need to be prioritized). #fediverse #mastodon #threads @fediverse@lemmy.ml @fediversenews@venera.social

@mike also here's a concrete project -- not just focused on Meta -- that could be a good next step. I submitted at the last minute to NLNet, and didn't have any EU folks involved or dev projects committed to work on it, so not surprisingly it didn't get funded, but it's an interesting starting point.

nexusofprivacy.net/ipsfs-nlnet

The Nexus Of Privacy · Improving privacy and safety in fediverse softwareA resource page for a work on threat modeling and other approaches to improve the fediverse.

@mastodonmigration @mike the skills to do this are very different to the ones needed in architecture, developing, and managing systems. Often those soft skills are where open loses out because the commercial model around closed knows they are a cost of doing business. Some projects do an amazing job with inclusive and welcoming community. Others just rely on rtfm and snark

@mastodonmigration @mike @kissane

Some very useful and detailed observations in the item below. Risk mitigation will have to be robust and constantly monitored as threats evolve if success & safety are to be found. A key point is that a great many users of mastodon reside within the crosshairs of hardcore zealots on other platforms aiming to neutralize their voices. How federation is managed (or not) may afford those zealots useful operational cloaks.

mas.to/@kissane/11162093008161

mas.toErin Kissane (@kissane@mas.to)I needed to understand the angles on Threads federation in a more rigorous way, so I took a few days to think through and write up my sense of the benefits, risks, and available risk mitigations, along with loopholes that need closing and questions to discuss with fediverse administrators. This is a blisteringly hot subject for me, so it's hard to keep my head cool enough to understand other people's trade-offs, but I'm trying. https://erinkissane.com/untangling-threads

@mike Great points Mike. Thank you.

Can we expect a public outline of expectations for Meta and its executives in the same vein?

Something published that identifies what tactics are or are not acceptable, with clear mechanisms to hold Meta accountable if it does not meet those standards?

@fromjason I don't know. But maybe I'll go and ask them.

@mike Only if you think it's an important question to ask. I'm limited to the info on my feed so I trust your judgment. Thanks for replying.

@fromjason @mike

Meta is untrustworthy and has been since they taped their first dollar to the wall. You can bet your life you will need your accountability measures drawn up.

@mike Food for thought, appreciate the post Mike.

I hope I’m not splitting hairs, but what’s your definition of “win” here? It reads to me like you see it as a zero-sum game. Open survives, closed dies, or vice-versa.

Does it all need to be a competition? Surely the fact that both exist proves the pool that both swim in is open already?

Isn’t the availability of an open option the win already?

@vmatt well, you raise a good question. For purposes of this post Win=most people around the world do social media via an open standard like ActivityPub from whatever app, whatever provider, with whatever group of people, using whatever algorithms with whatever compensation model they prefer.

Lose=the big social media companies continue to own and run and lock in the majority of people on the planet.

@mike @vmatt

Open can win, but it's a narrow scrape. Consider the case of how and why IBM saw the wisdom of porting Linux to its hardware.

Nobody reading this needs to be told about openness or flexibility or reducing costs - Linux had a Benevolent Dictator to keep the whole contraption chugging down the tracks.

ActivityPub's leadership will require strategic leadership. It's done extremely well with collaboration and consensus, but may want to empower its governance... I don't know.

@mike I like you

I literally just got here.

Via 'Tusky' on my entry level (what I can afford) smart phone.

You are the top & therefore first post of my feed.

I only just read about 'Flipboard' yesterday or Wednesday (it's still Thursday for me as far as I'm concerned) "going fediverse" & barely understood whatever 'Flipboard' is.

But by your second bullet point & mention of 'AOL' I knew exactly what you were saying.

And agree.

Let's stay open.

Doing my part.

CHADMicDUP🎙️

@mike

Open will win for me. Closed is for the uninformed.

Too bad, but this has been the case forever.

@mike This is an excellent thread. 100% relevant to the circumstances the fediverse finds itself in today.

The "if we build it, they will come" mentality is a losing strategy. Open has amazing advantages in speed & agility that closed usually does not & this can be harnessed to accelerate innovation & potential value.

Meanwhile, hyping foundational underpinnings that have nebulous value to avg customers like 'ActivityPub', "decentralization', 'BYO Instances' are a fast way to irrelevance.

@mike ActivityPub is already open - that cat is out of the bag 🐈

After that, people will open and close all the doors and windows they want on their own systems, as they see fit. At the user level, group level, site level, network level.

Technology should serve people, not the other way around. Home taping didn't kill music and home defederation hasn't killed ActivityPub.

I'll be happy for the ActivityPub folks if it takes off.

I will not be jumping on any grenades to make that happen.

@mike You haven't actually said a word about defederation etc of course, these are just the things I think of in the context of your comments.

I didn't join Fedi to win anything.

I joined it to be on a community-owned social media site without recommendation and tracking engines, and where bigots get the boot good and quick.

Anything else is a nice to have from my perspective.

To some extent those desires, and the ones relating to openness, introduce a dramatic tension to Fedi 🎭

@mike which is why, of course, we're all using closed proprietary distributed hypertext systems over closed proprietary networks to access...

Oh wait, we're not.