• 2 Posts
  • 18 Comments
Joined 2 years ago
cake
Cake day: November 23rd, 2022

help-circle

  • it used to be cheaper, and with an audio jack. Add some environment and social consideration and I see many reasons to buy it.

    Or you can buy a Google phone from Amazon and text about privacy or freeing Palestine while sipping your Starbucks coffee in your Tesla car.

    Not everything has to be about how much do you personally get for the money you give.

    I am so glad I could get the Faiphone 3 while it still had an audio jack. At that time the hardware was not too far behind, still too much for my use which is mainly scrolling through obscure left-ish forums and YouTube channels (thanks newpipe) and startups late-stage capitalist hacker news (I don’t know any better about tech).



  • OK I got it, you are completely out of the loop here.

    You do not grasp the idea of NoScript and other JS filtering extension. This is not about server code, your all arguments is baseless here.

    By the way JS refered to Javascript and not NodeJS.

    Anyway I got you whole company/business talk about “keeping the service available, secure, performant” and “GDPR […] bankrupting fine”… yeah lemmy.world.


  • Thanks for your answer.

    First I don’t even grasp what a “service owner” is.

    Second, for JS front-end openness there are already a bunch of app (web, android) that are open-source and secured. Everything has dependencies nowadays, this doesn’t prevent good security. Think all the python app and their dependencies, rust, android… even c\c++ packages are built with dependencies and security updates are necessary (bash had security issues).

    I think with JS scripts it’s actually even easier to have good security because the app is ran in our web browser so the only possible attacker is the website we are visiting itself. If they are malicious then the close-sourced JS script is even worse. Unless you count 3rd party scripts embedded that bad dev uses in their website without even thinking about trusting them. That is also awful in both open or close source environment.

    So even having imperfect security (which happens regardless to openness), who is the attacker here? I would rather run js script on my end if the code can be checked.













  • They list gitea but not forgejo. That’s not really advocating for FOSS. “all” (the ones I looked at) are startup products coined as open-source.

    I really don’t like this website and this list, to me this is replacing bad solutions by other bad solutions (I am sorry for the people that like firebase and co).

    I am sorry for the negativity but I really don’t enjoy this link and all it represents and all the people enjoying such content. I guess I/we should explicitly separate FOSS from open-source.

    I may be out of touch and should be educated on why/how this is good.



  • Thanks for the link, I knew hyperbola for many years from afar. Reading this gave me a lot more insight on the project. I find it very cool and pushing toward better software like GNU, openBSD and suckless.

    Nothing is perfect but for server this distribution could be a nice option . I’d love to see an arm version of it. I guess RISC-V would also be a perfect match for them