• 1 Post
  • 91 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle



  • Thanks, that’s an interesting read.
    I know that’s one person’s opinion and not a thorough research, but that’s still plenty of red flags.

    I’ve used the 100 searches in the free trial, thought the search was fine, better than Google’s these days. The subscription is a bit steep so I held off, kinda glad I did after digging more into this.

    Having what little employees they have also make a mac-only browser, AI stuff and email that their user base doesn’t seem to want is all a bit weird.
    Buying a t-shirt factory (wtf) with the money they could have used to potentially lower the subscription, but decided to burn through it to give out free t-shirts. That just screams narcissism-driven to me.

    Their vague statements on privacy isn’t convincing at all.
    Some variation of “we don’t care about your data” isn’t in any way compelling evidence that you care about protecting the privacy of said collected data.

    In my opinion they lack focus, commitment and conviction into what I thought was their primary mission at first glance: being a privacy-focused no nonsense search engine.
    Although that’s probably on me for reading what I wanted to see between the lines and that never was their stated mission, which would explain a lot.






  • The problem is there’s likely not a universal solution that’s guaranteed to clean everything in every case.

    Cleaning specific logs/configs is much easier when you know what you’re dealing with.
    Something like anonymizing a Cisco router config is easy enough because it folllows a known format that you can parse and clean.
    Building a tool to anonymize some random logs from a specific software is one thing, anonymizing all logs from any software is unlikely.
    Either way, it should always be double-checked and tailored to what’s being logged.


  • It depends a lot on what the application is logging to begin with.
    If a project prints passwords in logs, consider to just GTFO as it’s terrible security practice.
    There might also be sensitive info that’s not coming from a static thing like your username, but from variable data such as IP addresses, gps coordinates, or whatever thing gets logged.
    Meaning a simple find&replace might be insufficient.

    When possible, I tend to replace the info I remove with a short name of what I replaced out as it’s easier to understand context when it’s not all ********** or truncated.
    example:

    proxy_container_1     | <redacted_client1_ip> - - [17/Aug/2024:12:39:06 +0000] "GET /u/<redacted_local_user2> HTTP/1.1" 200 963 "-" "Lemmy/0.19.4; +<redacted_remote_instance3_fqdn>"
    

    keeping the same placeholders for subsequent substitutions helps because if everything is the same, then you don’t know what’s what anymore.
    (this single line would be easy enough either way, but if you have a bunch and can’t tell client1 from client50 apart anymore that can hinder troubleshooting.

    regular expressions are useful in doing that, but something that works on a specific set of logs might miss sensitive info in another.

    I’m sure people have made tools to help with that, possibly with regex patterns for common stuff, but even with that, you’d need to doublecheck the output to be 100% sure.

    It helps a lot when whatever app doesn’t log too much sensitive info to begin with, but that’s usually out of your hands as a user.






  • I had never really thought about this before, but I’ve always imagined and played dragons as having an undefined sexuality/gender or at least in a way where it wasn’t really a defining part of their identity.

    Sex: Dragon sexuality is a bit too much of rule34 for my games.
    Gender: Social constructs don’t necessarily translate between a fantastical species and our labels? let alone our limited understanding/imagination of whatever ficticious draconic society.

    In a broader way, most things have been tainted by misogyny or other bigotry.
    I don’t think we should hide and pretend it never happened, but rather recognize the shortcomings and try and move forward in a more open and interesting manner.

    Gygax is dead. 2024 D&D is not Gygax.

    TL;DR: If a player asks which sex or gender a dragon is, just roll for the breath weapon before they can find out?




  • If I’m honest? probably nowhere near enough.

    The 46 hours is assuming it moves at 300mm/s on that axis for 46 hours, which just isn’t the case.
    I say this, but as a ballpark figure this is still useful. Even if typical prints probably take longer than that to reach 50km on an axis, that still tells me I certainly don’t lubricate them as often as I should.

    Maybe that’s something printer firmwares could one day be modified to calculate and warn the user about.


  • a home-instance temp ban will override a remote instance perma ban (there’s a PR in the works to fix this , but it’s the way things are currently)

    The way things work now is annoying.

    Troll creates an account on instance A, posts racist shit or other uninspired bait on instance B.
    Gets instantly permabanned from instance B.
    3 days later, home instance A decides to ban them for a week.
    Thus, a week later, user is automatically unbanned from home instance and all federated instances, including where they were permabanned.
    Current behaviour is bananas.

    This particular troll’s lack of creativity is unsurprising.