• 0 Posts
  • 27 Comments
Joined 1 year ago
cake
Cake day: July 5th, 2023

help-circle

  • So far, there is only some user settings accessible in the web interface. I don’t have an iPhone, hence I cannot say for their app. The android app will come later, apparently.

    I don’t give a removed about TikTok or short form video but legitimately how is this expected to succeed with these limitations? Clearly people like this stuff but can a fediverse service really afford to be iPhone only? This truly seems doomed to fail.




  • Re Google Safe Browsing

    I would argue it’s a security feature with potential privacy concerns, however I would agree it is more of a failsafe or suggestion.

    However it being disabled by default or not included at compile time versus enabled by default may also be relevant when it comes to security. As a hypothetical a high severity bug with Google Safe Browsing could arguably make a browser less secure. However even as a failsafe/suggestion, the small security benefit may make the overall browser more secure, e.g. filtering known bad websites that attack known vulnerabilities.

    I’m also just using Safe Browsing as an example here, it may or may not be worth focusing on since a browser is basically an operating system.

    You mentioned sandboxing, which I think is perhaps a more reasonable scope.


    1. Do you have your current list of sources? You mentioned you want more, but where are you looking to start? For example are you looking at the CVE database? Are you looking at competitions like Pwn2Own? Or detailed project group like Google Project Zero?
    2. Is it fair to compare Chromium, which is not an end user product, to Firefox which is? Do you plan to look at or compare forks of the software? As an example both Google Chrome and Mozilla Firefox enable “Google Safe Browsing” by default, however the fork “ungoogled-chromium” does not include “Google Safe Browsing” (and they provide their reasoning).


  • Re Concentration I’m not concerned that it is as of yet a problem. However I do think it is also a larger problem for Mastodon and other user-centric platforms than it is to Lemmy and other community-cetric platforms.

    If a Mastodon user wants to leave their server there are migration pains. If your server makes a controversial change, you may have to migrate. As a follower if something goes wrong I have to remember that I was following Ada & Bob, but maybe Bob now goes by Bobby.

    However as a Lemmy user I can just abandon my server and be done with it. If my server makes a controversial change, I can just leave. As a community follower can watch as Star Trek Memes becomes Risa, or Risa becomes Ten Forward. The names changed completely but it’s easy to find my community again.


  • I use flat case most of the time, but I also try to stick to single word files so there is no case to get in the way.

    I think for documents I might share like a PDF I’d use Pascal case.

    In a classroom or teaching setting I will sometimes use Kebab case as I find it is the least confusing and makes it extra clear where the word division is. Similarly I avoid Dot notation since it’s confusing for folks coming from a Windows world.

    And I would avoid Screaming because that’s just too loud anywhere.


  • Sure that reveals your distro, but also consider what is in the logs you’re sharing. If you’re asking for help you probably also already said that you’re running Debian. Or the logs are full of apt logs already, querying a well known Debian mirror.

    You’re right that PC is a fine default, but think about the whole picture as well.


  • Is the problem account making or data having persistence/backups?

    Or is the issue having an account on service A, service A dieing and then when you create an account on service B you have to start over again, so we need to improve account portability?

    I guess I also wonder… Is that a real problem for Lemmy? For Mastodon where you follow users sure, but does anyone care about their Lemmy account?








  • https://www.mozilla.org/en-US/security/advisories/mfsa2023-56/

    That’s a link to the most recent release of Firefox and the security vulnerabilities that were fixed.

    You’ll notice the first one listed says, “This issue could allow an attacker to perform remote code execution and sandbox escape.”

    So if you visited a site that exploited that bug, it escaped the sandbox and ran whatever code it wanted to. Since you were running as root it could do anything it wants. Your device is now the property of someone else. Potentially all your data has been stolen. You probably didn’t even notice.

    Now. Realistically. You probably didn’t get exploited. Your device may not be vulnerable to that particular bug. But new bugs are found, and fixed, and created every day. Can you be sure you weren’t exploited?

    Let’s look at it a different way. Think of it like driving a car with no seatbelt or airbags. As long as you don’t crash, you’re fine. The car still works fine without seatbelts and you have more freedom to move your arms around.

    Let’s look at it a different way. Do you ever lock the door to your home/apartment? Heck do you even close the door? Why not leave it wide open?

    At the end of the day security is about layers and the trade offs for convenience. You can run KDE as root, and you can run Firefox as root. You’ll probably be fine. It’s like driving without a seatbelt or leaving your front door wide open, but you can do it. If you do drive with a seatbelt and at least close your front door, you can probably run KDE and Firefox as a regular user.



  • Someone who disagrees with you is not a bootlicker.

    Meta is a garbage company. Meta has done terrible things historically. At the moment we don’t know how Threads will affect the rest of the Fediverse. I’m ok with giving Meta a short leash. If you disagree, join an instance that has already blocked them. That’s how this works.

    I fully expect, once rolled out, I’ll block Threads, but that is MY choice to make.