9 ms·
RFC 9518 – What can internet standards do about centralisation?
- shadowgovt 3y agoPeople centralize because centralization solves real problems they have. If we want decentralization, we have to build alternatives as convenient and simple as the centralized ones, and that's a hard project.
- imiric 3y agoRight. This is a convenience problem because the web has no analogue to the browser for publishing content. If publishing content would be as convenient and simple as consuming it, there would be no need for users to flock to publishing services. Most of the centralized services today simplify publishing. Any "community" that forms around them is entirely incidental, and in the case of global social media, mostly harmful. I think this is a problem the early web should've solved[1]. Now that the centralized model is dominant, most people wouldn't see a reason to change their habits, even if a new solution would be easier and simpler, and not just better on a technical or privacy level (which most people don't care about anyway). [1]: https://news.ycombinator.com/item?id=38659814 https://news.ycombinator.com/item?id=38659814
- quickthrower2 3y agoI don’t know. Stick everyones data in a single DB and have private business logic can do anything decentralised protocols can do but not vice versa. At least in respect to building the addictive attention seeking experiences that are needed for “success”. Decentralized has one advantage though. You choose your user agent. For example your browser, your bitcoin client, your email client and so on.
- mike_hearn 3y agoNetscape 4 came with Composer, Windows/Office used to come with FrontPage. People had content creation tools integrated with their browsers, but didn't use them and so they went away. I think it's because the tools were too un-opinionated and unconstrained, so if you wanted to do e.g. a blog then generic HTML editors were too much work even though they were visual. Also, static content publishing is almost never enough. You at least want(ed) search and to understand if anyone is visiting, but then you're into the realm of needing databases and such.
- imiric 3y ago> Netscape 4 came with Composer, Windows/Office used to come with FrontPage. Those are WYSIWYG tools only, which besides being a nightmare to work with, don't solve the actual serving problem. The earliest product that came close to that use case AFAIK was Opera's Unite in 2009, but it didn't last long. By that point it was already too late, since users mostly had asymmetric connections, so serving any type of content from their home network was infeasible. (Had the web launched with easy publishing tools, ISPs would've been forced to offer symmetric connections from the start, and this wouldn't have been a major issue.) > Also, static content publishing is almost never enough. True, but there's no reason these tools couldn't have evolved to allow dynamic content as well. Nowadays we have many different approaches that could make this possible, cobbled together from bits and pieces of native and alternative web technologies. Centralized services do make this easier, and who knows, we might've settled on them anyway, but I believe the general perception about user data would've been much different for the better had these tools existed from the start.
- mike_hearn 3y agoI don't think there was ever much chance of people running servers from home, if only because back then computers were noisy and power management didn't work well, so it was normal to turn them off at night. But most ISPs offered some web serving space via ftp so that wasn't an issue. It was more just that the tools were too much work. Obviously they were still a lot easier than coding it all by hand!
- idle_zealot 3y ago>as convenient and simple as the centralized ones I don't think that's sufficient. Take Mastodon for instance. The user count surged recently, demonstrating that it's not actually difficult to adopt or use as a Twitter alternative. But people tend to prefer algorithmically-driven social media that's optimized not to give them agency, but to be maximally attention-grabbing and sticky. The centralized and profit-motivated product is worse in the sense that it wastes more of the user's time and makes seeing the things they've explicitly followed more difficult, but that particular kind of "worse" by design is more popular. I don't really have a solution to propose here, just want to point out that sometimes the worse option wins by virtue of being worse, so being "as convenient and simple", or even being better is not always enough to attract people.
- quickthrower2 3y agoIt took some really bad stewardship of Twitter to cause those surges!
- myaccountonhn 3y agoPeople also adopted email without fail.
- j4yav 3y agoThings used to be decentralized well when I think back to the early days of the internet. When I think about why, its because links were expensive or unreliable - what centralization brought was a kind of predictability and ease of use. The challenge for new decentralized systems to address I think is to offer a similar level of convenience as the centralized systems. Just being decentralized doesn't seem enough.
- dijit 3y agoGranted I've not lived long enough to have witnessed the birth of the internet with adult eyes; what I have personally observed is a constant battle of centralisation and standards forming. For a common example that many people may remember, AOL was at one point pushing towards a centralised model and was succeeding- until they completely collapsed and the open web resumed being a thing. Similar for the times where there were no standards on video playback on the web, a bunch of companies competed with completely incompatible systems that had various pains associated until eventually standards emerged that sunk the majority of it. (ironically one of them with a healthy helping from Apple). The web was never really decentralised - it's a fond memory and a legend we tell ourselves, this battle seems to been waged from almost immediately after it was conceived. I found a much more articulate article on the matter while I was writing: https://archive.is/UUgl7 https://archive.is/UUgl7
- j4yav 3y agoI was there, AOL was certainly not the internet. It's an interesting article but it seems to cherry pick a bit. AOL was like a huge BBS that gave its users a limited portal into the internet, and only on a very limited basis starting in 1993. They never really had proper access as far as I know, and for those of us not accessing through AOL things worked perfectly fine and I never accessed anything through or hosted by AOL. I'm not really sure how to convince you in the end, but it's funny now hearing my own experience was only a legend. I feel like I've achieved something and need a plaque indicating I've successfully moved into some new life phase.
- 3y ago
- marginalia_nu 3y agoI'd put a lot of fault with the internet search and discovery mechanisms, that almost all favor popularity based mechanisms. This works well in a vacuum, but as they start to direct traffic, they feed into themselves to increase the popularity of whats popular, and obscurity of what's obscure; and inevitably create an extreme Pareto distribution where the Internet seems to consist of only a handful of different services.
- spiritplumber 3y agoThe easy fix would be to do something familiar to genetic algorithms - fish out things that are unpopular at random and give them 10% of results. On facebook or the like, do that for things that people DON'T want to see (conservative content for a progressive, for example). This doesn't require a substantive change to the existing algorithms, so it shouldn't break (many) things.
- spacebanana7 3y agoCouldn’t that upset users? Leading them to other platforms or installing ad blocker like solutions to avoid unwanted content.
- spiritplumber 3y agoYes, but it'd also make results more meaningful AND maybe reduce the opaqueness of bubbles. I'm guessing it would be a balancing act.
- quickthrower2 3y agoAll this is shadowed by the SEO industry. What small sites have in their favour is the long tail of new keywords. In tech there are a lot of them. I had a blog that came up in a colleagues search results, I checked and I was place 20 for a decent keyword. I don’t so SEO so there is hope for the little guy!
- thfuran 3y ago>fish out things that are unpopular at random and give them 10% of results. On facebook or the like, do that for things that people DON'T want to see (conservative content for a progressive, for example). I don't think that's nearly as easy a fix as you suggest. Sure, some political views may have reasonable opposing views, but the other side of the story when trying to look up the history of the measurement of the diameter of the earth is probably flat earth garbage.
- hobofan 3y agoStandards bodies like IETF and the W3C also play a crucial roles and are in some aspects the worst offenders when it comes to promoting centralization via standards. So seeing an RFC that's the product of multiple layers of centralization talk about that topic seems very ironic. They do address this in the RFC, but only briefly and I don't think to a sufficient enough extent. If you want to get rid of centralisation one of the most effective things to do is ignoring standards bodies. Of course that may be detrimental to end-users in other ways (e.g. non-iteroperability).
- robertlagrant 3y agoIsn't interoperability how we get decentralisation?
- zaik 3y agoIf you want to communicate, you just have to agree on some protocol for communication. That's why we need standards and standards bodies. Having to agree on a protocol level is much better than everyone having to agree on a single entity who provides the apps and runs the servers.
- danbruc 3y agoNobody cares about [de]centralization, for more than 99 % of all internet users it does not matter whether the internet is the internet or a single server sitting in someone's basement. They want to use services - chat, write mails, watch videos, have a website, buy stuff, sell stuff - not run infrastructure of any kind. So nobody is going to have their own servers, they will all use existing services. And because it is easy to switch, everyone will be using the best - for some definition of best, could be easy to use, cheap, functional, ... - service and everyone else will go out of business. That also makes the internet simpler, there is one place for one kind of service and everyone else will also be there. And this does not only apply to end-users, the move of IT into the cloud is fundamentally the same thing, nobody wants to run the infrastructure. You can maybe argue that everyone has their preferences wrong and they are hurting themselves in the long run, but good luck fighting that battle.
- linuxandrew 3y agoI do agree that 99% of users don't want to run infrastructure. I think there's a difference between Fediverse-style federation/decentralisation and true P2P/BitTorrent-esque dectralisation. BitTorrent, in its current iteration, does have many semi-technical users, but perhaps your grandparents would struggle to use it. I think a much more friendly UX could be built; maintaining its decentralised properties would be more difficult but not inconceivably so. I actually think transparent decentralisation is possible but the current policy settings (copyright, surveillance and advertising) somewhat disincentivise people from working on it, to the extent that most of the current projects are hobbies, crowdsourced or funded by research grants.
- the8472 3y agoThey don't care when it works. Then they get locked out of their google account and lose a lot of things at once and only have few alternatives to choose from and may return google yet again due to lack of choice. > You can maybe argue that everyone has their preferences wrong and they are hurting themselves in the long run, but good luck fighting that battle. That battle has been won many times. We don't let people run blind into open knives in many contexts.
- fidotron 3y agoThe big problem is people have been trained to think that centralized authority is a necessary precondition for security. Just look at the state of browsers gating access to APIs for sites on local sub networks. We have created a two tier WWW. But the security concerns are not without basis, yet doing things like coming up with a secure replacement for mdns is not exactly aligned with the interest of organizations that want all information to go via the cloud, and they will fight it tooth and nail. As tech people we really should put our money where our mouths are on this and stop using github, and in doing so fix the pain points.
- robertlagrant 3y ago> The big problem is people have been trained to think that centralized authority is a necessary precondition for security. Just look at the state of browsers gating access to APIs for sites on local sub networks. We have created a two tier WWW. Most people wouldn't in any way think like or even about this. Which people do you mean?
- Geisterde 3y agoEvery single person that thoughtlessly backs up their data to cloud storage, so basically everyone outside of a few weirdos like us.
- maccard 3y ago> Just look at the state of browsers gating access to APIs for sites on local sub networks. Given we're on HN I think it's fair to nitpick a bit - what do you mean here? What API are you accessing through a browser? If it's a control panel or something through an API, you can install a cert into the browser, or get a wildcard cert signed for a local domain.
- quickthrower2 3y agoGithub for work is so productive though! At home yeah just use git and have a backup and you are done.
- 3y ago
- mike_hearn 3y agoI worked on Bitcoin in the early days, and developed decentralized software and protocols as part of that. I also did most of the design on an "enterprise blockchain" system later which is basically (in my view) a peer to peer database run by competing 'frenemy' businesses, i.e. with mostly untrusted nodes. So I feel like I have a lot of practical experience in this domain. The RFC is decent enough. It's moderate and reasonable, and cites Marlinspike's "ecosystem is moving" essay which is a very important piece of thinking in this space. I'm not a fan of the RFC's friendliness towards regulation. Governments often achieve the opposite of what they want when they try to regulate the internet, and they don't care about centralization at all or in fact prefer it because it makes it easier to engage in control when there are only a few big players vs thousands of smaller players (see how modern EU regulation is explicitly targeted only at "very large platforms" and ignores the rest). But the RFC lacks specific suggestions. For engineers who want concrete and achievable ideas that can be worked on with minimal cost, here are a few I'd pick: 1. Support IPv6. Getting flat end-to-end routing working again is one of the lowest lift ways to improve decentralization on the modern internet, in both obvious ways (reducing CGNAT) and less obvious ways, for example it's conceivable that Android could be extended to support socket activation. That would allow apps to bypass push notification and centralized reflectors in some cases. I'm not sure how commercially strategic push services are to Apple and Google these days - it costs a lot of money and it was revealed recently that governments are wiretapping supposedly e2e encrypted messengers by grabbing the push messages. So whilst I doubt Apple would allow it, in theory someone could write a patch for Android to enable it and contribute it upstream. 2. Support confidential computing. A lot of centralization happens because we need a program to be run on a server somewhere to do something sensitive, which means we need to trust the server operators (cloud+admins). So we gravitate towards big brands that everyone can agree on, like AWS. Confidential computing lets client apps (phones, desktop apps, less easily also web apps) to verify the server they're connecting to is untampered with and running the expected software. It takes cloud and root out of the trust equation, meaning you can in theory do things like have a P2P network of anonymous operators who offer their services without needing horrifically complicated and ad-hoc app specific cryptography. The tech works today, but very few people are aware of it or use it, and it's not integrated well into our tech stacks. But it should be! 3. Write smartphone, tablet and desktop apps. Web apps are inherently very centralized. The name of the app is conflated with its hosting location, browsers practically force you to delegate most of the app's work to the server, and user data ends up tightly bound with the operator and implementation. You can't even do tricks like confidential compute with them really, because browsers don't understand the remote attestation protocols. If you write client-side apps you can dodge all those problems and loosen the bindings between user data location, software distribution location and compute location. Still, you have to be realistic. After some years I realized that centralization happens because decentralization is in some sense like communism. If you take away ownership over private property then people lose the incentive to improve it. It becomes a commons and the usual tragedy follows. Centralized services are private property, and so the owners make sure they are well kept and improved. Also private property and profit is mentally grounding - projects that lack these things have a habit of going crazy and losing interest in what users actually want. These days I'm not quite so interested in pure open source p2p systems anymore because of that problem, but there's a lot of scope to find interesting corners where private property can be combined with more decentralized implementations. After all, Office 2000 was owned by Microsoft yet still much more decentralized in practice than Office 365.
- ThinkBeat 3y agoIRC, UCCP, NNTP Are in various ways all distributed SMTP, HTTP, FTP, Telnet, SSH, SFTP,Finger Are all relatively easy to self-host. and it used to be frequently done. We have plenty of protocols to use already, and we have had them for a long time, that is not the problem.
- california-og 3y agoCan you explain or give advice on how one would self-host? In my country none of the main ISPs offer static IPs. They're only available to businesses. Self-hosting with a dynamic IP seems difficult if not impossible. There are some dynamic DNS services but that kinda defeats the self-hosted part.
- tenebrisalietum 3y ago> Self-hosting with a dynamic IP seems difficult if not impossible You just need something on your network that monitors your IP and updates your DNS when your home IP changes. "Dynamic DNS Update Client" yields results in Google that will be a good start to understanding. > There are some dynamic DNS services but that kinda defeats the self-hosted part. No, selfhosting at home doesn't mean you have to host a public DNS server. You will definitely need some external DNS pointing to your home network. There are multiple free providers.
- _factor 3y agoYou will still need a static IP for SMTP. Dynamic IP assignment and NAT traversal are the largest hurdles to self-hosting reliably. DNS updates are great, but then you're still relying on a large centralized DNS provider. You can host nameservers yourself, but then you're back to the Static IP issue.
- layer8 3y agoYou have to rely on a registrar for your domain name anyway. For everything else, a cheap VPS with a static IP is easy to manage and can delegate to your homeserver behind the scenes. The VPS also can be easily replaced by a different one when needed just by managing the DNS entries.
- jongjong 3y agoOne of the things that bugs me is the design of the current DNS system which is currently extremely centralized and under the control of a small number of organizations. It's ridiculous that nobody can truly own a domain name and instead, we're all just renting them and renewing them and have to keep forking over money. I really like the concept of Unlimited Domains which lets you buy and own domains forever but I'm wondering why browsers don't support them broadly as an alternative. Blockchains are optimized for high-availability and therefore, that makes them ideal for the DNS use case where you want lookups to be free. Also, it is acceptable for updates (e.g. ownership changes or changes to the 'zone file') to incur a cost that is proportional to the utilization of the network for that purpose; it would guarantee that each update action would incur the lowest price possible.
- teddyh 3y agoDNS isn’t centralized; it’s federated. I mean, just because there’s an ISO and a UN does not mean there is a single world government.
- jongjong 3y agoYes, but in practice the whole system would be broken if different countries had different records for the same domain. With blockchain, you can enforce consistency.
- xoa 3y agoI don't see it mentioned yet, but I think it's pretty important to address that centralization goes far, far lower to the most basic Layer 1: asymmetric (ie, centralization promoting) WAN links, stickiness of IPv4, secure trust foundation, maybe DNS or other equiv, and lack of IP auth or otherwise core level mitigations for DDOS. These are core foundations, and whatever the internet standards above it's much harder when the foundations are shakier. 1. To the first, for a solid stretch of decades, WAN links in much of the world that might otherwise have supported more decentralization have been tilted towards consuming from the center vs providing anything oneself, and of course just fundamentally stagnating as well at the impetus of powerful monopolies and regulatory capture. Until a few years ago I had the exact same 5/1 ADSL link I'd gotten in I think 2000 or 98/99. It was really something at the start, and I was able to run some fun stuff of it. 5, 10, 15 years later? Not so much. The US in particular put hundreds of billions into promises of big fiber networks, which then instead got used to just consolidate and profit. Cable and big telecoms are still fighting tooth and nail to prevent efforts like municipal fiber. But once you have symmetric 100/1000 or more, an extremely reliable, sudden a lot of new possibilities open back up again. Of course in those decades a lot of effort has naturally gone into centralized efforts because what would even be the point of designing for something without much potential user base because said users were stuck on crap connections either slow period or with decent download but utter garbage upload? So the ecosystem isn't where it might be on that front either, even though it's decent for more technical users. But I don't think we should forget just the most fundamental issue that if you want to serve bits in 2023 doing so at .5/1/2 Mbps with mediocre latency is pretty limiting. Lifting that isn't sufficient but it is necessary, even if the decades of mindset and ecosystem will lag. 2. To the second, I did at least get in early enough that I could still get, for free (as it should be), a static public globally routable IP address. That has also been a major boon even back when I was stuck sipping through a narrow straw. It's hard to internet if you can't do the inter part. Workarounds to coordinate via an IP elsewhere of course exist, but it's an extra layer vs "hey I can just talk directly home (or barn or office)!" IPv6, despite its flaws, should help bring that part back as well, but the flaws and slow adoption have also delayed things. 3. To the third, how to authenticate is a perennial problem of decentralization efforts. If we at least had universal, highly reliable fully trusted secure DNS, preferably with better registrar governance as well, then that would be a somewhat practical way to bootstrap something. I could put my own domain restricted root CA public cert in DNS, and everything could then just trust all certs issued by it for that domain only at a basic level and it'd all just work. Add a few cross signing options and an ecosystem for turn key CA management appliances into the mix and it's possible to envision something pretty approachable that would at least match and slightly exceed everything Let's Encrypt offers. That's another sandy foundation that really stings. 4. Finally, if everyone has decent pipes, and was running in a decentralized manner, there is of course the potential for more and even bigger DDOS. It would be helpful if there were standards for all the various tiers of operator from core straight back to residential ISP so that attacks could be automatically reported and followed right back out the stack to whatever WANs worldwide were involved and cutting them right there, or at interconnects for ISPs who wouldn't comply. Having to layer in providers like Cloudflare, however hard and nicely they work, has papered over it but remains suboptimal. Granted, this doesn't hurt dark/gray types of decentralization, where rather then decentralizing services or communications to the world one is doing it to other trusted networks exclusively. And that's definitely still very useful. I'm sure there's others, but at the very least continuing the fight for a really good physical layer seems pretty critical to me.
- throwawaaarrgh 3y agoFor one thing, stop cargo-culting? "Centralization" is a vague term that isn't inherently bad. Use specific terms, identify specific problems, and it'll be easier to find solutions for them.
- teddyh 3y agoMaybe, but what you propose sounds a bit like the US attitude that monopolies aren’t inherently bad, only everything it leads to.
- throwawaaarrgh 3y agoProposing specific terminology means monopolies are good ?
- teddyh 3y agoAsserting that centralization isn’t inherently bad is kind of like saying that monopolies aren’t inherently bad, yes.
- majewsky 3y ago> "Centralization" is a vague term that isn't inherently bad. Use specific terms, identify specific problems, and it'll be easier to find solutions for them. Thank you for reading the RFC and succinctly summarizing its main thrust.
- rcbdev 3y agoOne aspect of this that independent site admins often have to deal with is CSAM filtering. Many jurisdictions require it in some form but by definition you can't "roll your own" automated solution because how could you? Centralized solutions like PhotoDNA are not available to most people. With most other things I can see open source solutions prevailing, with this I can't. This will likely be the thing killing the decentralized Internet of ye olden days for good.
- goatmeal 3y agoit's prohibitively expensive to access these tools. I have to identify myself and pay over £1000 to be allowed to access them. the agency either doesn't care about independent sites catching CSAM or they don't want independent admins finding out that these tools aren't very effective. alex gleason the fediverse dev tried contacting them about this problem and they didn't care at all.
- moolcool 3y agoI wanted to set up a security camera to watch my pets when I was gone. The only requirements were that it had to have iPhone app, and I wanted the video to stream from my home network and not be funneled through a cloud provider. I couldn't find anything that did what I wanted, beyond a bunch DIY solutions which I did not have the time or energy to implement.
- djha-skin 3y agoIt is my opinion that there is one singular powerful force driving centralization: the need for moderation. I remember when CmdrTaco left slash dot. The place went to ruins almost immediately. If dang didn't do what he did or someone like him, we would all probably leave here as well. Joel Spolski managed to create a self-moderating site in stack overflow. Say what you will about the platform being toxic, and you're not wrong. Content from the uninitiated is not treated well, but on the other hand, The quality of the content is generally very high. People have a lot to say about this, but I will remind them that self-moderation like what stack overflow achieved is a monumental achievement! This is a really hard problem! In the early years of Mastodon the moderation wasn't so up to scratch as it is now. It has gotten so much better. It does give me hope that moderation can still be done on a decentralized platform. That said, it can't be denied that Mastodon is fighting in uphill battle precisely because it is decentralized when we speak of moderation. Once we start to have more mature tools around moderation in the face of decentralization, I think we'll start to see a groundswell of decentralized services finally coming out of the shadows. We see this starting to happen already.
- mike_hearn 3y agoSlashdot's moderation system didn't depend on CmdrTaco, that was famously the point of it. The userbase moderated itself. Slashdot never really made money and got kicked around between different companies a lot. There were some website redesigns that upset people and the visual design limited the number of stories that could be posted. Moderation can be done in a decentralized way. Email spam filters are an example of that.
- CM30 3y agoI guess it depends what you mean by decentralised here. For peer to peer networks, moderation is indeed difficult, since by definition no one singlehandedly controls what's shared there. On the other hand, federated services like Mastodon really work fine in the same way old school forums and personal sites did; the community decides what's acceptable, and content that goes against that gets blocked/removed. The real issue is that moderation doesn't scale; you can't easily automate it if you want it to work well, and hence both large centralised networks like Facebook and Twitter and large decentralised ones struggle to keep things under control.
- eterevsky 3y agoCentralization happens because it's easier and cheaper to implement services in a centralized fashion. Since users care more about features and price than about centralization, it seems pretty obvious that this problem can't be solved with standards, since standards are unenforceable.
- nradov 3y agoStandards can be enforced through government mandates. We've seen that in the US health IT space where CMS/ONC now mandate that payers, providers, and vendors implement certain HL7, X12, and DirectTrust open interoperability standards. Compliance is fairly high. But there are also drawbacks to government mandates in terms of slowing down the pace of innovation and raising compliance costs.
- eterevsky 3y agoThis is true, but the closest example of this happening that I can think of is mandating USB-C for phones. I don't think governments have ever regulated anything like internet protocols. Also the standard has to have wide adoption before governments would consider mandating it.
- zaik 3y agoUsers could also make interoperability a requirement and thus drive standardization. Nobody is interested in an email provider that cannot send emails to other providers. After WhatsApp changed its ToS in 2020 and I didn't want to agree to the new terms, I decided to delete all IM apps which depend on a single provider and only use a single one which is compliant with the XMPP internet standard. I also wouldn't sign up for any social network that isn't ActivityPub compliant anymore.
- eterevsky 3y agoFair enough, but unfortunately you are in a tiny minority.
- m3047 3y agoI give away technologies / products which favor / foster decentralization: * De-anonymize cloud services and make PTR records work again. * "Track the trackers" email aliasing; since none of the big providers do this well, you'll need to run your own Postfix mailserver to take advantage of it. Maybe you should set up DANE while you're at it? * A decentralized telemetry / SIEM -like platform using the DNS. * "Internet in a box" on your laptop: a wifi access point which doesn't have broader internet connectivity and which takes over all DNS (as well as DHCP) and allows you to run apps on that hotspot that are only accessible via that hotspot. Beyond the utility for remote / mobile de facto geofenced applications, imagine a world where "routers" were nodes with multiple wifi radios and which joined multiple "boxes". If the three phases of consensus are kook / lone gunman, co-conspirators, movement, (...consensus) I'm past the kook phase and into conspiracy. Happy to get on a video call and give anyone an hour of help with any of the above. Things that the RFC (and frankly nobody, really) doesn't cover are that centralization is overwhelmingly good for "free", but this has two sides. What two sides do you think I'm going to point out? There are absolutely awesome proprietary offerings (distributed doesn't necessarily mean open source or free) for doing no-code responsive mobile development by an "army of one" or a savvy user, for 1000 users or less (designed for scenarios where a UI needs to be built for a single person or maybe a half dozen at the most). Centralization favors the Procrustean (I still like that word, thank you commenter for gifting it to me): if the user doesn't fit, kill it trying and if it dies another one will take its place. I'm not sure if I need to see Coca Cola ads intended for an Argentinian or Ukrainian audience. Just let that sink in. Saw a pro-centralization argument the other day that $grandma in a $third_world_country can't view her grandson's football league games without the wonders of centralization (conveniently conflated with not regulating those centralized entities' traffic across international borders)... but this chauvinistically fails to grasp that this requires an international data plan (oftentimes lacking on phones in third world countries) and that grandma has to register for some global nexus of surveillance capitalism that otherwise has little relevance to her life in order to do so.
- m3047 3y ago"But how can an 'international data plan' be a thing, since the whole point is that the Internet doesn't have borders?" (some rando I mumbled to about this) That's because nation states aren't the only gatekeepers. Those centralized services are also gatekeepers. Not only the services, the people who put the brick in your hands. A lot of free or low cost phones in places where people don't have much income are essentially tethered to some AOL-like service, like Facebook. Really, your internet connection is to (or optimized for) Facebook: it's e.g. a "Facebook phone". Anything that's not "Facebook" counts against your data plan.
- wmsmith 3y agoAsking a centralized body (IETF) to do something about centralization. Rules for thee but not for me?
- zaik 3y agoYou have to agree somewhere for communication. I'd rather agree on who publishes the internet protocols level than on the who runs the server level.