Searching We.Love.Privacy.Club

Twts matching #2
Sort by: Newest, Oldest, Most Relevant
thecanine
twtxt.net
 (30w ago)
↳ In-reply-to » Joining the Clippy profile picture club, now that I finally finished my custom one. Media

@movq@www.uninformativ.de Thanks, itā€™s mostly following the Louis Rossmann thing https://youtu.be/2_Dtmpe9qaQ - a symbol of protest, against the rapid enshitification the Internet is facing, accelerated to the extreme, during this year. It has reached a point where something really has to be done about it all. Obviously not just everyone changing their profile pictures, but also cataloguing all the consumer rights violations, invasion of privacy, censorship,ā€¦ to shove it in the face of as many government officials, as possible.

ā¤‹ Read More
movq
www.uninformativ.de
 (35w ago)
↳ In-reply-to » I was drafting support for showing ā€œapplication iconsā€ in my window manager, i.e. the Firefox icon in the titlebar:

@lyse@lyse.isobeef.org ā€œAdvancedā€, well, probably more ā€œmatureā€. There arenā€™t a ton of crazy features and that icon thing is the largest code addition in the last 10 years. %)

Speaking of OS/2 ā€¦ I just realized that Windows 3.x didnā€™t have icons, either. If Iā€™m not mistaken, this only got added in Windows 95. In other words, OS/2 had this feature before Windows did, because at least OS/2 2.1 from 1993 had icons. Who would have thunk.

(Now I kind of want to know which system really introduced this feature.)

ā¤‹ Read More
movq
www.uninformativ.de
 (35w ago)
↳ In-reply-to » I was drafting support for showing ā€œapplication iconsā€ in my window manager, i.e. the Firefox icon in the titlebar:

@lyse@lyse.isobeef.org Oh, huh, maybe it was just my GNOME 2 themes back then that didnā€™t show the icon. šŸ¤”

I like the looks of your window manager. Thatā€™s using Wayland, right?

Oh, no. Itā€™s still X11. All my recent Wayland comments resulted from me trying to switch, but I think itā€™s still too early. Being unable to use QEMU (because it canā€™t capture the mouse pointer) is a pretty big blocker for me. This is completely broken, it just happens to be unnoticeable with modern guest OSes, so itā€™s probably not a priority for devs.

(Not to mention that I would have to fork and substantially extend dwl in order to ā€œreplicateā€ my X11 WM. And then, after having done that, Iā€™d have to follow upstream Wayland development, for which I donā€™t have the resources. Things would need to slow down before I can do that.)

all that wasted space of the windows not making use of the full screen!!!1

Heh. Iā€™ve been using tiling WMs for ~15 years now, so itā€™s actually kind of refreshing to see something different for a change. šŸ˜…

Probably close to the older Windowses.

That particular theme is a ripoff of OS/2 Warp 3: šŸ˜…

We ran some similar brownish color scheme (donā€™t recall its name) on Win95 or Win98

Oh god. Yeah, I wasnā€™t a fan of those, either. šŸ„“

ā¤‹ Read More
lyse
lyse.isobeef.org
 (35w ago)
↳ In-reply-to » I was drafting support for showing ā€œapplication iconsā€ in my window manager, i.e. the Firefox icon in the titlebar:

@movq@www.uninformativ.de According to this screenshot, KDE still shows good old application icons:

Image

And GNOME used to have them, too:

Image

I like the looks of your window manager. Thatā€™s using Wayland, right? The only thing on this screenshot to critique is all that wasted space of the windows not making use of the full screen!!!1 At least the file browser. 8-)

This drives me nuts when my workmates share their screens. I really donā€™t get it how people can work like that. You canā€™t even read the whole line in the IDE or log viewer with all the expanded side bars. And then thereā€™s 200 pixels on the left and another 300 pixels on the right where the desktop wallpaper shows. Gnaa! Thereā€™s the other extreme end when somebody shares their ultra wide screen and I just have a ā€œregularishā€ 16:10 monitor and donā€™t see shit, because itā€™s resized way too tiny to fit my width. Good times. :-D

Sorry for going off on a tangent here. :-) Back to your WM: It has the right mix of being subtle and still similar to motif. Probably close to the older Windowses. My memory doesnā€™t serve me well, but I think they actually got it fairly good in my opinion. Your purple active window title looks killer. It just fits so well. This brown one (

Image

) gives me also classic vibes. Awww. We ran some similar brownish color scheme (donā€™t recall its name) on Win95 or Win98 for some time on the family computer. I remember other people visting us not liking these colors. :-D

ā¤‹ Read More
movq
www.uninformativ.de
 (35w ago)

I was drafting support for showing ā€œapplication iconsā€ in my window manager, i.e. the Firefox icon in the titlebar:

Then I realized: Wait a minute, lots of applications donā€™t set an icon? And lots of other window managers donā€™t show these icons, either? Openbox, pekwm, Xfce, fvwm, no icons.

Looks like macOS doesnā€™t show them, either?!

Has this grown out of fashion? Is this purely a Windows / OS/2 thing?

ā¤‹ Read More
movq
www.uninformativ.de
 (35w ago)

Only figured this out yesterday:

pinentry, which is used to safely enter a password on Linux, has several frontends. Thereā€™s a GTK one, a Qt one, even an ncurses one, and so on.

GnuPG also uses pinentry. And you can configure your frontend of choice here in gpg-agent.conf.

But what happens when you donā€™t configure it? Whatā€™s the default?

Turns out, pinentry is a shellscript wrapper and itā€™s not even that long. Here it is in full:

#!/bin/bash

# Run user-defined and site-defined pre-exec hooks.
[[ -r "${XDG_CONFIG_HOME:-$HOME/.config}"/pinentry/preexec ]] && \
        . "${XDG_CONFIG_HOME:-$HOME/.config}"/pinentry/preexec
[[ -r /etc/pinentry/preexec ]] && . /etc/pinentry/preexec

# Guess preferred backend based on environment.
backends=(curses tty)
if [[ -n "$DISPLAY" || -n "$WAYLAND_DISPLAY" ]]; then
        case "$XDG_CURRENT_DESKTOP" in
        KDE|LXQT|LXQt)
                backends=(qt qt5 gnome3 gtk curses tty)
                ;;
        *)
                backends=(gnome3 gtk qt qt5 curses tty)
                ;;
        esac
fi

for backend in "${backends[@]}"
do
        lddout=$(ldd "/usr/bin/pinentry-$backend" 2>/dev/null) || continue
        [[ "$lddout" == *'not found'* ]] && continue
        exec "/usr/bin/pinentry-$backend" "$@"
done

exit 1

Preexec, okay, then some auto-detection to use a toolkit matching your desktop environment ā€¦

ā€¦ and then it invokes ldd? To find out if all the required libraries are installed for the auto-detected frontend?

Oof. I was sitting here wondering why it would use pinentry-gtk on one machine and pinentry-gnome3 on another, when both machines had the exact same configs. Yeah, but different libraries were installed. One machine was missing gcr, which is needed for pinentry-gnome3, so that machine (and that one alone) spawned pinentry-gtk ā€¦

ā¤‹ Read More