Baby Buddy VS Synapse

The templates seem to be in /app/babybuddy/core/templates/core (see this page: https://github.com/babybuddy/babybuddy/tree/master/core )

https://github.com/babybuddy/babybuddy [could probably be amended to use for anyone]

Something like babybuddy (https://github.com/babybuddy/babybuddy)?

I'm currently using it as an interface for Baby Buddy, which has a pretty great Home Assistant integration for tracking feedings, diaper changes, etc. for my newborn.

I set up a self hosted baby tracker app: (baby buddy)[https://github.com/babybuddy/babybuddy] it's our second baby so we have not been tracking any of the baby stats. I literally only use it to track my pumps.

I’m using Baby Buddy, I built some ESPHome devices to trigger on button presses (from what others have posted as modifications). So when we change a diaper we hit the appropriate button (I mounted it above the changing table) and it fires off and logs a diaper change (wet, solid, etc). Then using the Baby Buddy HA integration I have an automation that fires every time the “Last Diaper” time is changed, it then makes an API call to Grocy and deducts one diaper from the stock. I did it this way since we use the Baby Buddy app via the web interface on our phones as well, so this way if you log a diaper from the changing table buttons or from your phone the diaper stock is correctly updated.

https://github.com/babybuddy/babybuddy best app ever. Free, not selling your data, lots of features, can add multiple babies.

Tried to get my wife to use https://github.com/babybuddy/babybuddy but she wanted an app not a website.

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.

some context re the Matrix isses, long history apparently: https://github.com/matrix-org/synapse/issues/14481#issuecomm...

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

> 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