@julian It's interesting how different platforms implement things. Some platforms, like Friendica, tell you which platform someone is using by showing a little icon next to their name on all of their posts (Mastodon icon, Hubzilla icon, potentially a NodeBB icon, etc.), whereas Mastodon makes it appear as if everyone is on Mastodon. Some Mastodon users are not even aware that they are talking to people on other platforms.

The reason why I say indicating that it is a forum or group discussion is useful is not just the cultural issue, but also because replies to forum posts are distributed differently than a normal post. You are not just replying to your followers and the person who posted, but also to everyone following the forum (or forum category).

But, this is something that is nice to have, and not needed. It just is useful information to have. And I doubt that platforms like Mastodon will make such a change anyway.

It's also interesting to see how platforms that pre-date Mastodon implement things versus platforms that came later and are influenced by Mastodon.

@scott@loves.tech I think it's a neat thing to show the software icon next to a post.

... but at the same time, think about who you want to use your software. Software geeks? Totally on board with that.

... but everyday people won't know what they're even looking at, and this (among other items people constantly bring up re: explaining ActivityPub) is all stuff that should be abstracted away from the end user.

It's not a matter of "before Mastodon" and "after Mastodon", at all.

@julian

It's not a matter of "before Mastodon" and "after Mastodon", at all.

I was trying not to state this so bluntly, but basically, platforms that came before Mastodon has blockquotes before Mastodon existed. We did not get rid of them in 2016, and we aren't getting rid of them now.

So, even if you implement this proposed feature, which is your right, some platforms will stay with the tried and true blockquotes.

@julian By the way, edits don't appear to be appearing on NodeBB. I fixed a typo, but NodeBB still displays it.

@julian Or, to put it more diplomatically and to give a little context, this argument over blockquotes has been going on for about 8 years now. I don't think everyone is going to be on board with a single solution.

@scott@loves.tech at it's core quote posts and block quotes are separate constructs. I have no plans to disallow users from making block quotes (not to mention there's no way I can even do that).

@julian I don't think that will matter. People who want a quote that cannot be deleted with figure that out and will pick the method that makes the quote undeletable. It seems like a lot of work for something that people will simply bypass.

@julian To be fair, platforms that don't have quote posts might be interested in this, since they can offer quote posts without the risk.

@julian You're right, the choice of software shouldn't matter. Our goal is seamless interoperability.

@trwnh @thisismissem @mro @jupiter_rowland @renchap @scott @AltCode @leroy @Kichae @scott

@silverpill @julian

that's a bit simplistic imo. software doesn't matter, sure; what matters is what the software lets you *do*. but "interoperability" is not a goal in itself. it's a means to an end. for different software that let you do fundamentally different things in fundamentally different worldviews, there can be no meaningful interoperability.

example: fedi has concepts and abstractions for "posts" and "profiles". what happens when you don't have these same building blocks?

@silverpill @julian i posit a different goal, at least for myself: empowering people with effective tools by which they can express themselves.

i'm posting this from mastodon right now, but i could just as well be posting this locally from within nodeBB. the federation is irrelevant, and in some cases, the federation is actually a burden. it creates the seams in UX. federation is a boundary that information crosses. the goal of a discussion form is to get information across various interfaces.

@silverpill @julian reframing it in terms of information and interfaces, of data stores and transports, we find that there are multiple ways to participate in a centralized conversation:

- by web app + sign in (local or federated credentials)
- by HTTP POST to an endpoint (plus additional protocols on top)
- by emailing a certain address, if you wanted
- in theory you could physically send a letter to some building, if that was agreed upon beforehand, to manually enter it into the database...

@silverpill @julian so the exact protocol and its finer details are less important than what you can *do* with that. the goal is to make information reach your destination with minimal information loss.

in that sense, whatever subset of whatever fedi-adjacent protocol you adhere to is only useful insofar as it allows ingesting information without missing anything important.

and when it comes to publishing information (a separate concern from discussing!), you again likewise have interfaces...

@silverpill @julian

the primary publishing interface we have is the Web. that should be the primary focus, not "publishing to the fediverse". the fediverse shouldn't be the end-all-be-all. we shouldn't be poorly reinventing the Web from first principles.

in a similar vein, the "network" is made up not of fedi nodes, but of mutually intelligible interfaces for information. instead of negotiating an exchange of content, it is just as valid if not moreso to negotiate an exchange of *identity*.

@silverpill @julian given this framing, it is incredibly limiting to say "the network consists solely of URIs hosting JSON documents which contain an inbox and an RSA publicKey which is used to generate a Cavage draft 8 Signature on an AS2 Activity payload of a certain shape which is then delivered to another inbox via HTTP POST with a certain Content-Type, after which the activity will be unwrapped and discarded... no exceptions to any of this" (etc)

because maybe there's better ways.

@silverpill @julian

can the network not consist of all manner of agents whose identities can be established by all manner of methods? in the same way TLS negotiates an encryption suite, a generic "TLI" can be used to negotiate an identity proof without relying on TLS client certificates.

can the application layer not similarly negotiate a semantic profile for which data models, serializations, etc are supported, and what will be done with thr payload?

@silverpill @julian because at the end of the day, it all boils down to agents passing around resources. or if you take an RDF view, resources communicating with other resources.

the question is in how we allow that to happen. on which terms. within which semantic framework.

the protocol is once again irrelevant, beyond its function of passing the message from A to B. it's what B does with A's message that matters. it's the set of every possible message A could send... regardless of transport.

@trwnh @julian Almost all social networks have profiles and posts.
If application is doing something completely different, then we don't need to interoperate. But within a federated social network interoperability is the goal because otherwise user experience is going to be poor.

@silverpill @trwnh @julian@community.nodebb.org Remember that one AI-based social network that said that they would never have follow relationships? Trying to imagine how to make that work with federation was a bit of a brain teaser. Their attempt at Mastodon interoperability fell apart for much simpler and much worse reasons though, so that experiment quickly turned into a nonstarter.

@julian@fietkau.social @silverpill @julian@community.nodebb.org i think the real question is what kind of world are we building here -- one limited to being a "social network"? that's so constrained. i don't want to live in that world. i don't want to "post" to "followers". i want to publish on my website and maybe syndicate to other websites of my explicit choosing. i want to be able to participate in discussions on various forums without having to make a new set of credentials for each one. neither of these require federation...