orowith2os

@orowith2os@tech.lgbt

:QueerCat_Lesbian:, she/they

#GNOME, #Fedora, and #Flatpak

Fill out your profile before following.

Interested in all things #FreeDesktop and #Wayland

Learning #Rust / #rustlang at this very moment!

I maintain:
The #ArmCord Flatpak
The #Inochi2D Flatpak(s)
The vpuppr Flatpak
the (experimental) asahi/mesa flatpak
some Flatpak modules on #Flathub

if you couldn't tell i like Flatpak

Matrix: https://tech.lgbt/@orowith2os:tchncs.de

Searchable via tootfinder (https://tootfinder.ch/)

This profile is from a federated server and may be incomplete. Browse more on the original instance.

orowith2os, to random

Well, I think I'm making more progress towards understanding what makes me tick.

And all it took was scoring an 11 on the PHQ-9.

Going to take a while to find a decent therapist (there are a lot of "christian" ones), but progress.

If all goes well, I at least won't feel like shit.

orowith2os,

on an unrelated topic, made tons of progress on Flathub stuff. Just added a generic gamescope extension (https://github.com/flathub/flathub/pull/4329) and I've been updating a ton of apps for the change.

I'm going to document how to use qemu-user-static/binfmt_misc to run non-native binaries on your system with Flatpak too, in the hopes that it improves the UX for e.g. Asahi Linux users.

I'm also going to try and work on an add_path extension argument for Flatpak: https://github.com/flatpak/flatpak/pull/5482

orowith2os, to random

used to be the guy that got straight As, now I'm neither straight nor a guy :ablobfoxbongo:​

orowith2os, to fedora

folks, any of yall have some decent guides on getting Silverblue going on a 4?

The official Fedora docs are either a) iffy, b) assume you're using Workstation, or c) badly designed and hard to understand

I'm considering just using Workstation with how annoying this is. Everything ARM-related is so fragmented and hard to set up....

orowith2os, to Texas

Let's do this again! My name is Dallas, but I prefer being called Oro - still iffy on my name. Do give suggestions if you want to, though.

I'm a (pretty queer) developer from southeast #Texas, USA. A few(!) years ago I installed (Arch) Linux, and that started my whole Linux journey. From there, I started to learn #Flatpak, and got pretty intimate with Linux. After my Arch install failed again, I finally installed #Fedora, and after that broke I went to Silverblue and have been comfortably developing using it for one year now.

I've been learning how to program, and am somewhat familiar with #Rust. Now I've rewritten some xdg-utils, and am looking at learning how to build a web utility using it.

Maybe you've seen me around - I'm working on some Portal stuff (https://github.com/flatpak/xdg-desktop-portal/pull/996), I maintain a few Flatpaks, and am learning how to build and utilize vtuber applications such as #Inochi2D.

Oh, and I did this. We don't talk about this. https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/6161

#Linux #FOSS #GNOME #introduction #rustlang

orowith2os, to random

It's sad to see a FOSS project look to add (user-controlled!) telemetry and the first thing the community says is "what, so a corporation can mine our data?"

Not all telemetry is bad. Our view of it is just tainted because of its abuse by companies.

Strip personal information, ask the user, and aggregate it.

It's genuinely useful information for developers to have. It's far easier to get information on bugs like this than it is to wait on an issue tracker. You can also see what most people are interested in - performance, workflow, features, etc.

orowith2os,

@wolf480pl

You can't reliably figure out what the users want (or don't want) without using telemetry. If you don't, and all you do is rely on them to go into surveys and issue trackers on completely foreign platforms, they get confused and might not give enough needed information.

You can view crash logs, performance metrics, and certain features used with telemetry, and it's far more reliable than opt-in surveys where the user probably doesn't even know where to respond.

Don't use telemetry and you end up orienting your app towards a VERY SMALL subset of the users of your app.

alatiera, to GNOME
@alatiera@mastodon.social avatar

Rejoice, GNOME 45 Alpha release is out

Play with it at https://os.gnome.org

https://discourse.gnome.org/t/gnome-45-alpha-released/16087

#gnome #linux

orowith2os,

@alatiera going to see if Fedora Rawhide has it, will rebase ASAP :)

orowith2os, to rust

Anybody with a bit of experience in #libadwaita UI design that wants to help out?

I want to start an equivalent to Tweaks from scratch, all I need is someone that can handle making the UI. There's been some efforts upstream, but it hasn't been active for a while, and I think it's better to just start from scratch.

I'll be using #Rust, and may look at potentially managing several GNOME versions (and maybe even some third-party GNOME stuff, like #Budgie and #Pantheon configs, assuming there's enough overlap)

This is going to be a bit cursed, especially since Tweaks isn't all that clean, but it would be better than nothing.

#GNOME #FOSS #GNOMETweaks #GTK #rustlang

orowith2os,

@gregorni Don't worry, I'll handle the logic and whatnot, ideally all you'd be doing is putting together the UI!

I'll send you a Matrix DM, it's a bit late here so will talk more in the afternoon :)

gamingonlinux, to random
@gamingonlinux@mastodon.social avatar

Today is a day of problems huh. I love Flatpaks but what am I supposed to do with 8 of this same error?

orowith2os,

@gamingonlinux it's a known issue, downgrading libostree should fix it for now

orowith2os, to rust

I heckin did it

I heckin built Rust (1.39) from source

without rustc

no ocaml fuckery or whatever

and all it cost my was my sanity, sleep, and 10 hours of my time

all for a "cargo 1.39.0"

oh I also had to fuck around and find out with openssl-1.1

I hECKIN DID iT

#Rust #mrustc #rustlang #openssl

geerlingguy, to random
@geerlingguy@mastodon.social avatar

Dear Red Hat:

are you dumb?

https://www.redhat.com/en/blog/furthering-evolution-centos-stream

I am seriously considering dropping support for all RHEL/Fedora on all my Ansible work.

orowith2os,

@geerlingguy @peotr26 @AudraTran

Still, unless there's a clear reason to stop supporting Fedora, there's no reason to punish them.

The target here is RHEL - not Fedora. If Fedora starts to feel the effects from RHEL, then I'd say consider dropping support for it. But not before.

inexcode, to random

I'm somewhat disappointed that Linux support of HDR and 10-bit color is almost nonexistent

orowith2os,

@kkarhan @inexcode

More info: HDR work is being done, but only for Wayland. Xorg's support for that is going to be nonexistent, especially considering the hellhole that is its codebase.

https://emersion.fr/blog/2023/hdr-hackfest-wrap-up/
https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/124
https://www.collabora.com/news-and-blog/blog/2020/11/19/developing-wayland-color-management-and-high-dynamic-range/
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2356

futurebird, to random
@futurebird@sauropods.win avatar

"cis is a slur" is some next level, roided-up ultra-erasure.

It's also very Newspeak. Double plus Newspeak. Delete the language that describes the concept to delete the concept.

It's funny, but it's also very very bad. Pure eliminationism.

orowith2os,

@futurebird @wagesj45

you got me thinking now

it's really fucking stupid, but if "cis" means "same" or "stay" here, you could do some really funky stuff

"transportation" and "cisportation", for example

foone, to random
@foone@digipres.club avatar

I'm going back and rewriting my Bundle Parsing code now that I have the DWARF data properly dumped. Mainly just renaming stuff like "third_part" and "size_maybe" to "nResLocsOffset" and "nSizeAndCompression"

orowith2os,

@foone hold the fuck up I need to try this out

orowith2os, to fediverse

Calling the wider #Fediverse !

I'd like all of your thoughts regarding companies such as #Meta attempting to join Fedi. Anything and everything is good.

What about #decentralization and the future of the web? User #freedom ? #FOSS ? Open standards?

Can we maintain a web where everybody has their own instances of social media, tailored to their own specific use cases?

How about the user experience? Privacy? Can we manage user-respecting #telemetry with the fediverse and put it to use?

To sum it up: give me all of your thoughts on a #corporate web. Don't hold back, everything I listed here are just guidelines for what to respond with ;)

Spread this far and wide! I'm composing everything into one document (article), and will give proper attribution to everyone who's information I use.

Mark your replies as "mentioned people only" if you'd like to keep yourself anonymous, and I'll just use the information you gave me.

#Mastodon #Facebook #Instagram #Twitter #Reddit

orowith2os,

@tchambers @DrPen also keep in mind that you're not limited to what I asked for on the OG post!

If you've got anything to say related to the web, anything at all, I'd love to hear it. No need to restrict yourself to what I've asked for.

orowith2os, to linux

My first public article/blog post:

Flatpak - an insecurity nightmare

https://orowith2os.gitlab.io/posts/Flatpak-an-insecurity-nightmare/

Thanks to @TheEvilSkeleton for reading over it :)

orowith2os, to linux

You don't hate Flatpak.

You hate the fact that developers don't need to track down 10 times more bugs, at the minimum.

You hate the fact that developers don't need to rely on other people to package and ship their software to end users.

You hate the fact that developers don't need to support at least four different environments, all with different libraries and versions.

You hate the fact that developers don't have to deal with the bullshit that's been plaguing the Linux desktop for the past 20 years.

You hate the fact that developers can feasibly ship their software to end users in such a way that it's sustainable for the long term.

You hate the fact that developers are less stressed and can put more time into making their software better.

If you reply to this with something like "but mah CLI app support", "but mah storage", "but mah 5 FPS", or "but some stuff breaks" then read my replies to similar comments here, or consider that everyone has room for improvement.

#Flatpak #Linux #Flathub

devinprater, to accessibility

So y'all remember that post that I shared from someone who has used Linux nearly their whole lives, and posted why they've given up on GUI and all? This came from years of their own experiences. They got into Linux much more than me, and even compiled their own kernel. Well, this looks like a member of the Gnome Foundation's response to their thread. No, I'm not going to link the blind person here because they don't need anymore bullshit from fossbros. I mean, calling their heart-felt posts a "trauma dump", and that they're "making up shit on the spot", isn't it time that we've had enough of these ableist people? Developers who are indifferent to people with disabilities will definitely see this, and the Gnome folks probably see this kind of talk all the time, that "we can't do this," or "We don't have the time or money," and that kind of talk makes itself true. Accessibility will not move forward with this kind of mentality at the head of one of the most popular Linux desktops. Can we get a little solidarity here? This Gnome foundation person is attacking a blind, nonbinary, Gendervoid person, and I'm sick of this shit going unnoticed. I want you Linux users to think about this. Think about the people who sit there in power. It doesn't take all kinds of people to make a community. Some people aren't just "a little rough around the edges." We need a community of empathetic people that do not punch down.

https://mastodon.social/@ebassi/110517100226754030

#accessibility #foss #blind #gnome #Linux

orowith2os,

@x0 @fireborn @devinprater this is taking it too far, too fast. One GNOME developer being an ass doesn't mean all of them are.

orowith2os,

@fireborn @x0 @devinprater as it was stated in the post, a11y has been degrading in the Linux stack for decades already. It's due a major rework, but there's nobody there to back it up.

If you want to make a change, look at funding development efforts for a11y. Don't go right to suing someone.

I am not denying that some GNOME developers are, and have been, assholes, just that this is not the way to deal with them.

devinprater, to accessibility

Oh lookie:

5.1.11. GNOME has reduced accessibility support for screen readers
Many GNOME apps have switched from the GTK3 graphics toolkit to GTK4. Sadly, this has made many apps much less usable with screen readers such as orca.
If you depend on a screen reader you should consider switching to a different desktop such as Mate, which has better accessibility support. You can do this by installing the mate-desktop-environment package. Information about how to use Orca under Mate is available at here.

https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html

#accessibility #foss #debian #blind #gnome

orowith2os,

@ArneBab @z428 @anna @devinprater The issue with keeping compatibility with all the previous tooling is that that tooling was made with X in mind, not Wayland. You can't help breaking compatibility with tools then, but at least for most apps Xwayland is relevant for the time being. This goes regardless of if your tools are for a11y or general desktop users.

Apparently Red Hat is looking into improving the a11y stack massively, so definitely looking forward to that. Should fix a ton of issues people have now.

orowith2os,

@ArneBab @z428 @anna @devinprater Xorg handles a lot, but a11y isn't one of them. There are dedicated interfaces for that, which toolkits already support. Some just don't support it well enough.

The reason some tools work only on Xorg is because of how insecure it is, which I want to say is somewhat solved by the standard a11y interface, but I can't be sure.

And no, expecting others to clean up the mess from Wayland breakages is the right thing to do. A Wayland compositor has no business handling fonts and rendering interfaces for applicaitons, but Xorg does that, and some applications rely on that functionality.

orowith2os,

@ArneBab @z428 @anna @devinprater

You can't reasonably expect Wayland to keep perfect compatibility with all Xorg applications, the two are too different and Xorg is too much of a hell. The reason Wayland exists in the first place is to replace Xorg, it knows full well what not to do. It's not like this is a normal thing though, Xorg had its 30 years. Now it's Wayland's turn.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • JUstTest
  • mdbf
  • ngwrru68w68
  • cubers
  • magazineikmin
  • thenastyranch
  • rosin
  • khanakhh
  • InstantRegret
  • Youngstown
  • slotface
  • Durango
  • kavyap
  • DreamBathrooms
  • megavids
  • tacticalgear
  • osvaldo12
  • normalnudes
  • tester
  • cisconetworking
  • everett
  • GTA5RPClips
  • ethstaker
  • anitta
  • Leos
  • provamag3
  • modclub
  • lostlight
  • All magazines
    •