• 3 Posts
  • 107 Comments
Joined 2 years ago
cake
Cake day: June 21st, 2023

help-circle






  • E2E with privately generated and held keys, have you published your PGP public key yet?

    Exactly. You can’t stop secure encryption.

    I remember in the very old days of the internet when only the US had strong encryption and thought it was some gotcha. They labeled it a weapon to prevent overseas export. Phil Zimmerman created PGP, lobbed the source into a book (protected under 1st amendment) then shipped it overseas.

    If strong encryption exists and people want to use it, you’re just not going to be able to stop them.





  • khannie@lemmy.worldtoAsklemmy@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    4 months ago

    I agree with all of that but some folks just aren’t clear communicators and / or English isn’t their first language so unless it’s a real workload to read, I’m generally grand with it.

    I actually find the general standard of text posts on here very high. I’d bet money that the number of correctly used commas per post here is way higher than the internet average, though that’s purely anecdotal.




  • Monero is built as a privacy first crypto. Essentially it’s like cash in many ways. You spend it in the shop and nobody knows where the cash you’re handing over came from. When you get your change at the till you know nothing about who had the cash before you that you just got handed. It’s just money.

    This is all handled by a bunch of very complex cryptography. If it comes to it there are ways to prove you sent the money etc but only you have that capability to decide to share.




  • You can make nearly all images small enough to upload and still look good without dropping colour depth. There are 3 ways to achieve it basically:

    • Resize it to a lower resolution (1280 x whatever looks just fine on a screen)
    • Reduce the quality
    • Change to lossy (JPG) from non-lossy (PNG)

    The resizing is usually enough.

    The quality reduction is something that google pagespeed focuses on too. For most apps that means choosing a lower “quality” when converting to jpg or saving as a new jpg. 85% of original is good.

    If you happen to have imagemagick installed, I have a little script that I use called “resize_to_pagespeed.sh”. The jist of it is this:

    convert inputfile.jpg -filter Lanczos -resize 1280x1280 -sampling-factor 4:2:0 -strip -quality 85 outputfile.jpg

    I just ran this on a 2.4MB photo (below) and it came out at 186KB. That’s a 13x reduction. Right click -> open in new tab to see it full size.

    If the image isn’t square, imagemagick is smart enough to figure out correct dimensions.