rofimoji VS Synapse

I would assume that they just mean rofi which is an app launcher that can be configured to do a lot more than just that. It can work as an emoji picker, calculator, and other general menus

Last week, I released version 6.0.0 with support for a new grid-like theme and some smaller stuff.

I use Rofimoji. It works on Wayland and Xorg.

you choose wrong subreddit, this doesnt have anything to do with i3, you can look at this github page, maybe it will help https://github.com/fdw/rofimoji

For these other emoji characters, one would typically need to turn to a helper application like the KDE Emoji Picker, the Gnome Emoji Selector, or a web browser with Emojipedia. There are also extensions for the rofi utility (rofi-emoji and rofimoji) which allow a lightweight solution for those not in full desktop environments.

I'm trying to set up an emoji picker on top of my rofi install. I found this repository that has a python install option: https://github.com/fdw/rofimoji

https://github.com/fdw/rofimoji see how they do this, you have to run some scripts over rofi. xdotool is what you are looking for i think.

Well recently I found rofimoji and it does exactly what the Windows picker does, but better - it's got great aliases so you can look up what you want without knowing exactly its name, etc. Somehow it's even in the community repository.

Emoji: Windows 10 has the most robust emoji picker there is. It opens with meta+. similar to plasma but that's where the similarity ends. Windows emoji picker doesn't copy paste emoji, it writes to the open window. User can input as many emoji as they like without pressing ctrl+v every time. I have tried many alternatives, Emote, rofimoji,x11-emoji-picker. Among those x11-emoji-picker is closest to windows but has a lot of bugs. I have had system freeze🥶🥶, no keyboard shortcut not working, frame drops🥴🥴🥴.

That was several years ago, and now [rofimoji](https://github.com/fdw/rofimoji) can do all UTF-8 characters (and custom ones), works on Wayland and is packaged for some distros. I'm so happy how my tiny project turned out and how many people helped with PRs and issues.

Professionally, I (and the whole team) lost track of our deployed artifacts, as we're not on a release schedule but also not really on continuous deployment. Mainly, we released when someone noticed that a release has been running stably on staging for a while.

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