monovergent

joined 1 year ago
[–] monovergent@lemmy.ml 7 points 3 days ago

“suicide linux”

Looked it up with quotes and the first update in the first search result:

Update 2011-12-26

Someone has turned Suicide Linux into a genuine Debian package. Good show!

:(

[–] monovergent@lemmy.ml 11 points 5 days ago (1 children)

It's nice and easy on the eyes. I conjecture that glossy and matte (as seen here) styles of skeuomorphism gave way to more abstract design since:

  • Skeuomorphism is hard to get just right without being excessive and tacky
  • Saturated, simple blocks of color pop out more, particularly on the increasingly prevalent mobile UI
  • And thus also have better shelf appeal

If it were up to me, the red line would be when buttons and interactive elements are indistinguishable from text. The stock Android settings is probably among the worst offenders in this regard.

What I really miss is light mode that isn't hated for blinding users and dark mode that doesn't plunge the user into the void. Those "toolbars" look lovely, perfect for any lighting condition or time of day. I've yet to understand why, at present, designers insist on pure white everywhere when it comes to light mode. Maybe everyone is using the night light filter so it doesn't matter? At least pure black dark mode makes sense for power efficiency on OLEDs.

[–] monovergent@lemmy.ml 6 points 5 days ago
  • Debian stable (w/ XFCE). No-nonsense, excellent community support, well-documented, low-maintenance, and runs on anything so I can expect things to work the same way across all of my machines, old, new(ish), or virtual
  • Just flexible enough that I can customize it to my taste but not so open-ended that I have to agonize over every last config
  • It's been around for many years and will be around for many more
  • I often entertain the idea of moving to Alpine or even BSD, but I can't resist the software selection available on Debian
[–] monovergent@lemmy.ml 9 points 1 week ago

Microsoft shouldn't revoke license keys unless it's a leaked VL key being spread around for piracy or the like. The semi-annual major updates seem to count as "versions" like Windows 11 22H2 (now end of service) vs Windows 11 24H2 (current). That said, it's a poorly worded error message and it doesn't help that Windows 11 will cry wolf at every opportunity.

 

Decided to uninstall my display manager and use startx instead. But now when I resume from suspend, the brightness keys cease to work until I log out and back in. Backlight does still respond when echoing into /sys/class/backlight/intel_backlight/brightness. But what kind of magic does a display manager do to keep brightness controls working after suspend and resume?

Using xfce on tty1 on an X230 if it matters.

[–] monovergent@lemmy.ml 5 points 1 week ago

Debian Stable. Predictable, low-maintenance, and well-supported. From time to time, I think about switching over to Alpine or even BSD, but the software selection and abundance of Q&A posts for Debian and its derivatives keeps me coming back. Having been a holdout on older Windows versions in the past, I'm quite used to waiting for new features and still amazed at how much easier life is with a proper package manager.

[–] monovergent@lemmy.ml 9 points 3 weeks ago

XFCE4. It's intuitive and predictable without sacrificing the ability to customize it exactly the way I want (with Chicago95 ofc). The built-in panel widgets are nothing short of amazing: battery, CPU, RAM, network, and disk monitors with labels toggled off to save space and a clock with only what I need on one line: MM/DD HH:mm:ss

Enough features so that it "just works" (no nitpicking through config files), especially on laptops, without being bloated in any way. Bonus of its lightweight nature is that I can keep my Debian/XFCE setup consistent across all of my machines, both old and new.

Can't wait for the finished xfwm4 port to wayland so I don't have to sacrifice some security running X11 and so I can do fractional scaling on hidpi machines.

 

I like my Linux installs heavily customized and security hardened, to the extent that copying over /home won't cut it, but not so much that it breaks when updating Debian. Whenever someone mentions reinstalling Linux, I am instinctively nervous thinking about the work it would take for me to get from a vanilla install to my current configuration.

It started a couple of years ago, when dreading the work of configuring Debian to my taste on a new laptop, I decided to instead just shrink my existing install to match the new laptop's drive and dd it over. I later made a VM from my install, stripped out personal files and obvious junk, and condensed it to a 30 GB raw disk image, which I then deployed on the rest of my machines.

That was still a bit too janky, so once my configuration and installed packages stabilized, I bit the bullet, spun up a new VM, and painstakingly replicated my configuration from a fresh copy of Debian. I finished with a 24 GB raw disk image, which I can now deploy as a "fresh" yet pre-configured install, whether to prepare new machines, make new VMs, fix broken installs, or just because I want to.

All that needs to be done after dd'ing the image to a new disk is:

  • Some machines: boot grubx64.efi/shimx64.efi from Ventoy and "bless" the new install with grub-install and update-grub
  • Reencrypt LUKS root partition with new password
  • Configure user and GRUB passwords
  • Set hostname
  • Install updates and drivers as needed
  • Configure for high DPI if needed

I'm interested to hear if any of you have a similar workflow or any feedback on mine.

[–] monovergent@lemmy.ml 3 points 3 months ago

What did it in were the semi-annual mandatory feature updates, which restored the invasive settings and bloat I worked hard to remove. Already being acquainted with Linux at that point, I began dual-booting and later having Windows on an entirely separate machine for a few stubborn programs I needed for work.

What made me acquainted with Linux was looking for alternatives after the loss of theming options and the start menu in Windows 8. That eventually brought me to my present Debian setup with the Chicago 95 theme, which recreates (and even improved) the workflow and stability I had grown to love in Windows 2000.

The first time I ever booted into a Linux iso, however, was to migrate files off of my machine, which was excruciatingly slow to transfer files under XP.

[–] monovergent@lemmy.ml 1 points 3 months ago

If you want to avoid this judgement, get an Apple silicon Macbook Air or something...

Damn, me over here trying to flex my Chicago95-ass X201T to my classmates

[–] monovergent@lemmy.ml 12 points 3 months ago* (last edited 3 months ago) (1 children)

Storytime!

As a physics major, daily driving Linux worked out pretty smoothly. The thing that saved me from trouble the most was making a weekly full system backup (I used Clonezilla and my file server). If anything was truly incompatible, I took care of it on the school's computers.

In my second semester, I began dual-booting on my X201 Tablet and desktop, eventually booting into Windows infrequently enough that I made my X201T Linux-only by the end of my second year.

Around that point, I began using LUKS full-disk encryption on my machines and USB drives. I highly recommend if you don't already, even if just for peace of mind. I have strong ideas about the way things ought to look and work, so being able to customize Linux to my heart's content (with Chicago95 ofc) made doing work on my computer a bit more enjoyable.

Documents

  • MS Office: Libreoffice worked 95% of the time. For the other 5%, I used the school computers or my Windows VM.
  • Google Docs and GMail: accessed through Chromium, which I only used to access Google and sites linked to my school's SSO system.
  • We did a lot of writing in Latex, though it might be a physics thing
  • A lot of other small stuff I'm starting to forget, but if I don't mention it, I probably did it through the browser.

Lab

  • MATLAB: GNU Octave sufficed 75% of the time, often needing just slight changes to the code. Otherwise I used the lab computers or my desktop with actual MATLAB.
  • Proprietary dana analysis software: One had a .deb package for oldoldoldstable so I set up a VM just for that. Otherwise, lab computers it was.
  • Lab computers running old and new versions of Windows were available to us, so if there was anything computationally intensive or requiring proprietary software, I would just take care of it in the lab.

Social

  • Slack, Discord, Facebook, Instagram, Whatsapp: browser client, which I would check on a schedule

Tools

  • VPN: NetworkManager, though it was a bit janky. I think it's a lot better nowadays.
  • Printing: We had a web print portal to upload docs and pdfs to a printer of our choice.

Graphics

  • Mostly prepared my posters, etc in a mix of Libreoffice Draw, GIMP, and Inkscape
  • Adobe: Had to use it on one occasion. Used the library computers where it was installed for everyone to use.
  • Digital notes: I would use Xournal on my X201 Tablet whenever I forgot to bring my notebook or refill my fountain pen. Managed to impress a few of my iPad-toting classmates when I whipped out the pen and the display around on what they believed to be an ancient clunker.

As for the desktop, I had purchased it with gaming in mind, but it eventually became my SMB file share, media server, and RDP session host so I could make any library desktop like my own. Each thing in its own VM, of course. By the end of it, I was one of about 3 students running a server over the campus LAN. Even in the comp sci department, surprisingly few students used Linux.

Linux also met all of my computing needs while studying abroad in Germany. For five whole months, I had not used Windows once. Though my SSD did give out on me once, a backup saved the day.

A friend once did need to use a rather invasive remote proctoring tool. Highly recommend a separate laptop or at least a fresh SSD for this case.

Mobile privacy, if it's relevant

  • I was in the fortunate position where none of my classes or jobs required proprietary mobile apps
  • Friends used Venmo or whatever else, I paid back in cash
  • SMS and emails sufficed for regular communication

Overall, it was smooth sailing using Linux throughout my college years and no incompatibilities that couldn't be solved in the library or a computer lab.

edit: i used debian btw

[–] monovergent@lemmy.ml 16 points 3 months ago (2 children)

Wayland, but I'm patiently waiting for xfce to support it

[–] monovergent@lemmy.ml 17 points 4 months ago (12 children)

yt-dlp. Too many options to remember and look up every time, but all useful and missing from GUIs when you just want to dowload audio or 'good enough' quality video in batches without re-encoding.

While nmtui is perfectly fine for the CLI-uninitiated, I sometimes wonder why the nm-connection-editor window doesn't provide the same level of functionality.

[–] monovergent@lemmy.ml 17 points 4 months ago

A metal 128 GB USB on my keychain next to the U2F key

16 GB Ventoy partition with:

  • Clonezilla ('deploying' my system image and backups)
  • Mint Debian Edition (everything needed to test and recover my Debian systems)
  • Debian netinstall
  • Various manuals and reference documents
  • Portable CrystalDiskInfo and VeraCrypt for Windows
  • Dumping grounds for files that I intended to transfer between machines, particularly the XP retro gaming rig
  • An optimistic IF-FOUND.TXT
  • KeePass
  • Previously Windows, until once upon a time, I booted into WinRE via Ventoy, got confused between X:, C:, and whatever else, and proceeded to nuke my USB instead of another disk. The Windows installer lived on its own USB happily ever after.

And a LUKS encrypted partition in the remaining space with more documents and a backup of almost all of my photos.

 

As I understand it, X11 has many inherent security concerns, including programs being able to read the contents of other windows and intercept keystrokes. Wayland addresses these concerns but at the moment breaks certain functions like screen readers, cursor warping, and the ability of a program to resize its own window.

I am curious as to how the display protocols of MacOS and Windows handle these situations differently. How does a program in those operating systems gain permission to read the contents of other windows, if at all? What is to be done in Wayland for these functions to be more seamless or are there inherent obstacles?

view more: next ›