Bartłomiej Maryńczak
Bartłomiej Maryńczak
Posting Neothesia logo svg here so it does not get lost (I have lost it and remade it 3 times already over the years)  
I have those (already implemented in [website/homepage-v2](https://github.com/PolyMeilex/Neothesia/tree/website/homepage-v2) branch):   Zach4531 also sent me this design:  > By the way, can you leave hex value of the logo's Gradient...
Ref: #247 got merged, so the situation has improved a little bit. We are using default Vitepress setup and theme for now.
What is the value of using Gnome specific setting if Gnome supports and prefers the existing standard anyway? We had it implemented already [here](https://github.com/PolyMeilex/sctk-adwaita/pull/10/commits/88a908cbbd5880c2c420dd46c240005ee0699e09#diff-cba64c21ab992eaad29fce147a08f4560a4769bc14682b8a96081a5fd02dbecd), but I'm not a huge fan...
Sorry I don't full understand the request, you mean just lowering the log level for the message? Or is the library behaving in an unexpected way when it can't find...
> without a way to fix it Well, settings portals are compositor agnostic, you could run one even in raw TTY, so you can simply run one like GTK portal...
> Why `cosmic-screencopy-unstable-v1` when there is already `wlr-screencopy-unstable-v1`? > > Would it mean that existing tools that use `wlr-screencopy-unstable-v1`, such as `wf-recorder -a`, would not work without modification on Cosmic?...
You can just click on the file name in the breadcrumb, like so, and it will open the source: 
> Would you be open for a PR that extends the API to allow setting this flag? Sure, I would probably just make it the default and call it a...
FYI you have to add protocols to [`src/data/protocol-registry.ts`](https://github.com/vially/wayland-explorer/blob/main/src/data/protocol-registry.ts) without that this MR only adds a frog category.