gtk
Synapse
gtk | Synapse | |
---|---|---|
6 | 367 | |
74 | 11,720 | |
- | - | |
0.0 | 9.8 | |
about 2 years ago | 5 months ago | |
C | Python | |
GNU General Public License v3.0 or later | 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.
gtk
-
GNOME’s self-serving nature (and why they’re right).
Eh, someone actually has a fork of GTK3 with that feature, and I believe someone pointed that out in the issue tracker already, but then the devs were just like "no PR/MR, doesn't exist from our perspective". Granted the person who made the patch does say in the fork's readme that they don't expect it to be in an acceptable form for the GTK devs anyway.
-
gtk file picker icon view patch for void?
New user here. I searched online for void package template for gtk patched with this applied https://github.com/Dudemanguy/gtk , but I didn't find anything particular. If I understand correctly, it's not just a patch applied to main gtk source is it? Is there any chance void template for this exists somewhere online?
-
Happy Birthday Filepicker Bug!
Gtk2(repo): https://github.com/Dudemanguy/gtk/tree/gtk2-filechooser-icon-view
-
qutebrowser v2.0.0 released (with better adblocker)!
I've been using this (patched variant of gtk)[https://github.com/Dudemanguy/gtk], which is okay, but it seems a bit overkill and possibly unwise to use a non-official GTK just for image previews. Writing this, I realize that going the KDE route may indeed be a much cleaner solution.
-
HN comments on gnome
Someone made a fork specifically to fix this one issue here, there's even an AUR package for it, and apparently it's still being maintained (said AUR package was last updated two days ago).
-
Element – All-in-one secure chat app for teams, friends and organisations
Someone created a fix for this 3 years ago. The Gnome maintainers refuse to add it for whatever reason.
https://github.com/Dudemanguy/gtk
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