Installed it from Aurora, an open source frontend to the Play Store.

Biggest pain-points for me with AppSupport is:

1. Lack of Bluetooth passthrough in a sane way (community workaround results in it being unavailable with host OS). 2. It does not report to apps that PIN entry is enabled, meaning some awful but important apps like Danske ID don't work.

Otherwise it does the job remarkably well. Still prefer native SFOS apps when available, however it is a small ecosystem and so depending on your usecase you may find yourself installing Android apps.

After attempt #4 at 1706 Europe/Helsinki, git push worked. So just keep trying.

https://f-droid.org/packages/com.aurora.store/

I requested it after they updated their Android app to have a check for pin-code enablement. Sailfish OS doesn't report it via the Android AppSupport system, so it was blocked before I grabbed an older build via Aurora and disabled it from updating. If it ever stops working, I'll only use the token. Once that stops working, I will switch banks.

Looking forward to purchasing the 16 regardless though. Keep up the amazing work / mission with Framework. Fantastic work to the team.

    [alias]
        permission-reset = "!git diff -p | grep -E \"^(diff|old mode|new mode)\" | sed -e \"s/^old/NEW/;s/^new/old/;s/^NEW/new/\" | git apply"

At this time, we do not support Wayland, that is correct. We leverage a fair few X11-specific APIs and include support for XEmbed-based system tray icons (you would have to pry system tray icons from my cold dead hands :D). Not saying it won't ever be supported, but that wouldn't be addressed until we move to our own window manager at the very least.

GNOME Shell is not the same as the rest of the stack.

"Budgie can't even comfortably coexist with GNOME Shell on the same OS installation"

Yes, it absolutely can. You can use GDM and log in to both.

"If you change your settings in GNOME Shell with the Settings app, it will affect your Budgie session."

It entirely depends on what settings you change. For displays, that generates the mutter related configurations which are used by Budgie because Budgie uses Mutter. Networking is related to NetworkManager and not GNOME. Notifications is something we intentionally hook into for filtering apps in Raven but can trivially be changed, we even have our own set of exclusions. Search doesn't apply to Budgie, that is specific to GNOME Shell. Applications is primarily oriented towards Flatpak. Most of the screen locker functionality isn't related because we use slick-greeter+lightdm+budgie-screensaver (a fork of gnome-screensaver).

Sound can be independently managed, we do that via Raven for example (which ties into Gvc). Power settings leverage a mix of gnome-related settings and upower. Mouse settings are primarily related to libinput. I could go on.

"Maybe you shouldn't say it's "based off of GNOME Shell", but it's probably accurate to say that Budgie is an alternative Shell for GNOME."

Not really. There are many settings we expose which are not related to GNOME or GNOME Shell at all.

"I even remember Solus devs at the time saying they might never actually do version 11 because they had fixed and worked around some of the issues that they thought they wouldn't be able to in 10.4(?)."

Yes and then Ikey, the project founder, let and I took over in late Budgie 10.4 and my first release was Budgie 10.5. I went back and fixed issues that previously were implied to only be fixable in Budgie 11.

"So, is Budgie 11 actually going to happen?"

Yes however it is not a priority over other aspects of Solus development.

"Budgie is based on GTK and the GNOME Shell."

To clarify, Budgie is NOT based on GNOME Shell. Budgie uses gnome-settings-daemon, GTK, and Mutter. It's written with GTK, C, and Vala, whereas GNOME Shell is written in C, St, and JavaScript. Budgie 11 isn't going to use any GNOME applications, its settings daemon, or Mutter. May not even use GTK (but rather EFL).

"originally developed for the distro called Solus"

It is still developed for Solus primarily.

"Another nice feature is the extensions that are baked into the Budgie Extras app, shipped together with the desktop."

This is part of the Ubuntu Budgie experience, not Budgie itself.

"These extensions are all developed by the maintainers of the desktop environment, so breakage is not really expected."

As the developer of Budgie, no these are not all developed by the maintainers. Many of them are developed by Ubuntu Budgie, whereas I use and develop on Solus. Breakage is to be expected and has occurred in the past, leading me to have to triage these issues filed against proper upstream rather than Ubuntu Budgie's extras repo.

"One of these extensions is a global menu that works wonderfully, and supports all my applications"

This is not one which is developed by us (Solus).

"The print screen keyboard shortcuts known from GNOME don't work by default"

Works under Solus.