Killed by Google
Synapse
Our great sponsors
Killed by Google | Synapse | |
---|---|---|
2,301 | 367 | |
2,345 | 11,720 | |
- | - | |
6.9 | 9.8 | |
6 days ago | 4 months ago | |
TypeScript | Python | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Killed by Google
- With Vids, Google thinks it has the next big productivity tool for work
-
Google Axion Processors, our new Arm-based CPUs
https://killedbygoogle.com/
Their reputation is deserved. Google domains was killed only last year!
-
Google's Decision to Effectively Kill-off Small Sites
And this isn't even the first time I've been burned by Google's decisions. If you're familiar at all with the Google Graveyard, you'll know that Google has a long history of killing off products and services that people have come to rely on. This has happened to me a number of times, in both a personal and professional capacity, and frankly it's getting old.
- Google Scholar PDF Reader
-
Calls grow for Sundar Pichai to step down from Google CEO position
Just because Google has a couple of decent services that you're willing to pay for doesn't detract from the fact that most of their products have a worse life expectancy than a victorian child in the 1800s. https://killedbygoogle.com
They ruined every single opportunity to be more than an advertising company since Orkut. With scrapped attempts, starts and lack of intention for most of the 2010s to even during the early half of the Pixel Era, they seemingly haven't learnt to stick to something and iterate on it well.
And the fact that over 50% of their revenues come from search and by extension, advertising.
The fact' that til this day, they still haven't evolved from the "throwing shit at the wall then at the fan" strat which explains how they have fumbled so much so quickly.
- Google's Gemini Headaches Spur $90B Selloff
-
Our Company Is Doing So Well That You're All Fired
Yeah. The Google Graveyard really shows how far this can go.
https://killedbygoogle.com
The punchline is that in addition to hundreds of failed hobby projects, their stock is doing great. Monopoly power is a helluva drug.
-
Gemini Ultra now available in Google Bard
To me Gemini is just sort of generic and uninteresting. There has to be hundreds or thousands of products and companies based on the name "Gemini" - "Bard" was at least interesting, different and distinct.
I've no idea about the quality of the product itself, I have never had a reason to use it. It's long past cliché now but I wouldn't get too attached to a Google product that is definitely costing a lot of money but which has no clear pathway to turning a profit. I think they will keep it ticking over until the hype train moves on from Chatbots/LLMs, and then it'll join the Google Graveyard @ https://killedbygoogle.com
-
Gemini Ultra Released
We're not talking about reliability, we're talking about Google's penchant for killing established products that people use. https://killedbygoogle.com
-
Google Promises Unlimited Storage; Cancels; Tells Journalist Life's Work Deleted
The website you're referring to: https://killedbygoogle.com/
Synapse
-
Organizing OpenStreetMap Mapping Parties
What are you thinking of here? Synapse has supported purging room history since 2016: https://github.com/matrix-org/synapse/pull/911, and configurable data retention since 2019: https://github.com/matrix-org/synapse/pull/5815.
Meanwhile, Matrix has never needed the full room history to be synchronised - when a server joins a room, it typically only grabs the last 20 messages. (It does needs to grab all the key-value state about the room, although these days that happens gradually in the background).
If you're wondering why Matrix implementations are often greedy on disk space, it's because they typically cache the key-value state aggressively (storing a snapshot of it for the room on a regular basis). However, that's just an implementation quirk; folks could absolutely come up with fancier datastructures to store it more efficiently; it's just not got to the top of anyone's todo list yet - things like performance and UX are considered much more important than disk usage right now.
-
GrapheneOS is moving off Matrix
some context re the Matrix isses, long history apparently: https://github.com/matrix-org/synapse/issues/14481#issuecomm...
-
Non-profit Matrix.org Foundation seems to be moving funds to for-profit Element
Why not Matrix? Here's one reason: it has incredibly hard-to-debug edge cases, and plenty of bugs. One of my favourites is the one where people are kicked out of your room at random, which was reported a year ago[0]. It wasn't fixed, however, because the head of the Matrix foundation (Matthew) presumably didn't like the issue being posted on Twitter.
This is honestly really disappointing behaviour from a platform owner.
[0]: https://github.com/matrix-org/synapse/issues/14481
-
The Future of Synapse and Dendrite
> That doesn't make this situation any less bad to the rest of the community.
How is the community suffering here? Let's say Element adds a bunch of baller stuff to their versions over the next few months and then closes the source. Can't the community just fork the last AGPL version? You might say, "well then no one can take the AGPL fork and make their own closed-source business", but do you want them to? Even if you do, they still can with the existing Apache-licensed version, just like Element is doing right now.
You're arguing that Element will lose a lot of contributions, but TFA points out that despite being super open, the vast majority of contributions are still made by Element employees (which seems to be true [0]). It's not the case that Element is looking to monetize the (small) contributions of others, it is the case that others are looking to monetize the (huge) contributions of Element.
And besides, aren't the MSCs the core of Matrix? It's already super possible to build your own compliant client and server.
The situation is that Element needs money to keep developing the ecosystem. It would be cool if there were a big network of donors and contributions, but there isn't. You're essentially saying, "that's fine, go out of business then, and the community will keep developing the ecosystem", but that's not happening now, and it can still happen anyway with the Apache-licensed versions, which again people can still contribute to.
[0]: https://github.com/matrix-org/synapse/graphs/contributors
- Synapse v1.95.0 Released
- Matrix Synapse how use python scripts?
- Synapse v1.91.2 Released
- Synapse v1.89.0 is out
- Synapse v1.88.0 is out
- Synapse v1.87.0 (Matrix Server) Released
What are some alternatives?
Materialize - Materialize, a CSS Framework based on Material Design
dendrite - Dendrite is a second-generation Matrix homeserver written in Go!
babel-plugin-superjson-next - Automatically transform your Next.js Pages to use SuperJSON
conduit
Ryujinx-Games-List - List of games & demos tested on Ryujinx
Rocket.Chat - The communications platform that puts data protection first.
tModLoader - A mod to make and play Terraria mods. Supports Terraria 1.4 (and earlier) installations
Jitsi Meet - Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.
BetterJoy - Allows the Nintendo Switch Pro Controller, Joycons and SNES controller to be used with CEMU, Citra, Dolphin, Yuzu and as generic XInput
Mattermost - Mattermost is an open source platform for secure collaboration across the entire software development lifecycle..
kotlin - The Kotlin Programming Language.
matrix-docker-ansible-deploy - 🐳 Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker