~kaey

Recent activity

Re: Text rendering on HiDPI screen a month ago

From Konstantin Kulikov to ~eliasnaur/gio

> That’s great. May I ask a screen capture of the kitchen example ?
>
> A 27" 4k screen is 163 DPI, not 192. How do you get 192 DPI ?

https://0x0.st/-pr7.png

I scale UI to 192 because qt and gtk don't exactly work well with 1.5
scaling - some apps work well, others, for example, have big icons
with microscopic text.

Re: Text rendering on HiDPI screen a month ago

From Konstantin Kulikov to ~eliasnaur/gio

What Alessandro said.

At 192 DPI text is lighter compared to browser and it's immediately noticeable.

If you're looking for a 4k display I use this one and can recommend it
https://www.tftcentral.co.uk/reviews/acer_nitro_xv273k.htm

Re: Containerised APK builds and security xattrs 2 months ago

From Konstantin Kulikov to ~sircmpwn/alpine-devel

Some packages also use libcap to enable servers to listen on port 80
without root privs.

On Wed, May 5, 2021 at 9:20 AM Timo Teras <timo.teras@iki.fi> wrote:
>
> Hi,
>
> There are multiple reasons why we want the xattrs. Originally it was
> introduced to store the grsec kernel pax flags, and some packages also
> use it to set capabilities for some executables. APK also internally
> uses XATTRs for the file hash, but that happens transparently and never
> hits the disk surface.
>
> It might make sense an abuild option to not include the on-disk xattrs,

Re: A shared vulnerability format for open-source packages 3 months ago

From Konstantin Kulikov to ~sircmpwn/alpine-devel

> Maybe we can get everyone together in ##distro-security to talk about this
> and organize something?

I'm not involved in this work, just thought it would be useful for alpine.

>From the doc:
>This format is still in early stages, a work in progress. Feedback from maintainers of other vulnerability databases is most welcome. Please feel free to add comments directly to the doc (preferred) or to mail rsc@google.com. Once we have some confirmation that the approach is viable and adoptable (perhaps after further modifications), we intend to move this document to an appropriate permanent home.

A shared vulnerability format for open-source packages 3 months ago

From Konstantin Kulikov to ~sircmpwn/alpine-devel

Russ Cox of Go language team has drafted a proposal for a shared
vulnerability format for open-source packages with goals to enhance
interoperability between language teams, security researchers, and
cross-language databases.
See google doc [0] and his original tweet [1].

[0] https://docs.google.com/document/d/1sylBGNooKtf220RHQn1I8pZRmqXZQADDQ_TOABrKTpA/edit#heading=h.ss425olznxo
[1] https://twitter.com/_rsc/status/1386682831770988545

Re: Proof of double gamma correction error with anti-aliasing 3 months ago

From Konstantin Kulikov to ~eliasnaur/gio

On linux amdgpu:
1. I also see horizontal lines, they disappear if you run with
GIORENDERER=forcecompute
2. Gaps are there, yes. I think they appear on a mismatched aspect ratio.

On Mon, Apr 26, 2021 at 6:33 PM Christophe Meessen
<christophe@meessen.net> wrote:
>
> Hello,
>
> The article referenced by Elias [1] was very instructive and gave me the
> idea to generate gray ramps with Gio to compare the result with what we
> should expect.
>

Re: [3.15] System change proposal: rename the Alpine 3.15 release to Alpine 15 3 months ago

From Konstantin Kulikov to ~sircmpwn/alpine-devel

Please consider using dates for versions, like ubuntu. Every time I
hear "buster", "big sur", "lollipop" or "freebsd 12" I have no idea if
the person is talking about recent version or a dated one.

On Fri, Apr 9, 2021 at 5:31 AM Ariadne Conill <ariadne@dereferenced.org> wrote:
>
> Hello,
>
> Alpine has traditionally used the major version to represent the current
> ABI version the system uses.  For example, Alpine 1.x was uClibc without
> NPTL, Alpine 2.x was uClibc with NPTL and Alpine 3.x is based on musl.
>
> With the current ABI being evergreen, and our having moved past the 3.14
> release, it no longer makes sense to keep the 3.x designation.  When this

Re: Use of supervise-daemon in Alpine 11 months ago

From Konstantin Kulikov to ~sircmpwn/alpine-devel

How can anyone seriously consider switching globally to supervision
service that cannot even properly redirect daemon's stderr to a file?

Re: [PATCH gio] app/internal: [X11] implement Window.Close 1 year, 1 month ago

From Konstantin Kulikov to ~eliasnaur/gio-patches

On Sat, Jun 20, 2020 at 7:47 PM Elias Naur <mail@eliasnaur.com> wrote:
>
> I'm not sure XUnmapWindow is correct either. See
>
>         https://tronche.com/gui/x/icccm/sec-4.html#s-4.2.8.1
>

Window managers react to UnmapNotify, see for example
https://github.com/nigeltao/taowm/blob/master/main.go#L399

What you've linked is a protocol for WM-initiated deletion, not client one.

Re: Understanding drawing delay 1 year, 2 months ago

From Konstantin Kulikov to ~eliasnaur/gio

> Right, Ok.
> 
> Thanks for that clarification, it does make sense, I would just not
> have expected it to
> be that noticeable.
> 

There was a discussion at https://todo.sr.ht/~eliasnaur/gio/63
TLDR: if you set c.Context.EnableVSync(false) in app/internal/window/egl_x11.go
you'll see that lag is gone (assuming you're on x11, no idea how other platforms work).

I've argued already if gio wants to make action games possible it needs
an option to disable vsync at allow user configurable fps limit, but ¯\_(ツ)_/¯.