not much

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

help-circle



  • The mentioned server side changes (e.g. A server move you mentioned but could also be server settings, provider settings, etc).

    I guess that is the case. According to https://searx.space/ the searx.be server is in Austria but might use some proxy to talk to Google and similar to avoid quick blocking. The maintainer of searx.be also maintains yewtu.be and that one uses proxies (The proxy names can be seen when blocking auto play of videos in Tor browser).

    Also getting results in Russian here since a few days. Usually it is either Swedish or Dutch. Never German.










  • 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.



























  • lemmyreader@lemmy.mlOPtoLinux@lemmy.mlLix - a new fork of Nix
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    6 months ago

    https://forum.aux.computer/t/the-future-of-nixcpp-lix/483

    The announcement resolves one of my last fears for Aux: development on Nix itself. It is no secret that the number of people knowledgeable about the project and are willing to work on this CPP codebase is small. You have probably seen me mention multiple times by now that @sig_cli needs all of the help that we can get. Lix resolves this entirely with a trusted team of experts. This means that Aux is now able to remove Nix development from our priorities and can instead collaborate with Lix moving forward.