João Azevedo @joao@librem.one

Why is everyone talking about the fediverse? Mashable's Christianna Silva explains the reason behind Meta's interest, the future of social media and how that will change the way online creators reach their audiences.

https://flip.it/uLc6Sx

#Fediverse #Threads #Mastodon

Be a Petal Hero! My game for #cccamp23 badge is finally starting to become playable 😁 #flow3r #flow3rbadge #gamedev #fretsonfire

I don't think this part of the Star Wars story was intended to be prescient.

Congratulations @purism team on hitting shipping parity for the mass-produced Librem 5! I know first hand how hard everyone has worked to get to this point and how many obstacles you faced along the way.

https://puri.sm/posts/thank-you-librem-5-supporters/

#Librem5

Hey Disrooters, here is our new account on the fediverse! Don't hesitate to follow us to know about service maintenance or other information, and to contact us if needed! #Disroot #Fediverse

@agx For context, libcall-ui is a dependency shared by the Calls app and Phosh itself.

GTK4 Calls and GTK4 Phosh coming soon* to a #mobilelinux phone near you 🚀

*pending a little more porting 😅

#gtk #gnome #phosh

Thanks to @antonok libcall-ui's main branch now uses GTK4/libadwaita. We've also tagged 0.2.0~beta1 for that.

For GTK3/libhandy applications there's still the 0.1.x branch.

#gtk #gnome #phosh

Purism is approaching fast shipping parity for the #Librem5 #Linux #phone

They write: "Note to the few early backers who have not yet confirmed your address: “We Have Your Phone Ready to Ship!” Your Librem 5 is ready to ship to you, please reach out to support with your order number (or email and rough date of order so we can work to verify it)."

https://puri.sm/posts/we-have-your-phone-ready-to-ship/

On my way to #DebConf23 \o/

I don't really share my tattoos on social media, but this one seems fitting for mastodon :-) done by my fiancé (as are most). Nice way to play around with colour transitions and lack of outline. Really happy with the result! #Debian #tattoo #colours

A month using #XMPP (using @snikket_im) for every call and chat.

An experiment for my wife and me, and, so far, it has worked *really* well.

https://neilzone.co.uk/2023/08/a-month-using-xmpp-using-snikket-for-every-call-and-chat

phosh 0.31.0 is out 🚀📱:

Lots of fixes in #phoc ➕ better xdg-activation ➕ less CPU usage ➕ animations on tiling/max

#phosh now supports the tablet-mode of convertibles (based on work by Jonathan Hall)

p-m-s allows to configure the notification priority for waking up the screen (thanks to Suraj Kumar Mahto).

libcall-ui switched to GTK4 thanks to @antonok.

Check out the full release notes at https://phosh.mobi/releases/rel-0.31.0/

#phosh #librem5 @purism #gnome #linux #mobile #LinuxMobile #MobileLinux

For the NoScript/uBlock/uMatrix gang

yt-dl.org

Access denied

Due to a ruling of the Hamburg Regional Court, access to this website is blocked.

Zugriff gesperrt

Aufgrund eines Urteils des Landgerichts Hamburg ist der Zugriff auf diese Website gesperrt.

Here is a hopefully-useful notice about Linux kernel security issues, as it seems like this knowledge isn't distributed very widely based on the number of emails I get on a weekly basis:

- The kernel security team does not have any "early notice"
announcement list for security fixes for anyone, as that would only
make things more insecure for everyone.

- The kernel community does not assign CVEs, nor do we deal with them
at all. This is documented in the kernel's security policy, yet we
still have a number of people asking for CVE numbers even after
reading that policy. See my longer "CVEs are dead..." talk for full
details about how the CVE process is broken for projects like Linux:
https://kernel-recipes.org/en/2019/talks/cves-are-dead-long-live-the-cve/

- You HAVE to take all of the stable/LTS releases in order to have a
secure and stable system. If you attempt to cherry-pick random
patches you will NOT fix all of the known, and unknown, problems,
but rather you will end up with a potentially more insecure system,
and one that contains known bugs. Reliance on an "enterprise"
distribution to provide this for your systems is up to you, discuss
it with them as to how they achieve this result as this is what you
are paying for. If you aren't paying for it, just use Debian, they
know what they are doing and track the stable kernels and have a
larger installed base than any other Linux distro. For embedded,
use Yocto, they track the stable releases, or keep your own
buildroot-based system up to date with the new releases.

- Test all stable/LTS releases on your workload and hardware before
putting the kernel into "production" as everyone runs a different %
of the kernel source code from everyone else (servers run about
1.5mil lines of code, embedded runs about 3.5mil lines of code, your
mileage will vary). If you can't test releases before moving them
into production, you might want to solve that problem first.

- A fix for a known bug is better than the potential of a fix causing a
future problem as future problems, when found, will be fixed then.

I think I need to give another talk about this issue to go into the above in more detail. So much for me giving a technical talk at Kernel
Recipes this year...

honestly surprised the balloons haven’t been replaced with just a bunch of 🖕 by now