Zach "earboxer" DeCook @zachdecook@librem.one

@PINE64 Other (I think ordinary) wear and tear from infrequent opening would be the clip closest to the dip switches starting to wear both frame-side and back plate side. So maybe a third thumbnail slot in that corner as well... at that point might as well put one in each corner.

Anyone else crack their #pinephone back plate like this?
Maybe this is from dropping it and/or opening it too much.
I think the design could be fixed if @PINE64 made a backplate that had thumbnail slots on both sides.

@linuxlounge @linuxlounge @LinuxLounge (man putting comments in the right place is difficult. Why do you have 3 fediverse accounts? It'd probably be easier if you dropped one of the peertube accounts and boosted the peertube post from mastodon instead of making a new post).

@FredBednarski @neauoire @rek maybe texture could be used instead of black/white so each die could be printed as a single piece (think stripes/solids in pool, but textured).
Since one side is completely white, that could be the untextured side that sits on the build plate.

@linuxlounge did you manage to test performance with framebufferphone or sxmo?

https://www.jwz.org/doc/cadt.html

The CADT model of software design: just rewrite it!
Note that I do encourage (on the consumer's part) fixing bugs over reporting them, but I covet stability from maintainers.

@neauoire

The protestor's “great stumbling block in the stride toward freedom is ... the white moderate who is more devoted to order than to justice; who prefers a negative peace which is the absence of tension to a positive peace which is the presence of justice;”

@hamblingreen so, we pretend to be the end-users of your software, and needlessly beg for features that you won't implement?

@hamblingreen maybe learn zig... somebody's got to keep his codebases up to date with the changing standard. https://ziglang.org/download/0.9.0/release-notes.html

@hamblingreen is the problem that ~mil's projects don't compile with the newest (or at least, the arch-packaged) version of zig?

@ddevault #cproc is great! It compiled #scalableFont2 in under 9 seconds (12 times faster than gcc).
Runtime comparison, it had about 75% performance.

I'll definitely be using this for development on the pinephone (aarch64).

You can find my #eggnog #recipe live at gemini://gemini.zachdecook.com/recipe/eggnog.gmi

Made my own recipe for #eggnog tonight. (Rather than following some recipe online).
"Try not to curdle the eggnog. After you've curdled it, blend until consistent." 😅 If it's any good, maybe I'll share it.

@craftyguy should we instead distribute our malware with instructions to add our own key for easier updates?

@jameschip Can someone hurry up and make a POSIX-compliant fish-inspired shell?

@arlequin @PINE64 In my experience, applications run similarly across different environments (performance-wise). In SXMO with sway (SWMO), the display scaling is set for the whole desktop, rather than per-application as phosh does. In SXMO/dwm (xorg rather than wayland), scaling probably results in pixelation, so you'd probably config a scale factor of 1.

@PINE64

> While #Phosh is clearly the most popular UI across the board, it came as a genuine surprise to me how popular #SXMO and SWMO are in general and on #postmarketOS more specifically. I didn’t expect such a complex and unorthodox UI to gather such a following in a relatively short period of time. But to be clear, I think this is great. We also shouldn’t overlook that a sizable portion of respondents is indifferent to which UI they use as long as the experience is solid.