JoshStrobl

Just get some x86 and ARM runners off netcup, manage Woodpecker CI + Woodpecker Agent. Generally pretty hands-off once you get it set up. That plus a cheap VPS running Forgejo with postgres off-site backups, you are looking at a small fraction of the cost compared to per-seat GitHub pricing for orgs + Action Minutes.

So glad I moved my OSS org mostly over to a self-hosted Forgejo + Woodpecker CI. I get that we are operating on a completely different scale but I swear the GitHub outages are far too regular than they ought to be.

My experience mirrors this as well.

I was fully in on Cursor for a good chunk of last year, using Composer + Gemini Pro (via Copilot / GH integration). I really enjoyed Cursor's tab completion capabilities, but when Sonnet and Opus started getting particularly good for me (think for me it was around 4.5), I swapped over to Zed + claude code in the integrated terminal. I've found that after a bit, I haven't ended up missing the tab completion. I've been perfectly fine with just LSP + claude always open. I don't miss Cursor. All my colleagues are on claude code with half of us also using Zed.

That joke really went over your head, huh...

As far as I know, it's their own in-house solution (not fltk, gtk, qt, etc.)

WhatsApp works okay on my Jolla C2. Occasional annoyance with device detection (BT headphones) where it'll still end up outputting to speaker, but I haven't had that with any other Android app running via AppSupport like YouTube Music, so dunno if that's just WhatsApp being problematic.

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.

Same here, Helsinki Finland

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

Cure. Ordered a shirt and stickers. Looking forward to being able to rep Firefox!

Unless you have a specific reason to use Google Play Store (as in the app, not the distribution medium), I would highly recommend using Aurora Store (which you can handily get via F-droid). I use it on my Sailfish OS phone (C2) to similarly get apps not available via F-Droid.

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

I'm not aware of your circumstances, but at least here in Finland I was able to get (and the bank was required to provide at my request) a cheap 2FA token generator device that can be used instead of the app (Danske ID). It works whether I am confirming an online transaction or signing into a service that uses the Suomi.fi centralized login system.

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.

Or Fedora Budgie Atomic: https://fedoraproject.org/atomic-desktops/budgie/

File System API is a baseline feature supported across all major vendors. https://developer.mozilla.org/en-US/docs/Web/API/File_System...

Funny to see Onyx be mentioned in the wild! :D

Not sure why the post for Arch-specific item when we announced the temporary soft fork at https://buddiesofbudgie.org/blog/wayland, which will be used for X11 support while we build a wlroots-based compositor for Wayland

Please do an ortho or split ortho layout. I get that it'd be low volume but I'd be willing to pay a premium if it meant being able to keep my Helidox Corne at home while I travel or go into the office, without sacrificing ergonomics.

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

Meanwhile as an American living in Finland, I just wish I could have my directions in English, use Metric system, but have the names of streets and the like use the Finnish pronunciation. Instead it absolutely butchers the pronunciation almost beyond comprehension and gives me the streets in both Finnish and Swedish as further punishment.

I ended up putting this in my .gitconfig (global)

    [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"

So when I run git permission-reset, it sorts it out.

"Do I understand from a quick Google that you don't support Wayland (or at least Solus doesn't)? If you're using mutter you should presumably have the core of the capability available I believe?"

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.

Thank you for fixing the items raised, much appreciated! Regardless of what operating system you use Budgie under, glad you are enjoying the desktop experience :)

"but it's absolutely based on GNOME, the desktop stack. Just to clarify your clarification. :)"

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.

I can't really speak to any sort of timeout, but I have since reduced animation timings and tied the "disable animations" option into workspace switching as well (so there is zero transition in it, should you disable animations).

Long time lurker, had to create an account to post about this though. Hey folks!

"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.