Not Everyone Wants the Spotlight

Bluesky just handed its users a quiet little superpower: the ability to disappear from the algorithmic crowd.

On Thursday, the open social network rolled out an algorithmic opt-out feature that stops your posts from surfacing in the main Discover feed. It arrived less than 24 hours after Bluesky added support for longer videos — a busy week for the team.

The Discover feed, for the uninitiated, can currently pull in just about any public post on the network. Bluesky posts are public by default, which means a stray thought can suddenly find itself in front of thousands of strangers. Not everyone wants that.

What This Feature Actually Does (and Doesn’t Do)

Let’s clear up a common misconception right away. This is not a privacy toggle. Your posts remain public, and anyone with a link can still see them. Bluesky is still building private data support at the protocol level — that’s a separate project.

What the opt-out does is make your posts less discoverable to people outside your existing circle. It’s a visibility dial, not a lock.

The company says it built this because some people just want to post for their followers. They don’t want their words amplified to a larger crowd. They don’t want to go viral. Simple as that.

How to Turn It On

If you’re ready to step out of the algorithmic spotlight, here’s what to do:

1. Open the Bluesky app on your device.
2. Head to Settings, then Privacy and Security.
3. Toggle on the new option to stop your posts from appearing in Discover.

One small caveat: the change can take up to an hour to fully take effect. So if you flip the switch and immediately check the Discover feed, you might still spot your post lingering there. Patience is key.

An Account-Level Setting That Travels With You

Here’s where Bluesky’s implementation gets interesting. This isn’t just a setting that lives inside the Bluesky app. The preference is recorded at the account level, which means it travels with you across the AT Proto ecosystem.

Let’s say you post from another app built on the same underlying protocol — something like a third-party client or a custom feed tool. That app will see your preference and know you’ve opted out.

But here’s the catch: those other apps have access to the information, yet they still have to choose whether to respect it. Bluesky is essentially setting a standard and hoping the ecosystem follows along. The protocol can carry the message, but it can’t force compliance.

Why This Matters for the Fediverse-Style Future

Bluesky’s approach is a small but meaningful step toward user agency in social media. The company is betting that people want more control over how their content flows, not just what they see.

It’s a different philosophy from the algorithmic giants that dominate the space. On platforms like X or Instagram, the algorithm decides who sees what, and users have little say in the matter. Bluesky is flipping that script, at least partially.

This also raises a broader question: if the AT Proto ecosystem grows, will other apps honor these preferences? The protocol can encode the intent, but enforcement is another matter entirely. It’s a test of whether decentralized social media can actually deliver on its promises.

The Bigger Picture: Slowing Down the Virality Machine

The Bluesky social network has been on a roll lately, adding features at a brisk pace. Longer videos yesterday, algorithmic opt-out today. The company seems intent on building a platform that feels less like a popularity contest and more like a community.

For those who’ve been burned by viral moments they never asked for, this feature is a welcome reprieve. It’s a recognition that not everyone wants the same experience — some people are chasing reach, while others just want to talk to their friends.

Bluesky’s privacy and safety tools are clearly evolving, and this latest addition shows the team is listening to the quieter voices in its user base. The question now is whether the rest of the ecosystem will follow suit.

One thing’s for sure: the opt-out won’t stop you from going viral on other platforms. But on Bluesky, at least, you now have a say in the matter. That’s more than most social networks offer.

If you’re setting up a database-backed application on Linux, the first hurdle is often getting MySQL running smoothly. The good news? A new tutorial from LinuxHint walks you through the entire process on the latest Ubuntu 26.04 LTS, covering installation, security hardening, and database creation. It’s a practical, no-nonsense guide that saves you from scouring forums for hours.

In this article, we’ll break down what the video teaches, why each step matters, and how you can apply these skills immediately—whether you’re a developer, sysadmin, or just starting your Linux journey.

Why This MySQL on Ubuntu Tutorial Stands Out

Many guides assume prior knowledge, but this one starts from scratch. The instructor begins with a fresh Ubuntu 26.04 LTS system and runs `sudo apt update` to refresh package lists—a simple yet critical step. Then, it’s straight into `sudo apt install mysql-server`, which pulls in MySQL 8.4, the latest stable version.

What makes this tutorial particularly effective is its focus on verification. After installation, you’re shown how to check the service status with `sudo systemctl status mysql`. This isn’t just a box-ticking exercise; it ensures your database server is actually running before you move forward. As a result, you avoid the common pitfall of assuming everything works when it doesn’t.

Building on this, the video emphasizes security from the get-go. Running `sudo mysql_secure_installation` right after installation is a best practice that many beginners overlook. The script prompts you to set a root password, remove anonymous users, and disable remote root login—all essential for a production-ready setup.

Step-by-Step: Securing and Accessing MySQL

Once MySQL is installed and running, the tutorial dives into the security script. This interactive tool asks a series of yes/no questions, and the video clearly explains each one. For instance, you’ll be asked whether to remove test databases—a wise choice for security. The instructor doesn’t just click through; he explains why each option matters, turning a routine task into a learning opportunity.

After securing the installation, the next step is accessing the MySQL shell. The command `sudo mysql` logs you in as root, but here’s a crucial tip: on Ubuntu, root uses the system’s auth socket by default, so no password is needed at this stage. This can confuse newcomers, but the video clarifies it perfectly.

Inside the shell, you’ll learn to create a dedicated database and user—essential for isolating your applications. The commands are straightforward:

– `CREATE DATABASE linuxhint_db;`
– `CREATE USER ‘linuxhint’@’localhost’ IDENTIFIED BY ‘your_secure_password’;`
– `GRANT ALL PRIVILEGES ON linuxhint_db.* TO ‘linuxhint’@’localhost’;`

Each command is explained, and the video shows the expected output, so you know exactly what to look for. This hands-on approach is ideal for visual learners.

Creating Databases and Users: Practical Skills for Real Projects

Why create a dedicated user instead of using root? The video addresses this head-on. By granting privileges only on a specific database, you minimize risk. If an application is compromised, the attacker can’t access other databases or system tables. This principle of least privilege is a cornerstone of database security, and the tutorial drives it home with a real example.

Moreover, the instructor demonstrates how to verify your work—using `SHOW DATABASES;` and `SELECT user FROM mysql.user;` to confirm everything is in place. These small checks build confidence and reinforce good habits.

For those who prefer written documentation, the video description links to a complete guide on LinuxHint. That’s a thoughtful touch, as some viewers like to follow along in text while watching.

Who Should Watch This MySQL Installation Tutorial?

This tutorial is perfect for a wide audience. Linux beginners will appreciate the clear, step-by-step instructions. Developers will find it a quick refresher for setting up local environments. System administrators can use it as a reference for deploying MySQL on servers. Even students studying databases will benefit from the practical, hands-on approach.

Furthermore, the video is part of a broader series from LinuxHint, which regularly posts Linux, Bash, and DevOps content. If you enjoy this style, subscribing is a no-brainer—you’ll get weekly updates on similar topics.

Final Thoughts: Get MySQL Running Today

Installing MySQL on Ubuntu doesn’t have to be intimidating. With the right guidance, you can have a secure, configured database server in under ten minutes. This tutorial distills the process into clear, actionable steps, and its emphasis on security sets it apart from older guides.

Therefore, if you’re ready to take control of your database setup, watch the full video below. Whether you’re preparing a production server or just experimenting on your laptop, you’ll walk away with the skills to get MySQL up and running—and keep it secure.

Don’t forget to check out the free Linux Mastery PDF linked in the description for more foundational knowledge. And if you found this helpful, hit subscribe and turn on the bell so you never miss another practical tutorial.

Watch the video now and transform your Ubuntu system into a database powerhouse.

If you’ve been battling the dreaded “An Unreal process has crashed: UE-MARVEL” error in Marvel Rivals, you know how frustrating it can be. You’ve tried verifying game files, updating drivers, and tweaking settings—yet the crash persists. But here’s the thing: the culprit might not be the game itself. It could be your PC’s GPU selection.

A growing number of players have discovered that Marvel Rivals sometimes defaults to the integrated graphics chip instead of your powerful dedicated GPU, especially on laptops and desktops with hybrid graphics. This mismatch triggers instability, random freezes, and those infamous Unreal Engine crashes. Fortunately, a new, community-confirmed method is making the rounds—and it’s surprisingly simple to implement.

In this guide, we’ll walk you through the exact steps to force Marvel Rivals to use your dedicated NVIDIA or AMD GPU, based on the latest 2026 troubleshooting video from Windows Fixer. You’ll also learn how to disable integrated graphics safely, whether via Windows settings, Device Manager, or even your BIOS. Let’s dive in.

Why Marvel Rivals Crash Fixes Often Fail

Before we jump into the solutions, it’s worth understanding why so many standard fixes don’t work. Most crash guides focus on game files, overlays, or RAM—but they ignore the GPU selection issue. Windows often assigns Marvel Rivals to the integrated GPU (like Intel UHD) to save power, even when a beefier card is available. This mismatch leads to memory pressure, driver conflicts, and ultimately, the UE-MARVEL crash.

As a result, players see random crashes during matches, especially in intense moments. The solution? Force the game to use your dedicated GPU. This is the core of the Marvel Rivals crash fix we’re about to explore.

Method 1: Force Dedicated GPU via Windows Graphics Settings

The first—and easiest—approach is to use Windows’ built-in graphics settings. This works for both NVIDIA and AMD users and takes less than a minute.

1. Open **Settings** > **System** > **Display** > **Graphics**.
2. Find Marvel Rivals in the list (or click “Browse” to add it).
3. Click on the game, select **Options**, and choose **High performance**.
4. Save your changes and restart the game.

This tells Windows to prioritize your dedicated GPU for Marvel Rivals. Many users report immediate improvement after this simple tweak. It’s a critical step in any Marvel Rivals crash fix routine.

Method 2: Configure NVIDIA Control Panel for Marvel Rivals

If you have an NVIDIA GPU, you can also set the preferred processor directly in the NVIDIA Control Panel. This gives you more control and ensures the setting sticks.

1. Right-click your desktop and select **NVIDIA Control Panel**.
2. Go to **Manage 3D Settings** > **Program Settings**.
3. Select Marvel Rivals from the dropdown (or add it manually).
4. Under **Preferred graphics processor**, choose **High-performance NVIDIA processor**.
5. Click **Apply**.

As a result, Marvel Rivals will always use your dedicated GPU, bypassing the integrated chip entirely. This is particularly effective for laptops with hybrid graphics.

Method 3: Disable Integrated GPU via Device Manager

If the above methods don’t fully resolve the issue, you can disable the integrated GPU altogether. This forces your system to rely solely on the dedicated card. However, be cautious—this can affect your display if your monitor is connected to the integrated port.

1. Press **Win + X** and select **Device Manager**.
2. Expand **Display adapters**.
3. Right-click the integrated GPU (e.g., Intel UHD Graphics) and select **Disable device**.
4. Confirm the prompt and restart your PC.

Building on this, if you have a secondary monitor plugged into the integrated GPU’s port, it will stop working. In that case, connect all monitors to your dedicated GPU’s ports instead. This is a safe way to manage multi-monitor setups while applying the Marvel Rivals crash fix.

Method 4: Permanently Disable Integrated Graphics via BIOS

For advanced users, disabling the integrated GPU in the BIOS is the most permanent solution. This ensures Windows never even sees the integrated chip, eliminating any chance of Marvel Rivals using it.

1. Restart your PC and enter BIOS (usually by pressing **Del** or **F2** during boot).
2. Navigate to **Advanced** or **Integrated Peripherals**.
3. Find the option for **Integrated Graphics** or **iGPU** and set it to **Disabled**.
4. Save and exit.

However, proceed with caution. If your dedicated GPU fails or is removed, you’ll have no display output until you re-enable the integrated graphics. Therefore, only do this if you’re confident in your hardware setup.

Final Tips and Community Feedback

After applying these methods, test Marvel Rivals thoroughly. If crashes persist, check the video’s previous troubleshooting guides for other fixes like overlays or RAM settings. The creator emphasizes that community feedback is invaluable—so if this method worked for you, leave a comment to help others.

In conclusion, the UE-MARVEL crash is often a GPU selection issue, not a game bug. By forcing Marvel Rivals to use your dedicated GPU, you can eliminate most instability and enjoy smooth gameplay. Watch the full video below for step-by-step visuals and timestamps for each method. Don’t let crashes ruin your matches—take control today.