not much

  • 190 Posts
  • 486 Comments
Joined 2 years ago
cake
Cake day: December 8th, 2022

help-circle



  • This article is about Mobifree https://f-droid.org/en/2024/05/24/mobifree.html As far as I can see F-Droid mentions that it will be a contributing partner :

    For more than 14 years, F-Droid has been developing solutions which act as pieces of the alternative mobile ecosystem puzzle. So it was a natural fit for F-Droid to become a contributing partner in the broader Mobifree project.

    F-Droid playing a role :

    F-Droid will play a major role in this project, tasked with creating a decentralized distribution system for developers to deliver apps to Android users.

    Help to create the NGI funded project Mobifree :

    F-Droid is one participating organization who has joined forces to help create this new mobile ecosystem. However, additional input, expertise, inspiration and work will be needed in order to break the traditional framework established by Big Tech. From community outreach to legal support, from developers, to researchers and end users, we welcome all forms of support.

    I don’t read that F-droid will force ads on F-Droid on users any time soon. I can imagine F-Droid will continue to exist as it is but I could be wrong.









  • EDIT: I kinda forgot to actually mention my problem. When booting nornall, I get stuck at a lonely white blinking cursor on a black screen, so startx seems to make some problems. I enter a TTY and run startx and this is what I get when running startx:

    output of startx

    What was the output ? It is not visible for me here.

    • Were you using startx successfully before ?
    • Or are you reverting to trying startx and you did use some graphical display manager like gdm, sddm or lightdm before ?
    • Could it be a disk space problem ? If you run out of space trouble can happen with various applications.
    • Can you boot from a previous kernel (At the GRUB or systemd boot menu) and see what happens ?

  • Huge news 🎉 Thanks OP for sharing.

    It feels like a relief after reading earlier Lemmy comments in other posts about btrfs vs ext4 and having read this Wikipedia page paragraph :

    In 2008, the principal developer of the ext3 and ext4 file systems, Theodore Ts’o, stated that although ext4 has improved features, it is not a major advance, it uses old technology, and is a stop-gap. Ts’o believes that Btrfs is the better direction because “it offers improvements in scalability, reliability, and ease of management”.[29] Btrfs also has “a number of the same design ideas that reiser3/4 had”.[30] 😢

    Oh no, wait a minute, I overlooked the next sentence last time 😀 :

    However, ext4 has continued to gain new features such as file encryption and metadata checksums.




  • I picked the lesser evil

    The choice for iOS can be a convenient choice for daily use if one is ready to deal with the restrictions (Like every other web browser is a Safari browser layer instead of a real browser and the fact that Apple is not into allowing ad-blocking easily). With Android phones the freedom for the end user is, compared to iOS, massive. And having a de-Googled Android phone with a custom ROM is no longer rocket-science or for the faint of heart these days because you can buy custom ROM Android phones pre-installed so you’re good to go.
















  • Yes, go ahead and file the bug. And as others mentioned already, the custom screensaver modifications of XScreensaver like for LM may have bugs. The author of XScreensaver has been complaining about this several times.

    The bug you found looks similar to this one :

    Unlocking a machine locked with Xfce’s screensaver xfce4-screensaver has long been a simple matter of turning two monitors on at the exact same time. That makes Xfce4-screensaver versions prior to 0.1.9 segfault and crash - leaving the machine unlocked. This very unfortunate Xfce bug #16102 has been open since October 29th 2019 and we have pointed fingers at it several times before. Xfce developer Sean Davis has finally closed this gaping security hole. He explained that the embarrassingly long delay before this security vulnerability was addressed was due to “real life conflicts” in a brief comment on March 22nd. He did not elaborate and we did not ask for further details since it is likely none of our business.