Posted on

Customization options removed in favor of one commercial default

Old Reddit communities could look ridiculous.

That was partly the point.

Subreddit moderators could use custom CSS to change colors, layouts, headers, sidebars, labels and sometimes nearly the entire visual identity of a community. A subreddit could look nothing like the one next door.

When Reddit began preparing its major redesign, that freedom became a product problem.

CSS was powerful because it could break things

In 2017, Reddit told moderators it planned to deprecate CSS in the redesign and replace it with structured customization tools.

The company’s explanation was specific. CSS only affected the desktop web experience, was difficult to learn, could create confusing changes, and made Reddit’s own interface development harder because platform updates risked breaking custom styles.

The web redesign, CSS, and mod tools
byu/spez inmodnews

Those are legitimate maintenance problems.

Arbitrary CSS gives community operators a lot of power precisely because the platform cannot completely predict what they will do with it.

Reddit’s replacement offered controlled options for community appearance that could work consistently across redesigned desktop and mobile interfaces.

https://redditinc.com/news/an-update-on-reddits-redesign

A theme editor is not the same thing as a stylesheet

The redesigned Reddit added options for banners, colors, icons, menus and widgets. That covers the common cases and is much easier for nontechnical moderators.

What it does not provide is arbitrary control over the page.

Old Reddit CSS could be clever, ugly, funny, inaccessible, brilliant or completely broken. It could also implement little interface tricks the official product never anticipated.

The structured system narrows that space. A community gets choices from the platform’s menu instead of control over the underlying presentation layer.

That gives Reddit a more predictable product across devices. It also makes communities look more like variations of Reddit rather than separately designed places that happen to live on Reddit.

Standardization has a real cost

A consistent interface is easier to support, easier to update and easier for new users to understand. It also gives the platform stronger control over where navigation, promoted material and new product features appear.

That does not prove advertising was the reason Reddit moved away from CSS. Reddit’s own stated reasons centered on mobile compatibility, complexity and development speed.

The loss is still measurable.

Users went from a system where skilled community operators could rewrite much of the visual experience to one where customization happens inside boundaries defined by Reddit.

The newer system is cleaner.

It is also less weird.

On the old web, those two qualities were often enemies.

Posted on

Interoperability promises weakened after adoption

Google Talk did something that now feels almost exotic: it let people on other compatible messaging systems talk directly to Google users.

The service used XMPP, an open messaging standard. Google’s own developer documentation described Google Talk as fully interoperable with other services supporting server-to-server XMPP federation.

https://support.google.com/code/answer/56278

That meant the network boundary was softer than the company boundary.

Federation did not require Google’s permission

Google’s documentation said outside service providers did not need special approval to federate with Google Talk. If their servers supported the XMPP standard, their users could communicate with Google Talk users and vice versa.

https://support.google.com/code/answer/55704

Another Google help page listed Earthlink, Gizmo Project, universities, corporations and individual XMPP servers among the kinds of systems that could participate.

https://support.google.com/code/answer/55703

That is genuine interoperability. A person could choose a different provider or client without necessarily abandoning everyone on Google Talk.

Then the product direction changed.

Hangouts replaced Talk without XMPP federation

In May 2013, Google announced Hangouts as the replacement for Google Talk. Google’s old developer documentation now carries the same blunt notice on multiple pages:

Hangouts does not support XMPP.

https://support.google.com/code/answer/55693

The messaging service still worked. Google users could still talk to Google users. What disappeared was the open bridge that had allowed independently operated XMPP systems to participate in the same conversation network.

That is a different kind of product change from removing a button.

A button can be relearned.

A protocol boundary decides who can connect at all.

Adoption makes lost interoperability expensive

Once enough contacts, organizations and conversations accumulate inside one provider, losing federation creates a practical choice for outside users: move closer to the dominant service or accept reduced reach.

Google had legitimate product reasons to build Hangouts differently. Messaging had expanded beyond simple text and presence into richer media, mobile synchronization and tightly integrated Google services. Open standards can also constrain how quickly proprietary features evolve.

But that tradeoff belongs in the record.

The original system advertised openness as a feature. The replacement system kept the audience while dropping the protocol that made cross-provider communication possible.

Interoperability is most valuable before a platform wins.

It is also easiest to remove after everyone has already arrived.