Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)C
Posts
7
Comments
99
Joined
3 yr. ago

  • Absoutely. I mostly use Firefox because I'm so familiar with it by now but the privacy is generally much better and it doesn't have a massive monopoly on the web. I'm just a lot more comfortable with it.

    When I have to, I use ungoogled-chromium on desktop and Bromite on mobile. I recommend those to anyone familiar with Chrome.

  • I've read not to bother with Decentraleyes. The dependencies are often out of date which mean you'll hit 3rd party CDNs anyway. Unless its coverage is 100℅, it's less than useless for privacy as the hit pattern to CDNs might even make you stand out.

    Privacy Badger is also redundant if you have uBO.

  • Sounds like someone has sticky fingers.

  • These two form a "mesh VPN" which use direct encrypted links between any number of devices. You can think of it as forming a virtual LAN where you can communicate with devices, including open ports. A lot of them have clever tricks to overcome CG-NATs, which you seem to be struggling with.

    Another option is to just rent a server. You can get massive storage space for less than some VPNs cost and you don't need powerful hardware if your device supports the codecs you're using. You could even get a cheapy VPS and reverse proxy to your Jellyfin server through an SSH tunnel or similar. Lots of options here.

  • They can laugh all they like but I've been to hot climates during "winter" and heard complaints about the cold at 70F (~21C) which is a temperate spring day to me. We're all used to the climates we live in and hate when it reaches (relatively) extreme temperatures.

  • Can you get on with using teddit.net which is a privacy-focused front end for Reddit? It doesn't change much but they'll get less useful data from you.

    Either way, if you use Lemmy more and Reddit less than you used to, they've still lost something.

  • Has anyone independently verified that this is the case for the FP4? It's well known that the FP3 accepts testsigned ROMs, but all discussions regarding the FP4's trusted keys points back to the same FP3-specific thread on Fairphone's forum.

    It seems so.

    I don't know, it does make flashing custom ROMs easier but I would rather have to install my own signing keys or signing keys for the ROM as this way renders a part of the device security completely useless. I'd at least like to have known when I bought it.

    I'm not paranoid which is why I'm still using the device but these three points were each huge disappointments which make me not want to buy another Fairphone.

  • I think it's a Qualcomm Snapdragon SM7225.

    It's not really about better, it's more knowing what I'm getting. It's not their fault that Qualcomm's support is only 3 years (at the time) or that it takes them 10 months to develop support for the chosen SoC which eats into part of that 3 years. Still, I got the phone thinking I would have a reasonably secure device for 4-5 years which wasn't entirely accurate.

    I love the idea and, if you're willing to sacrifice some security for sustainability, that's great. I just want people to know what they're getting into because I didn't.

  • As the owner of a Fairphone 4, don't get one.

    It's sold as a 5G phone but crashes intermittently if you actually enable 5G. I bought a 5G phone and I'm still on 4G. I wish I could say that's the most of the problems, I could live with that.

    The software support, in my opinion, is falsely advertised. You do get 5 years of kernel and Android updates but the system-on-chip updates, which aren't made by Fairphone, end October of this year. That's a whole important part of the updates which cease only 2 years into support.

    Then, there's the real kicker; the hardware root of trust has the (publicly available) AOSP test keys installed. This means anyone can sign and flash a verified ROM if they have access to the unlocked phone. That's perhaps not too important for most people, but it screams incompetence and it means you cannot trust a second hand device.

    When the SoC support is up, I'm moving to a Pixel. I'm done rolling the dice on Android phone manufacturers and I want a well implemented device.

  • I agree. When I learned programming over a decade ago, I didn't follow a course and I'm not sure courses were particularly widespread. Looking back, what I made was terrible quality but it got better with time. At first I'd even copy entire sections of code into place unsure of what it really does and eventually I would make it work. It sounds like OP is much further along than that. Just make something, it's the best part!

  • Weird to see this, I had to do it this morning!

    I have a fix to enable IPv6 but I'll do it after hours :)

  • If we can travel faster than the trolley, we could adjust all switches with one person who continues to travel to the next junction before the trolley arrives!

  • I've noticed advocates for exclusively for libre software and actively discourage simple open source software for not going far enough, also want censorship of not allowing any proprietary software to be mentioned, and don't allow any critiques of the software they use because it's libre software so there are no faults or bad designs.

    I mean, proprietary software isn't popular with people who strongly advocate for free and open source software. At the same time, lots of companies criticize FOSS. Shall we talk about that too? Either way, they have no obligation to cater to you.

    I thoroughly enjoy the code purity of what is labelled as libre software, for license I only like the ISC license for freedom. My attitude is if someone changes my code and doesn't give back, it does not harm me or injury me in any way.

    It may or may not harm you, it depends. It will probably harm the user. Namely; some software is inherently monopolistic. For example, operating systems are monopolistic because targeting more than one is hard for many applications and so we target the few most popular. If you create an OS with a permissive license and it becomes popular, whoever manages to create the most popular fork of it has the power to close the source, drop compatibility and form a monopoly because application developers want to target the most popular fork and users want to run those applications so will use the most popular fork. Whether the owner of the fork did most of the work on the OS or not, they get to reap the rewards of the monopoly. How is that fair or beneficial to anyone in this situation except the owner of the monopolistic fork? How are people supposed to reliably share a standard with each other if the draw bridge can be raised any time major popularity is achieved? The problem here is, only proprietary forks have the ability to do this. You have to actively deny or limit proprietary forks to stop this situation. It depends on the application but the choice of license can have huge implications.

    I also believe libre software can be used for the surveillance of other people, libre software does not be default mean privacy.

    Yes there are examples of this and we fork those projects to not include tracking for those who care enough about it. Can you do that with proprietary software?

    On the principal of freedom, I do support the right to develop proprietary software. The fact that it exists does not harm anyone who chooses not to use proprietary software.

    How does the existence of FOSS infringe on your right to create proprietary software? If you mean that people at the FSF disagree with you, that's just a disagreement. Maybe their personal view is extreme and against your personal liberties but that's not the same as software freedom.

    It seems the die hard libre software crowd, not open source people but the ones who want to live in an only GPLv3+ world can start to live in ther own world, their own bubble, and become disconnected losing perspective that which software other people use is not something that should affect your day in any way.

    As is their right. I mean, it only gets difficult if someone exclusively uses FOSS and you only accept contact via iMessage. Though, if you disagree that much, maybe you shouldn't be in contact.

    Maybe you've just found the folks at the FSF have some extreme views? Please consider, what would it say if Richard Stallman waltzed into a presentation holding an iPad? They kind of have to take the most extreme view, they'd be pretty shoddy advocates otherwise.

  • Yeah, the spread operator is heavy. Admittedly, one iteration of our software abused it and still seemed to run ok. We didn't end up changing that for performance reasons and it was more about code complexity. I wonder how excessive you have to get?

  • I don't know how some developers manage it. I've written web apps in React and, without even using available optimisations, the UI is acceptably snappy on any modern desktop.

    We inherited an application from another vendor (because of general issues with the project) and it's just S L O W. The build is slow and takes several minutes, the animations are painful and even the translations are clearly not available for the first 5 seconds.

    My question is, how? I'm not an expert, I generally suck at frontend and I just had to fill in for it. I didn't purposely write optimised code, the applications are similar in the amount of functionality they provide and they both heavily use JavaScript. How do you make it that slow?

  • Audacity was probably, unknowingly, the first GPL program I directly used as a kid (as in, not a library or software on a server.) We had it on school computers and made silly voice recordings.

    It was either that or Tux paint where we made silly drawings :)

  • Yeah. When a Chromebook can satisfy the needs of a lot of users, I feel some distros were ready even a decade ago.

    The installation step is a huge hurdle. I don't know anyone, except techies, who has done it and even some techies haven't. You can make it pretty (and some installers are both pretty and dead simple) but getting it on a thumb drive and booting from external media are just not user-friendly steps.

  • You've got me down a rabbit hole now.

    Shorter than expected SoC support is one thing, but the hardware root of trust trusting AOSP test keys which was also stated by GrapheneOS is something else. That's a total amateurish blunder and the only reason it's not a complete disaster is you need to boot into EDL mode first to actually flash a recovery. The verified boot is practically useless.

    Thank you for bringing this to my attention, I'm not purchasing another phone from them. Unfortunate, because I liked the removable battery and seemingly long support. Back to the drawing board.