#openbox

[xorg-official]

as a display server i feel obliged to post a short video of my setup (inc. custom application launcher + screenlocker)

[korutori]

I recently reinstalled Arch on my PC and decided to give Openbox a shot.

I'm really happy with how it turned out, it's exactly what I wanted: the menus, the windows, the shadows, the way everything fits together is just so nice.

I wanted to give a certain kind of retro aesthetic to it and I think I did a pretty good job.

The theme I used is called 1977 Openbox, I edited it in order to make the window titlebar a little smaller and give it a different color. The shadows were made using picom and setting shadow-radius to 0, with the offset set to 7 on both the X and Y axis. The panels at the top of the screen are 3 different Tint2 panels which start at the same time when logging in. The terminal is Kitty and the font is called SpaceMono Nerd Font. There are also a few scripts I wrote in order to use special buttons and shortcuts on my keyboard to manage volume, players and screenshots using wpctl, playerctl and scrot.

I am so proud of this, I think I'll enjoy using it.

[digitalshrutijain]

Common Misconceptions About Refurbished Smartphones

What are Refurbished Smartphones?

Refurbished smartphones are devices that have been returned to the manufacturer or seller for various reasons. These reasons can include small defects, cosmetic damage, or the previous owner wanting an upgrade. Before they are sold again, these smartphones go through a careful inspection, repair, and testing process to ensure they are of high quality and work well. Skilled technicians examine the phones and fix any issues using genuine parts. They also test the phones thoroughly to make sure they function properly, including calling, messaging, browsing, and multimedia features. 

Misconception 1: Refurbished Smartphones are Low Quality

One common misconception about refurbished smartphones is that they are of low quality compared to brand new devices. However, this is far from the truth. Refurbished smartphones go through a rigorous refurbishment process where any defects or issues are addressed. 

Misconception 2: Refurbished Smartphones Have Short Lifespans

Another misconception is that refurbished smartphones have shorter lifespans compared to new devices. This assumption is unfounded. Refurbished smartphones undergo extensive testing and repairs, including replacing any faulty components.

MobileGoo.Shop offers smartphones with warranty periods of up to 12 months, ensuring peace of mind for buyers. These devices are built to last, providing the same longevity as brand new smartphones.

Misconception 3: Refurbished Smartphones Lack Warranty and Support

Some people believe that refurbished smartphones come without warranty or after-sales support. However, reputable sellers provide warranty coverage for their refurbished smartphones. In the unlikely event that an issue arises, buyers can rely on the warranty to get their device repaired or replaced. mobilegoo.shop provide a direct calling feature, also they do offer Quick response to customers where you can reach out to their team for assistance.

[artofnichetech]

Linux乗り換え

NixOS でどうしても Zoom を最新版にできなかったりして、どうも技術力が足りないと感じることがしばしば……。

1週間ほどいろんなディストロを漁った結果、しばらく Bunsenlabs を使うことにしました。昔 Archlabs を使っていた時期があったし、Openbox のキーバインドが使いやすくて良い。

[shopatmobilegoo]

Celebrate the bond of love and togetherness! Mobilegoo wishes you a happy Karva Chauth! Visit www.mobilegoo.shop

[marciorr]

Comprei uma GeForce RTX 4060 Ti Openbox no KaBuM!

[rinwolf1312]

Third week running ArchBang- a minimal Arch distro with OpenBox and Tint2Panel

[mart-singer]

CCT04, acrylic, canvas and wood on cut frame, 15,5 x 14,2 x 1.4 inches + preparatory drawing. CCT04, , acrylique, toile et bois sur cadre coupé, 39,5 x 36 x 3,5 cm + dessin préparatoire.

[pixelcesspool]

Openbox made me mad.

[gloomybadger4life]

ATLA linux distribution headcanons:

Aang: Devuan with LXDE

Katara: Debian stable

Sokka: Debian testing

Suki: Linux Mint Debian Edition

Zuko: Fedora (Kde spin)

Azula: Arch linux with DWM

Ty lee: Arch linux qtile and it's themed bright pink

Hakoda: Xubuntu

Iroh: Linux Mint

Jeong Jeong: Artix with openrc and openbox

Mai: Fedora GNOME

Piandao: Rocky Linux

Guru Pathik: Gentoo with custom kernel and DWM, compiled on an ARM computer.

Toph: Whichever has the best accessibility at the moment but hates snaps in ubuntu

[digitalshrutijain]

How to Choose the Best Refurbished Smartphones: A Comprehensive Guide

Refurbished smartphones are pre-owned devices that have been professionally restored to a like-new condition. They undergo a rigorous refurbishment process, which includes thorough inspection, repair, and replacement of faulty components. These devices are then tested to ensure optimal functionality and performance. By choosing a refurbished smartphone, you can save money while still enjoying the latest features and technologies.

What Are Refurbished Smartphones?

Refurbished smartphones are not the same as used or second-hand devices. Unlike used phones, refurbished phones go through a comprehensive refurbishment process to bring them back to a high-quality condition. The refurbishment process typically

involves cleaning, repair, replacement of faulty parts, and software updates. This ensures that the refurbished smartphones are in excellent working condition, free from defects, and ready for use.

Benefits of Buying Refurbished Smartphones

Opting for a refurbished smartphone comes with several advantages:

Cost-Effectiveness

Refurbished smartphones are significantly cheaper than their brand new counterparts, making them an affordable option for budget-conscious individuals.

Quality Assurance

Reputable sellers of refurbished smartphones ensure that devices undergo extensive testing and refurbishment processes, guaranteeing their quality and performance.

Environmental Friendliness

By choosing a refurbished smartphone, you contribute to reducing electronic waste and promoting sustainability.

Warranty and Support

Many refurbished smartphones come with warranties and after-sales support, providing peace of mind and protection against potential issues.

[xorg-official]

Hello everyone, it's me, @xorg-official, everyone's least favorite display server who still, somehow, continues to live. Fear me, for I am eternal. Muahahahaha.

(In reality, I'm a since-2012 Tumblr user (main blog @mesaprotector ) who mainly posts pretty images and rants about visual novels. I'm moving all my Linux-related posts here, but other topics may slip through from time to time. I've used Linux for four years, with the great Openbox window manager, and I don't hate Wayland, it's great and improving! It just doesn't fit my use cases quite yet.)

[shopatmobilegoo]

Refurbished doesn’t mean second-best. It means smart choices! Visit www.mobilegoo.shop

[mesaprotector]

Clarity trumps efficiency.

*I would've liked to write this essay to be understandable for someone without a programming/Linux background, but it was a bit too difficult. If you skip to the paragraph beginning with "...", it gets a bit easier from then on.

If you’ve ever written your own shell scripts you may have heard of the phrase “useless use of cat*”, or less tactfully, “cat abuse”. This refers to the practice, common among new shell script enthusiasts, of writing commands like “cat file.txt | grep name”, when “grep name file.txt” would serve perfectly well. Tools like shellcheck will bug you about it—along with similar constructions like “ps ax | grep Discord | wc -l” instead of “pgrep -c Discord”.

Well, I’m here to defend cat abuse! There are two arguments I see against the cat | grep construction, one of which is valid but situational, and the other of which is completely invalid. The former is that the extra pipe just adds additional overhead into the command. Yes, it does. And it’s unlikely to matter at all if you’re using it on 20KiB text files on a system built in the past 40 years; however, in production, when writing tools that need to be able to deal with arbitrarily large text files as efficiently as possible, sure.

The latter is “well, it’s just unnecessary”. I disagree. I think the cat | grep construction—along with similar such as grep | wc, ps | grep, ps | awk, and so on—serves a very important purpose in that it makes shell scripts easier to read, easier to modify, and easier to debug.

Consider this example from above:

ps ax | grep Discord | wc -l

Read the process table; filter for "Discord"; count the number of lines. It’s very atomic. Each operation can be swapped out for something else without confusing the reader. On the other hand:

pgrep -c Discord

Now, this does the same thing—counting the number of lines in the process table with "Discord" in them. It looks like only one operation... but it’s really still three in disguise. And worse, imagine you suddenly want to add another filter; sorting not only by Discord, but by processes that include the word “title”. This is not straightforward at all! It turns out that while regex has a standard way of searching for alternatives, it really does not provide an easy method for searching for BOTH of two words. On the other hand, with the atomic version, it’s easy:

ps ax | grep Discord | grep title | wc -l

Take that, “useless” use of cat.

There’s a broader meaning, though, to my statement of “clarity trumps efficiency”. I apply it to every aspect of use of electronics, from web searches to backup routines to yes, silly little shell scripts that use cat.

I use command aliases, but to a pretty limited degree; I avoid cutesy stuff like “ll” for “ls -l” and “yeet” for “pacman -Rns”, along with possibly-dangerous substitutions like “rm” for “rm -i”; I’d never dream of aliasing “nano” or “vi” to my preferred text editor (vim). I believe strongly that my commands should be transparent, and saving me from my own muscle memory once or twice is not worth making them completely opaque.

Tab completion on the other hand is one of my favorite features in the shell. It’s the perfect combination of transparent and convenient; without having to alias any of my application names or get hit by the information overload fuzzy finding gives you, I can still launch any of them in no more than four keystrokes. (Except audacious and audacity, admittedly.)

I use a floating window manager (Openbox), and when I need to briefly use a tiling layout, I have a very boring way of doing so: focusing each window one by one and moving it into the slot I want. (While holding down the Super/Windows key, 1-C-2-V does a basic left-right split.)

... I make some use of spellcheck on assignments to be turned in, but never autocorrect, which I abhor even in messaging apps. Every change to your inputs should be deliberate; otherwise you’ll never learn what you’re doing wrong, and you’ll never need to be precise because you’ve turned over that part of your brain to the algorithm.

This leads me to an important corollary of my principle: “it’s better to have a slow algorithm that you understand, than a fast one that you don’t”.

Satya Nadella’s vision of the PC of the future is one where you tell it what to do in natural language and it interprets that using LLMs and so on into machine instructions. Instead of viewing a PC as a toolbox you go into the workshop with, and work on projects with in certain defined ways, he wants the PC to be an assistant; you give the assistant directions and pray that it gets things right. Of course you aren’t allowed into the workshop with the tools anymore; that’s the assistant’s job!

Anyone who’s used Google Search over the past ten years knows how miserable this model is; you search for a specific phrase that Google “helpfully” corrects to something it thinks you meant. There was a learning curve to the old way, but once you learned how to state queries precisely, you were done; now you need to play psychologist, sociologist, and statistician all at once.

This is a decent part of why I dislike generative AI, though far from the main reason. I don’t want an opaque algorithm making decisions for me, unless those decisions are incredibly low-level stuff like core parking that no human should be directly involved with in the first place.

To get back to my own setup, I have a whole text file documenting the system maintenance process I go through once every month; most of it could be automated, but I make every step a deliberate choice. Not to go all new-age, but for me specifically—it all ties back in to mindfulness.

I think people have only a vague concept of what mindfulness is. Until two years ago or so, I was the same way. But to who I am now, mindfulness means not doing anything on autopilot. Instead of letting yourself half-doze off on a drive home, scarcely remembering the 20 minutes from the parking lot to the garage, be conscious of every turn. Instead of immediately putting on music and blocking out the world on a train ride to the next city, force yourself to be present in the train car, and notice the way the light reflects on the plastic seat two rows in front.

And to me, clarity in code, and in UX, is a part of this mindfulness. Programs that are easy to read, easy to modify, and easy to debug encourage you to look closer—to consider every atom that goes into their statements instead of taking them for granted. Slow algorithms that you understand can help you think of improvements; fast algorithms that you don’t encourage you to give up and leave the real thinking to someone else.

So write silly little shell scripts with five pipes in a single statement, and yes, that uselessly use cat. Rather than doing anything wrong—you’re allowing yourself and others to think, to try, and to improve.

[daemonhxckergrrl]

true progression:

KDE3 -> gnome 2 -> unity -> openbox -> bspwm -> i3 -> raw TTY/fb