A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community’s icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
So hold on, is this an open source space, a protocol or “like email”? Which of the poor analogies people use to convey excitiement about AcitivityPub are supposed to apply here?
Because, you know, Google got into the Linux space, into email and into open source software and it seems those survived the experience.
Try to start up your own independent email server instead of going with one of the largest providers. You will never be able to message anyone on Gmail.
Very much not true. All I’ve really had to do was create an SPF entry in my DNS and setup DKIM. Once that was done, it was okay.
The guys I regularly exchange email with have had no issues getting mail from my server.
Yeah but these examples are all bigger than Google. The fediverse irrelevant in comparison. Additionally at least Linux doesn’t have such a strong network effect, since it’s not a social network. I mean I’m going to let myself be surprised. But I kinda doubt that anything good will come from it.
The Meta business side isn’t nice folks that try to do good in general.
It’s debatable whether email survived. But yes, I do believe this problem is being blown out of proportion, it was inevitable that large companies would get into ActivityPub.
Google is actually a great parallel here, because of what they did to XMPP (the federated chat protocol). They implemented it for hangouts/gchat. It was a good on-ramp that allowed people to talk across platforms. Then Google created a bunch of features that only worked internally and not with XMPP. Then they removed XMPP.
XMPP didn’t work on mobile. You had to have the app running to receive messages, and the battery wasn’t large enough to keep the CPU powered up all day.
IIRC Slack did something similar with IRC.
Somebody not being able to message me while I’m offline is a fantastic feature that I wish we still had. I miss that.
Not really. Google is responsible for the open source browser Chromium, which is the base for Google Chrome, Edge, Brave, Opera, Vivaldi, etc. They dominate the browser market, and they use their position to implement features outside the web standard. Their competitors (mainly Firefox) are not able to implement the non-standard features, driving them out of the market. Classic Embrace-Extend-Extinguish.
Technically, both Android and Chromebok are Linux-based. But Google has done everything possible so that they aren’t part of the “Linux space”, to the point that Android uses a fork of version 3.x of the Linux kernel (regular Linux is now at version 6.x).
Right. But you do notice how any of those scenarios fail to “extinguish” anything, right? I’m typing this on Firefox, which is still going strong and has negligible incompatibilities. Chromium didn’t eradicate the competition by embracing open source, it did so by succeeding with their commercial product. The ONE competitor it didn’t outright replace with its open source alternative is Firefox, in fact.
And in the other scenario Android simply forks and separates. Linux is clearly not threatened by Android or ChromeOS, and all of those remain viable, healthy alternatives to closed, paid competitors from Microsoft and Apple.
Can’t have your cake and eat it, too. Either the open source environment based on Firefox and Linux is thriving or it’s been dismantled by malicious adoption from commercial enterprises. Which is it?
Android is moving towards upstream linux, and chromeos is moving towards using wayland + the linux version of chromium
Pretty sure that was Apple, not Google. Google joined the WebKit party later. By the time Google forked WebKit the other rendering engines (used by the FireFox and old versions of IE) were pretty much gone.
Also, Now that Google has forked WebKit, we’re back to two competing engines. And at least on the websites I run our traffic is about 45% each (and 10% other). That’s actually more healthy than it used to be (95% IE).
Private companies embracing open source browsers fixed a broken platform, it didn’t embrace/extend/extinguish.
Yes, FireFox is struggling for marketshare. That happens sometimes. Personally I think their biggest problem is they have a legacy code base that dates back to Netscape. It’s got nothing to do with Google.