ibus VS https-bot

1.5.29-rc2 was tagged on 9 Nov 2023 [1] and in did not contain "N_("CJK Unified Ideographs Extension I")," in src/ibusunicodegen.h [2].

Commit 228f0a77b2047ade54e132bab69c0c03f0f41aae from 28 Feb 2023 introduced this change instead. It's the same person who tagged 1.5.29-rc2 and committed 228f0a77b2047ade54e132bab69c0c03f0f41aae which is typically an indication the maintainer tar'd their checked out git folder and accidentally included changes not get committed.

[1] https://github.com/ibus/ibus/releases/tag/1.5.29-rc2

[2] https://github.com/ibus/ibus/blob/0ad8e77bd36545974ad8acd0a5...

[2] https://github.com/ibus/ibus/commit/228f0a77b2047ade54e132ba...

On https://github.com/ibus/ibus we can see gtk+ are probably only need for ibus-setup. I would like help to be sure i not miss any step.

I also know input methods work great in Ubuntu (Gnome Wayland) because Gnome supports ibus.

But the article is specifically about incompatibility of input methods among different DEs: Gnome, KDE, wlroots-based environments such as Sway and Hyprland.

After many years, ibus still doesn’t work with wlroots: https://github.com/ibus/ibus/issues/2182

The list of recommended IMEs on Sway are all WIP: https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway#...

Most people use fcitx5 with Sway because fcitx5 and Sway both support input method unstable v2. But the article explains that v2 is still not universally supported among wayland DEs, and that’s why it’s problematic.

Have no idea what the daemon does practically, here is the GitHub page.

The F38 beta is currently affected by two (mostly gaming-related) issues that you should be aware of: - https://gitlab.gnome.org/GNOME/mutter/-/issues/2678 -> a lot of SDL-based games have their fullscreen mode broken. The issue is bisected. - https://github.com/ibus/ibus/issues/2480 -> Keyboard input sometimes gets stuck. Issue has already been identified and we're waiting for an ibus release.

Also, to add to what u/Pizza-Driver said, it seems that ibus is not yet interoperable with the protocol used by Wayland display servers based on wlroots.

I meant ctrl+., but it looks like ibus recently changed their emoji input shortcut back to super+., so the gtk emoji picker should be available via ctrl+. again without requiring changes: https://github.com/ibus/ibus/commit/1520c39d0d6036da725fcecd932883be3f3d3575

Looks like it was changed here: https://github.com/ibus/ibus/commit/1520c39d0d6036da725fcecd932883be3f3d3575

It's inspired by this comment I made: https://news.ycombinator.com/item?id=26599746.

I actually saw several comments with HTTP URL posted, and that was the only one I bothered to comment on. So I thought that this is something better suited for bots than human.

I hacked this together over yesterday and today: https://github.com/fishy/https-bot.

Basically it uses the Firebase API (https://github.com/HackerNews/API) to find comments with HTTP URLs in them, try the HTTPS version, compare the contents, post back a comment if the contents are more than 95% similar.

The "95% similar" part was actually the first part I wrote in the code. At first I tried a few existing go packages implementing diff/lcs, but most of them was quite slow and does a lot of allocations when I'm comparing two randomly generated 10KiB blobs, so I wrote my own (https://pkg.go.dev/github.com/fishy/https-bot/similarity), which is optimized for space (it does almost no allocations), and it's also faster because allocations are slow. (I know this is an unfair comparison that most of the existing implementations need to give you an output that can be used to reconstruct the two blobs back, so at least some of their allocations are required and unavoidable)

I also wrote a bug that it would find the same HTTP url in every run and post the same comment over and over again. My apologize to dang or whoever dealt with it (or maybe the system is good enough that it blocked those repetitive comments automatically).

In the end it successfully made 6 comments across ~4 hours (not including the repetitive ones). All of those comments are flagged (likely due to hn policy), https://news.ycombinator.com/item?id=26692588 is the only one that's still visible to other users at the time of writing, if you are curious.

I just killed it completely from the request of dang. Although it only lived for a few hours, it's still a fun exercise. Maybe I'll convert it into a reddit bot next? Who knows.

Thank you for the feedback. I added FAQ to the README and answered this question: https://github.com/fishy/https-bot/blob/main/README.md#this-...