Given some other very strong and interesting discussion on male loneliness recently (I'm intentionally not linking to avoid adding to drama or bringing that tension here), I thought I'd try and spark a discussion on what I see a major problem that addresses male loneliness significantly without digging into the thorniness of gender norms and responsibilities: the death of third spaces.

There has been a decent amount of writing on the fact that third spaces - spaces that are not home or work where people can meet, hang out and build community - have been disappearing since at least the 90s (and really going extinct since Covid), and that we need to actively recreate them. But I have not yet seen any proposal that I think could be easily replicated and addresses the core needs that third spaces address. In fact, I haven't even seen any agreed-upon definition of what an ideal third space is, or what specific needs they should address!

So, let's talk about it. In no particular priority or order:

• What are some third spaces you enjoy or fondly remember?
• What are the key features of third spaces to you? Do they need to be free, or just low enough cost that people can join in relatively easily?
• What key needs should a good third space address?
• Who should run them? The government? Community groups? For-profit?
• Are there any groups or initiatives that have shown a good formula for re-creating third spaces across their communities?
• How do we ensure people are motivated to join third spaces? We aren't going to get really lonely, isolated people out just by opening up doors most of the time.

Have you watched any TV shows recently you want to discuss? Any shows you want to recommend or are hyped about? Feel free to discuss anything here.

Please just try to provide fair warning of spoilers if you can.

Back in the relatively recent years of 2017(or maybe not, that's nine years ago already), smartphone standards were far below what they are today. You could find phones configured with less than a gigabyte of RAM and 16GB of storage could be considered reasonable. Granted, these weren't going to be considered spec beasts during their time, but they were serviceable for the price. However, as compute power increased, these stragglers failed to hold on after being cluttered by user activity like bottlenecked storage or simply higher spec requirements. Thusly, Android Go was born around the tail end of 2017.

I don't intend to make this a history post, but just for the sake of comprehensiveness, Android Go really took stride by doling out optimizations for barebones cellphones and limiting some features like picture in picture and split screen. It really hit it's stride around Android 11 to 12, when phones were still transitioning to modernly reasonable specs.

Mayhaps the most surprising part is that the main constituent of Android Go is essentially a hard-bound toggle set by the manufacturer. But what may be overlooked is that Android Go still exists in the present day. So some developers still end up using it! But why does it still see use in the present day?

In the current iteration of Android Go, phones with 4GB of RAM or less by default are required to use Android Go. But nowadays, we can utilize virtual RAM extensions by allocating some storage space as quick read memory in settings. So this gives manufacturers the power to provide 8GB Android Go phones, making them honestly ovespecced for their on paper capabilities. Often times, these phones have to tone down their bloatware too, so that they don't sap the phone of too much power.
It isn't all upside though, as the aforementioned limitations on multitasking features are arguably the biggest deal breaker.

Manufacturers that use Android Go today are those that have models that cater to ultra-budget and emerging markets. Lower end Motorola and Redmi phones are the ones that are widely available. A notable example are all the phones of Transsion, whose main target market is in Africa and emerging SEA countries.

What's the experience of using it today though?
Aside from the PiP and split screen, The biggest difference isn't really all that strict: the Android Go apps. These can even be downloaded on regular Android and are often just stripped down and more data efficient versions of official Google apps that haven't been given the fresh do-over of Android Go itself. The notable exception is that Android Go will always have Google Assistant, for Google doesn't have plans to release a version of Gemini for Go. Which is ironic as EoL Android phones with lower spec than the current maximum of Android Go(4GB RAM) actually do have Gemini OTA updated on them. Go phones are trying to modernize, so they nowadays have 120hz screens, punch-hole cameras, and enough compute power for everyday. And yet they still compromise by having SD card slots and headphone jacks. The rest is really in the hands of your OEM. Samsung, Redmi, and the Transsion phones all have their little tweaks on the software, some being a little more egregious than most (cough Samsung cough). Motorola should be mostly stock though.

All in all, I just wanted to spread the word that Android Go still exists. Honestly, considering the world RAM crisis, we might actually see more devices on the horizon that utilize Android Go. What're your thoughts?

This year I'm finally putting into action something that I've been wanting to do for some time: fortifying my home's network, improving privacy for my father and me, and laying the foundation for a smart home. (You guys took the time to help me out with that here, which, btw, thanks again!)

The network and privacy fortification is well underway and working. I set up Pi-hole with Unbound on one of my Raspberry Pis that also acts as a Tailscale exit node, got a new router that can connect my devices to ProtonVPN, have my Synology server working as storage, and... you know what, let's save this for another post. I'm still figuring some things out and want to let the dust settle first.

Anyway, back to gaming and PC'ing.

I'm no stranger to Linux; I've been using it on and off for over a decade on older PCs. But I've never committed to it on my main rig. As I said in another post, "It's the little things that make me not jump to Linux". While "these little things" didn't completely go away, I guess rolling up my sleeves to reconfigure my network, becoming more privacy-conscious, and reading about the ongoing issues with Windows 11 tipped the scales.

I debated between EndeavourOS and Fedora KDE. Fedora won.

EOS is a solid choice and I'd recommend it to anyone who wants to try out an Arch-based distro. But Fedora is undeniably more popular, which means if there's a Linux app, it's almost guaranteed the devs will have a Fedora version with dedicated documentation and installation commands. In other words, the potential for more convenience won out.

And convenient it was, mostly thanks to this website: https://nattdf.streamlit.app/. It helped a ton. It installed codecs, SSH, enabled Flathub and RPM Fusion, etc. It even provides a script to install Nvidia drivers.

But drivers weren't my real worry. My real worry was something else entirely.

You see, I lied to you guys by omission. I actually tried to install Fedora a few months ago, but I had severe issues with my TV. My PC is connected to both a monitor and a TV. The monitor worked without problems, but the TV was a different story. The image quality was terrible. You know those photos taken with the very first camera phones? That's how the colors looked. I remember trying everything: switching to X11, installing different driver versions, messing around with Nvidia settings, display settings, color profiles, even the TV's internal settings. Nothing worked. So I gave up and went back to Windows.

But today, while trying to fix an issue with my TV, I noticed two things:

1. I found out that my TV's HDMI ports are not all equal. Port 4 is HDMI 2.1, while all the others are 2.0.
2. My PC was connected to Port 3.

This was the problem. It's what caused my Windows to randomly lose sound, and it's what made the image quality terrible on Fedora, and it's what caused issues I mentioned in my old post. I don't know how or why Windows could "deal with it" and output 4K 120Hz without apparent image quality loss, but somehow it did.

Regardless, after moving the cable to Port 4, installing Fedora, and getting the drivers running... it works just fine and dandy. Great image quality, 4K, and 120Hz. My PC still works flawlessly as a gaming machine.

The moral of the story? Don't be like me. Before blaming Wayland, Nvidia, drivers, or Linux... check the back of the TV.

This also brings a much-needed sense of standardization to my setup. Now that everything is under the same Linux umbrella, I can manage it all via SSH with total consistency. I’m already eyeing my Raspberry Pi’s Telegram bot as a way to remotely wake the PC for heavy tasks and shut it down afterward. The potential of this setup has me feeling pretty euphoric.

Now that the biggest hurdle is cleared, Steam is running perfectly and Proton is handling my game library like a champ. I'm finally daily-driving Linux on my main rig, and this time, I think it's for good.