Just your normal everyday casual software dev. Nothing to see here.

People can share differing opinions without immediately being on the reverse side. Avoid looking at things as black and white. You can like both waffles and pancakes, just like you can hate both waffles and pancakes.

been trying to lower my social presence on services as of late, may go inactive randomly as a result.

  • 0 Posts
  • 11 Comments
Joined 3 years ago
cake
Cake day: August 15th, 2023

help-circle



  • Honestly. I think if tracking is disabled it should do the following:

    • anything screen dimension related including available height/width -> blocked (realistically java-script should never need to disclose this information outside of an internal function anyway)
    • User Agent: generalized (this usually already is the case)
    • Cookie status: kept the same as needed for functionality.
    • addon/plugin info: blocked
    • buildID: blocked
    • hardware concurrently: generalized instead of a set number (low end being < 4 middle being < 12 high anything else)
    • any hardware characteristics(such as gyro, battery state, etc) -> request for permission by default

    Like there are many steps that can be done to help mitigate fingerprinting, its just getting vendors to actually do it.

    being said I had never known about the TLS fingerprinting option, I generally don’t see that shown on the fingerprint detector sites, that’s interesting.


  • Yes, I post a review on every product and restaurant I visit. I wish more sites let you review more than once as there are some places/products that had amazing visits at one point, but then some visits that sucked hardcore, so allowing the average visit would be nice.

    Why? Because I want to share what /my/ expereience with the service was. If they screwed up, others should know. If they did amazing? Others should know. If I was in the other persons shoes, I would rather have known.




  • I’m not sure location but, if it’s the US my parents had something similar with the no assets thing. Someone stole their car, took it for a joy ride and burned it up the road, they were charged and given a verdict of guilty and had to pay it back, but they claimed no assets. After a few years of no payments whatsoever my mom started complaining, eventually she complained enough they started the legal process of garnishing wages. If he has a job or an income source, they can garnish that either via tax time or via the wages. Being said, the garnish system is super lax for living costs, if they are making bare min wage, you probally won’t get money out of it




  • Personally, it seems like it’s trustworthy again. The previous owner of the repo did eventually admit that they authorized the transfer, but, The entire transfer process was extremely sketchy and had no chain of custody or trust. It was just the repository got deleted, and then a few days later showed under a whole blank state again with a user with no profile, no contribution history, and it was just a trust me bro, I knew the original maintainer look I have the keys to prove it.

    The maintainer of the Google Play build of it seems to trust them though, and they are established in the community, plus they archived their sync thing builds again in favor of just using one repo, so it’s likely fine.

    For future people wondering about it as well, it doesn’t help that the new maintainer of the app has deleted every issue that had to do with the migration, so you no longer can research the issue for yourself. The only information you have available to you is the discussion chain listed on the community forums, But any type of issue that they link to were deleted.

    Personally though, I plan on keeping my current version pinned to prior to the transfer until either I’m forced to update due to bugs or I feel comfortable with the current maintainer again. I’m not sure how long that will be.

    For an app that contains very sensitive information, I was not impressed with how the transfer process underwent.