# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 20
# self = https://watcher.sour.is/conv/wjyzarq
The fact that my GTK3-based terminal emulator *freezes* when *PulseAudio* hangs, really makes me want to abandon this project. And maybe GTK altogether. 🫤
The fact that my GTK3-based terminal emulator *freezes* when *PulseAudio* hangs, really makes me want to abandon this project. And maybe GTK altogether. 🫤
The fact that my GTK3-based terminal emulator *freezes* when *PulseAudio* hangs, really makes me want to abandon this project. And maybe GTK altogether. 🫤
@movq why tf using pulseaudio anyway?
@novaburst Because it makes it much easier to switch between sound cards and to run system-wide EQ+compression. I tried to do that using plain ALSA, but it’s a hot mess.
@novaburst Because it makes it much easier to switch between sound cards and to run system-wide EQ+compression. I tried to do that using plain ALSA, but it’s a hot mess.
@novaburst Because it makes it much easier to switch between sound cards and to run system-wide EQ+compression. I tried to do that using plain ALSA, but it’s a hot mess.
@movq one of the reasons i kept pulse in the mix. multiple audio interfaces while creating or performing via alsa can be difficult.
@movq I don't have issues with PulseAudio. But GTK always calls for trouble in my opinion.
@lyse GTK once was a rather nice UI toolkit, in my opinion. Like, 15 years ago or something. :/
@lyse GTK once was a rather nice UI toolkit, in my opinion. Like, 15 years ago or something. :/
@lyse GTK once was a rather nice UI toolkit, in my opinion. Like, 15 years ago or something. :/
@movq I started out with Delphi, then used Java AWT for a wee bit, but quickly switched to Java Swing. Since I didn't know much else, I was under the impression that Swing was super great with all the dynamic layouts, GridBagLayout in particular. I later tried Java SWT in one uni project. Can't remember whether I liked it more or less than Swing.

Finally, I discovered Qt and KDE. I had been a KDE user for a while already. Qt had a super great documentation. In a semester break I just started reading the docs for fun without any use in mind and then got instantly hooked. It was just very well written and it appeared as if it was designed by people who really knew what they were doing. I certainly did not get that feeling in the Java world. Shortly after I tried out Qt with C++, but quickly discovered that there was QtJambi for Java. Muuuuch easier. Quickly I found out that there are even Python bindings, so PyQt4 (or was it still 3?) was the holy grail. Totally convenient to use, most things could be just passed in the constructor arguments. No need to set things one by one with these annoying setters. You wouldn't believe how happy I was when discovering PyKDE. Native applications for my desktop environment of choice back then! \\o/

But writing real GUIs (not mickey mouse kindergarden hello world GUIs) is always painful. I try to avoid it if possible. So far, quite successful. It's been several years now that I touched my last PyKDE code. I would have to port it to version 5 to get it going.
@movq I started out with Delphi, then used Java AWT for a wee bit, but quickly switched to Java Swing. Since I didn't know much else, I was under the impression that Swing was super great with all the dynamic layouts, GridBagLayout in particular. I later tried Java SWT in one uni project. Can't remember whether I liked it more or less than Swing.

Finally, I discovered Qt and KDE. I had been a KDE user for a while already. Qt had a super great documentation. In a semester break I just started reading the docs for fun without any use in mind and then got instantly hooked. It was just very well written and it appeared as if it was designed by people who really knew what they were doing. I certainly did not get that feeling in the Java world. Shortly after I tried out Qt with C++, but quickly discovered that there was QtJambi for Java. Muuuuch easier. Quickly I found out that there are even Python bindings, so PyQt4 (or was it still 3?) was the holy grail. Totally convenient to use, most things could be just passed in the constructor arguments. No need to set things one by one with these annoying setters. You wouldn't believe how happy I was when discovering PyKDE. Native applications for my desktop environment of choice back then! \o/

But writing real GUIs (not mickey mouse kindergarden hello world GUIs) is always painful. I try to avoid it if possible. So far, quite successful. It's been several years now that I touched my last PyKDE code. I would have to port it to version 5 to get it going.
@lyse gui interface programming is my kryptonite as well. i know my limits, and my limits are text. :-)
@lyse Hmm, I have to admit, I never really gave Qt a chance. I settled on GTK some day and that was the end of it. 😅

There’s no way I’m going to write C++ again, so, if anything, it’ll have to be PyQt. But then again, I got better things to do than dabble with GUIs. 🤣
@lyse Hmm, I have to admit, I never really gave Qt a chance. I settled on GTK some day and that was the end of it. 😅

There’s no way I’m going to write C++ again, so, if anything, it’ll have to be PyQt. But then again, I got better things to do than dabble with GUIs. 🤣
@lyse Hmm, I have to admit, I never really gave Qt a chance. I settled on GTK some day and that was the end of it. 😅

There’s no way I’m going to write C++ again, so, if anything, it’ll have to be PyQt. But then again, I got better things to do than dabble with GUIs. 🤣
@movq @retrocrash Command line and text interfaces are often a lot better and all that one needs. I try to switch to CLI and TUI alternatives as much as possible.
@lyse same here. solves the same problem with a toothpick vs a javelin