Quack Doc

pretty much

sure thats portable, but you would need a lot of devices for that

this would be… somewhat possible, you can’t really boot GSI images, however the folk at BlissOS do have an android generic project that makes porting custom roms to x86 a lot easier. By porting android images to generic x86, we can serve them as temporary VMs, just like https://distrosea.com/ (I’ve actually been thinking about doing something like this for bliss specifically but funding says no lol).

This is contingent on roms being ported to x86 though, off the top of my head there are images floating around for

• Bliss (Obviously)
• Lineage OS,
• Vanilla AOSP,

and specific verisons of

• Project sakura (A11 iirc)
• CarbonROM A10
• Bootleggers A10
• RessurectionRemix
• Pixel Experience
• Dirty Unicorns
• Tesla

I believe there are also images of LMODroid and Calyx floating around… somewhere

specific parts. you need metal to withstand the pressures of the actual bullet to get a somewhat degree of reliability, so any pressure bearing part needs to be metal, everything else can be plastic, but the more metal the better. Now you can get some more basic designs with parts that you could fabricate at home, but a lot of the higher end designs require off the shelf gun parts.

The “leading design” right now is the FGC-9 which is actually seeing a degree of use in myanmar(??). The design requires metal parts that could be feasible to fabricate at home. However it is shockingly easy, even in heavily restricted countries, to be able to order the metal parts.

we already have them. It’s not hard to make a firearm, and the 3d printed weapons scene has taken off quite well. all of the good ones still need metal parts ofc, but they are pretty easy to get your hands on in many cases.

Edit: Accidentally thought it was a Glock at first, my bad.

Sig boys are seething

not enough guns, needs a rifle and a shotgun at least.

Yes, there are open source firearms. there is even 3d printed designs for an MP5 the youtube channel Print shoot repeat showcases a lot of them.

You can also try it using arch for anyone curious, I have pkgbuilds for most things here https://github.com/Quackdoc/pkgbuild-scripts/tree/Master/cosmic-epoch (dont try meta-git it breaks things) I havent clean room tested them but i’ve slowly been working on making sure the dependencies for everything are up to snuff but they arent all there yet

Does this mean we will finally be able to mark/search mobile/TV compatible apps? i remeber there being talk about that supported with appstream metadata

good to hear

can you try running ovmf? also try using IDE for boot, remeber to re-setup your boot order if you need to change that

this broke on my lemmy instance, can you upload to a pastebin or something? I only see a couple of characters

can you send your virt manager xml?

The issue with flat packs is the more you use it, the higher the chance that you get less shared runtimes and the higher the chance of the duplication. And at some points it really does get to awfully ridiculous levels.

A while back, I had run everything I possibly could with Flatpak to the point I’d even make my own Flatpak to try and see how well it would work. Instead of using the AUR. And it worked great for the first little while. I’d installed all of my apps and it was fine, but as I kept using the system, kept installing new apps and not uninstalled the old ones, it really started to build up awfully quick, especially with older apps.

I feel like the usefulness of flatpaks is the inverse parabola, where it’s extremely useful in the center use, but when you go to either side of it, it becomes less and less useful.

Apologies for any incoherentcy this was written with a speech 2 text.

I think having separate standard APIs for screenshots, screen capture, and video capture that aren’t married to one implementation makes sense.

The idea of a using a separate thing for it is fine, in itself, but necessitating it is an issue to me. There are a LOT of wayland compositors now, for all sorts of systems, each one also new needs a compatible xdg portals implementation (or whatever third party tool you like), in the case of xdg portals this also means pulling in things like dbus. It actually becomes a lot to build a “Minimal but fledged out” ecosystem. something which should otherwise be possible.

we’re talking about standalone desktop apps, they need some common building blocks no matter if they’re containerized or not, right?

sure but then you have xdg-portals denying actually useful a11y protocols because they “don’t want to expose it to containers” -_- apparently they never heard of a permissions system? but this also highlights why the wayland ecosystem right now is so poor for select individuals (and why they get heated when told that they need to swap to wayland)

I have a couple of issues with portals. One is that we’re putting too much eggs in the basket of something that is designed for containers. XDG portals Have rejected features that people have requested because they don’t want to expose that functionality to a container and they are allergic to permission prompts apparently.

I also have other issues with the portals for instance video capture. It requires you to have a camera portal. It requires you to have a desktop capture portal. It also requires you to have an app to app, video, portal, which doesn’t exist yet. All of these things require pipewire pretty much in most cases, so why can’t we just have a single pipewire portal? It may not scale well in the future, but it doesn’t scale well now anyways. If you want just a generic pipe wire stream, you’re not gonna be able to have it, you’re going to have to conform to one of the standards anyways. For a case in point example, the OBS pull request for Game Scope Capture is the perfect example of this over reliance in XDG portals.

I’m showcasing this just to highlight the fact that the XDG portals are incredibly poorly thought out, and I don’t think that it’s a reliable method for the future going forwards.

PS. Please pardon any oddities in this, I had to use speech to text, since my RSI is acting up.

I did and quite frankly it’s trash, XDG portals are a clunky and quite frankly terrible and poorly thought out api. I’m not the only one that disagrees with this sentiment as multiple people are trying to get protocols like ext-screencopy-v1 for screen recording and ext-foreign-toplevel-* for window management upstreamed into wayland so that xdg portals aren’t necessary for these use cases. I don’t mind the reliance on pipewire too much, but I too think that It shouldn’t be necessary for screen capture.

IMO It is one of nate’s worst takes of all time if not the worst. Usually I agree with most things he writes, but not this, xdg-portals is a travesty, pipewire is nice and all, but I don’t see why we should need an entire media system for basic screen capture capabilities. and clearly im not alone on this sentiment

woops my bad, I mean to link this https://github.com/probonopd/wayland-x11-compat-protocols it’s a repo of going to be protocols, to fill in the gap instead of pretending the issue doesn’t exist

Really glad probonopd is doing this, X11 is dying but wayland isnt ready to replace it, so it’s nice to have this

EDIT, paste didn’t work https://github.com/probonopd/wayland-x11-compat-protocols