• 4 Posts
  • 9 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle



  • One of the points made quite astutely in the FT comments section mentioned that ofwat was also strongly responsible for this.

    Apparently the regulatory model is set up in the following way - in order to encourage investment in infrastructure, the calculated amount that customers are charged is based on a ratio of how much money is invested into infrastructure. Supposedly Thames Water and other water companies in England wanted to invest more in infrastructure, however ofwat did not allow it as they wanted to protect customers from price increases. Furthermore because of the silly shell game of holding companies that were set up to move the debt around, ofwat didn’t understand just how much debt was being racked up and didn’t make any moves to stop it.

    However what this all shows is that the regulatory model is absolutely broken. So not only is ofwat toothless in allowing a ridiculous corporate structure to be set up to obfuscate the silly financial leveraging going on, they are also operating on an entirely faulty premise.

    What it all shows is that trying to set up a functional privatised system for water companies that incentivises investment and works for citizens is extremely difficult, is prone to regulatory capture, is still under pressure from meddling ministers and ultimately costs more for customers and the government than servicing the government debt that would be used to pay for investment under a nationalised system.

    Just bloody nationalised it.










  • The two potential roads seem somewhat equivalent to me:

    1. Threads federation is blocked by the main Mastodon instances. A huge user base of non-techies starts using Threads and it dwarfs the rest of the fediverse acting as a singular centralised platform. The fediverse continues to be a techie/ideological anti-corporate community as it is now with a relatively small community in the grand scheme of things.
    2. Threads federated with some of the big Mastodon instances. Fediverse instances outside of Threads get a large amount of growth as people see the extra content available in this larger federated environment. Growth of Threads still outpaces all other fediverse instances combined. Meta then carries out some form of EEE tactics and some large chunk of the userbase of the non-Threads instances switch to Threads. The techie/anti-corporate community continues to use fediverse instances without any interaction with Threads.

    Both scenarios end in a large centralised platform run by Meta and a small community that want to avoid a corporate platform.

    I think it’s also wise to separate the effect of large corporate instances in the fediverse between effects on Mastodon (where users follow users) vs Lemmy/Kbin (where users follow communities). In the case of Mastodon, the effects of EEE tactics will be strong due to a more powerful network effect because it’s important that a particular person is on the same platform as you (i.e. this is a similar situation to XMPP and gchat). In contrast, you just need some people to participate in a Lemmy/Kbin community to make it worth joining, but it doesn’t matter exactly who, meaning that membership can be small and sparse but the community still has a meaningful existence (i.e like niche forums).