windows is ass. i use only linux now.

Hi guys. I dunno if any of you use MacOS but it's fuckin stupid and if you ever click the share icon, it only gives you options to share to/from Mac products. I don't use any Mac products other than MacOS. There's literally no way to just copy a link from the share button. If I just copy the link from the URL bar and send it to someone it will say "mismatching instance" (whatever that means) with no way to resolve it.

I'd like a way to share posts to people not on the threadiverse, but with the Photon frontend, so that it looks less shitty. How would one do that?

Maybe I'm just out of touch, but I don't understand who this is for, and I think it's going to flop.

First of all...who is asking for thinner phones?

Secondly, the price. This is not an Air SE. This thing is only $100 less than a full-fat iPhone Pro, and $200 more than iPhone base (which is a particularly good value this year).

And what do you get for that price?

• 2 fewer lenses than the pro, and 1 fewer than the base
• Titanium frame, I guess?
• Less powerful processor than the base
• Inherently more fragile frame
• Less battery life than even the base model (this was often cited as the shortcoming of the iphone Mini)
• Slower charging speed than both models
• no cinematic video mode

Are people really clamoring for thinner phones so badly that they'll spend more money for less features?

https://www.apple.com/iphone/compare/?modelList=iphone-17-pro%2Ciphone-air%2Ciphone-17

Edit: 1 week later and the Air underperforms the base model as well (as expected)

Also someone pointed out below that the 16e is only 2 grams heavier and is $400 cheaper.

In the past, if you broke or lost your phone, your Signal message history was gone. This has been a challenge for people whose most important conversations happen on Signal. Think family photos, sweet messages, important documents, or anything else you don’t want to lose forever. This explains why the most common feature request has been backups; a way for people to get Signal messages back even if their phone is lost or damaged.

After careful design and development, we are now starting to roll out secure backups, an opt-in feature. This first phase is available in the latest beta release for Android. This will let us further test this feature in a limited setting, before it rolls out to iOS and Desktop in the near future.

Here, we’ll outline the basics of secure backups and provide a high-level overview about how they work and how we built a system that allows you to recover your Signal conversations while maintaining the highest bar for privacy and security.

Secure Backups 101

Secure backups let you save an archive of your Signal conversations in a privacy-preserving form, refreshed every day; giving you the ability to restore your chats even if you lose access to your phone. Signal’s secure backups are opt-in and, of course, end-to-end encrypted. So if you don’t want to create a secure backup archive of your Signal messages and media, you never have to use the feature.

If you do decide to opt in to secure backups, you’ll be able to securely back up all of your text messages and the last 45 days’ worth of media for free.

If you want to back up your media history beyond 45 days, as well as your message history, we also offer a paid subscription plan for US$1.99 per month.

This is the first time we’ve offered a paid feature. The reason we’re doing this is simple: media requires a lot of storage, and storing and transferring large amounts of data is expensive. As a nonprofit that refuses to collect or sell your data, Signal needs to cover those costs differently than other tech organizations that offer similar products but support themselves by selling ads and monetizing data.

Anatomy of Secure Backups: Privacy First, Always

At Signal, our commitment to privacy informs which features we build and the ways that we build them.

Using the same zero-knowledge technology that enables Signal groups to work without revealing intimate metadata, backup archives are stored without a direct link to a specific backup payment or Signal user account.

At the core of secure backups is a 64-character recovery key that is generated on your device. This key is yours and yours alone; it is never shared with Signal’s servers. Your recovery key is the only way to “unlock” your backup when you need to restore access to your messages. Losing it means losing access to your backup permanently, and Signal cannot help you recover it. You can generate a new key if you choose. We recommend storing this key securely (writing it down in a notebook or a secure password manager, for example).

These choices are part and parcel of Signal’s guiding mission to collect as close to no data as possible, and to make sure that any information that is required to make Signal robust and usable cannot be tied back to the people who depend on Signal. This is why wherever there’s a choice between security and any other objective, we’ve prioritized security.

Enabling Secure Backups

If you want to opt in to secure backups, you can do so from your Signal Settings menu. For now, only people running the latest beta version of Signal on Android will be able to opt in. But soon, we’ll be rolling this feature out across all platforms.

Once you’ve enabled secure backups, your device will automatically create a fresh secure backup archive every day, replacing the previous day’s archive. Only you can decrypt your backup archive, which will allow you to restore your message database (excluding view-once messages and messages scheduled to disappear within the next 24 hours). Because your secure backup archive is refreshed daily, anything you deleted in the past 24 hours, or any messages set to disappear are removed from the latest daily secure backup archive, as you intended.

Backing up, moving forward

We’re excited to introduce secure backups, making sure you can retain access to your Signal messages even when your phone is lost or destroyed. But secure backups aren’t the end of the road.

The technology that underpins this initial version of secure backups will also serve as the foundation for more secure backup options in the near future. Our future plans include letting you save a secure backup archive to the location of your choosing, alongside features that let you transfer your encrypted message history between Android, iOS, and Desktop devices.

Secure backups are available in today’s Android beta release. A full public release, along with iOS and Desktop support, is coming soon.

E: apparently it needs to be said that I am not suggesting you switch to Linux on your phone today; just that development needs to accelerate. Please don't be one of the 34 people that replied to tell me Linux is not ready.

Android has always been a fairly open platform, especially if you were deliberate about getting it that way, but we've seen in recent months an extremely rapid devolution of the Android ecosystem:

1. The closing of development of an increasing number of components in AOSP.
2. Samsung, Xiaomi and OnePlus have removed the option of bootloader unlocking on all of their devices. I suspect Google is not far behind.
3. Google implementing Play Integrity API and encouraging developers to implement it, which prevents apps from the Google Play Store from being downloaded without a system-wide OS-level account login. Notably the EU's own identity verification wallet requires this, in stark contrast to their own laws and policies, despite the protest of hundreds on Github.
4. And finally, the mandatory implementation of developer verification across Android systems. Yes, if you're running a 3rd-party OS like GOS you won't be directly affected by this, but it will impact 99.9% of devices, and I foresee many open source developers just opting out of developing apps for Android entirely as a result. We've already seen SyncThing simply discontinue development for this reason, citing issues with Google Play Store. They've also repeatedly denied updates for NextCloud with no explanation, only restoring it after mass outcry. And we've already seen Google targeting any software intended to circumvent ads, labeling them in the system as "dangerous" and "untrusted". This will most certainly carry into their new "verification" system.

Google once competed with Apple for customers. But in a world where Google walks away from the biggest antitrust trial since 1998 with yet another slap on the wrist, competition is dead, and Google is taking notes from Apple about what they can legally get away with.

Android as we know it is dead. And/or will be dead very soon. We need an open replacement.

E2: thank you to everyone stopping by from Hacker News, Reddit, etc. to check out the threadiverse. I hope you'll stick around for a while. Check out https://phtn.app/ and the Voyager and Blorp apps for a nicer UI. Fuck Spez!

tl;dw their performance numbers don't match up to what we've seen in the past. Some pretty significant decreases in performance over Windows. I think there's clearly some sort of configuration error there. They also ran into the old dual-boot problem where Windows overwrites the Linux partition.

In my opinion this is lazy and irresponsible reporting. I don't at all mean to discount his experience, they are legitimate concerns, and it's fine to show the struggles of using Linux, but it's very clear he (admittedly) doesn't know what he's doing, and they need to consult an expert (or even a casual user) to figure out what the problem is before reporting. He said in the last video that Bazzite reached out to him to let them know if he has any problems so they could help but he obviously did not do that. As is, it just makes Linux/Bazzite look bad.

I hope he follows up with another video discussing the solutions.

What do you think?

Hi all, big fan of Bazzite and have it installed on several of my devices.

I just picked up a new (to me) laptop. This laptop has an 8845HS APU w/ 780M iGPU and also a NVDA 3050 6GB dGPU.

Using this laptop in desktop mode works perfectly fine. However, I reallllly want to use gaming mode, which, upon initial installation works just fine, but after reboot it opens to a black screen.

Now the Bazzite website says:

Some devices with two AMD GPUs (iGPU and dGPU) cause gamescope to be unable to detect your display resulting in a black screen. If you are affected, use an image without Steam Gaming Mode or disable your iGPU.

Obviously neither of those suggestions are ideal...

I assume this also applies to AMD iGPU + NVDA dGPU.

However the issue they link to in the above message pertains to several Framework 16 users. And if you select the Framework version of Bazzite, you get this message:

Enjoy enhanced dGPU support on the Framework 16…Applications like Steam and Lutris are automatically configured to run on your dGPU for optimal performance…Be sure to select Steam Gaming Mode for the ultimate console-like gaming experience

Implying that there's no problem with hybrid GPUs? So is there a fix somewhere they're not pushing to other versions? Or is this a hardware issue I'll never be able to overcome? Should I try and install the Framework version?

I posted this on the Bazzite Discourse forum but honestly it seems dead as hell over there.

Currently I'm using Nobara and using NVDA on desktop and AMD in Game Mode but that's obviously not ideal and Nobara doesn't ship with Game Mode + GNOME and honestly I really don't like KDE. 😬

Can't see my comment history... Using phtn.app

Hardware: 27" 2017 iMac

Connection: Wired

Storage: 1TB SSD

Hi all. I installed Linux Mint on my Mac on an external drive, which was all good fun. But when I went back to boot into MacOS, I got the 🚫 symbol. Booting into recovery mode and running first aid revealed that the disk was corrupted. The only advice it gave was to run first aid in recovery mode, which I was already doing.

Whatever, no big deal, everything important was backed up. So I went ahead and erased the disk using Extended Journaled (I guess APFS is unavailable for Sierra, which is what recovery mode wants to install). I made an installer disk with a later OS but I just received 🚫 again upon selection. Ran first aid again and it passed. Backed out of disk manager and selected install MacOS. Then after about 3 mins. received the error "an error occurred while preparing the installation. Try running this application again". Tried several more times, receiving the same error every time.

The log reveals even more errors including:

• "Could not find package ref in any source for:" 15 times for different packages such as "base system resources", "essentials", "OSInstall" etc.
• No native mechanism to verify InstallESD.dmg
• Couldn't mount base system dmg! (error code 110)
• IATOOL: Failed the mount outer dmg

I have installed MacOS several times before, including on the same device.

I have an exclusive gaming PC. Ideally what I'd like to do is shove it in a closet or other vacant room to contain the heat and then stream games over LAN.

The problem with existing solutions is:

1. They need a monitor connected
2. The monitor to be powered on
3. They don't support varying refresh rates/resolutions. Only whatever is displayed on the connected monitor. I want to play on my 4k/60Hz TV in the living room for AAA visual spectacle games that work best with controller, and the 1440p/120Hz display in my office for FPS or otherwise fast-moving games that demand KBM, and the 5k monitor for photo/video editing.
4. I haven't had much success getting these working at all. Red screens, 1/4 screens, image noise, etc.

They're literally just mirroring the screen of the connected display.

I really don't want to have to buy a dedicated PC for each use-case. Does a solution like this exist? What are their pros and cons? Preferably something that doesn't require a degree in software engineering.

Currently I am using Bazzite OS with 5700x + 6800xt, if that matters.

E: I AM NOT USING FEDORA. Please stop linking to guides for Fedora. They will not work. uBlue/Bazzite does not use dnf.

I got a free iMac. Installed Linux on an external drive. Bazzite, specifically. WiFi does not work. My research leads me to a problem with proprietary Broadcom drivers but no solutions. If you know how to get this working, your advice would be appreciated.

Also if there's another distro that works "out of the box" on Macs with GNOME I'd be open to installing that as well.

E: "System information" says it is a

Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1772.1)