Zach "earboxer" DeCook @zachdecook@librem.one

We are rapidly approaching three years of Weekly Updates on #LinuxMobile! 📱🎉

Please help on with coming up a nice summary of all that time to celebrate! The pad for this is at https://pad.hacc.space/5g5RIS0qSh2hoPhMzCsL9w?both#

Thank you, @Blort for the great idea!

https://writefreesoftware.org

Introducing Write Free Software: A comprehensive educational resource for the free software community

https://writefreesoftware.org/blog/introducing-writefreesoftware.org/

#freesoftware #foss

the april blog post is out, ditching duckduckgo for mojeek. i've loved using this search engine for a few months now, and wanted to write about why i opted to use it in place of duckduckgo. https://hamblingreen.com/

Ever since doing the initial completion support in #phosh 's osk-stub I wanted to add a generic "unix pipe" like completer. phosh-osk-stub would feed the program preedit on stdin and read the completions from the program's stdout.

That is there now and with that and some more changes I can use @zachdecook 's #swipeGuess to do swipe like typing. To be clear: all the hard work is done by swipeGuess, phosh-osk-stub just piggy backs on it:

#LinuxMobile #gtk #gnome #librem5

What kind of Linux distribution is running on your main computer?

#linux #distributions

why do I support right to repair? simple: i want to upload my own MIDI files to my washing machine to play when it finishes a cycle without voiding my warranty

Me trying to figure out how an API works in a FOSS tool: "Let's go to the git repository to see what it does."

Me trying to figure out how an API works in a multi-million dollar VLSI tool: "Lets guess and check a bunch of random ideas because nothing works like it should."

*sigh*

IMO the set of software licenses which covers basically everyone's needs are MIT/BSD, WTFPL, CC-0, Apache 2.0, GPL, AGPL, MPL, and OFL.

If you're using anything else, you should have a good reason.

My door's always open if you need help choosing a license for your needs!

For those that are not familiar: https://wiki.eth0.nl/index.php/LackRack

Administrative note: I just received a request to share our server's moderation data from someone who claims to be a university researcher (and seems to be legitimate - on a cursory search).

I rejected that request for a variety of reasons; chief among which is that such data does not belong to me, even as a server admin who solely pays for the hosting of my server. Since this is the case, further research into their claims was, frankly, unnecessary.

We made a promise that user data is not for sale - and "free" is a price. Yes, it probably would be *possible* to remove "sensitive" information - but that would be at my own judgment, not that of the users to whom it pertains. All of the moderation data, it is true, would concern users which are from other servers - but I don't see how that matters. Giving away someone else's data, even that of people we have specifically moderated, doesn't seem any more palatable, when viewed in that light.

Caveat: I was willing to share a) The simple number of federated users deactivated b) The simple number of posts moderated c) The amount of time per day that I spend on moderation - as that is either data generated by the server itself, or properly belonging to myself. I am also aware that some would find even that to be an overreach - and I understand that position, somewhat - but I will reiterate that such data, which pertains solely to server operation, is purely within my discretion, as server administrator, as it gives out absolutely no personal data other than my own, and only server data, otherwise.

While I sympathize with researchers' omnipresent need for data, I would caution fellow server admins to remember that administration is a trust, and that such trust needs to be fed and watered on occasion for it to stay healthy. You don't have the luxury of choosing who to share your users' data with.

The Helios micro-kernel ABI https://spacepub.space/videos/watch/4f7d2307-ab24-41e4-92f4-9bf89d57eac0

We are developers and designers making user-friendly apps. We take pride in our craft and work hard to make sure our applications are a great experience for people.

Unfortunately, there are increasing efforts on the current market to disallow or discourage customization. This worsens user experience for a lot of software.

Kirigami colour sets allow developers to easily make their UI work with any colour schemes.

Icon Themes allow users to have a unified view across different applications.

Application styles allows users to decide how a button is represented, how wide a scroll bar should be, etc.

All these not only give users the freedom to decide how the applications should behave, but also make room for accessibility considerations like larger buttons, more visible focus indication, and more contrastive colours and shades.

This is why we believe application developers should be aware of the possibility to customize its appearance.

If you are an application developer, we kindly ask that you do not hard-code any colour or size, but rather follow the system styles.

On a platform level, we should implement a colour set editor that informs users about what colours might be put where, and advises about how contrastive the foreground and the background are in different places.

If you are a user or distribution maintainer that ships our apps, and you are having issues with our apps on your customized colour set or application style, please do tell us, and we can figure out the cause of the problem.

Signed, tusooa, maintainer of kazv.

This document is inspired by https://stopthemingmy.app/ .

@zachdecook Thank you for your feedback, this is the future plan!

The Case for LineageOS and the #PinePhone

https://jleightcap.srht.site/blog/openphone.html

Anyone interested in the multiplayer FPS game I'm making - we've got a new domain and a simple website now! Thanks to @siina for her awesome work on that!

https://libla.st/

#Liblast #GameDev #indiegame #GodotEngine #Godot