• 9 Posts
  • 52 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle

  • Love this. Always interesting to see novel ways of querying data in the terminal, and I agree that jq’s syntax is difficult to remember.

    I actually prefer nu(shell) for this though. On the lobste.rs thread for this blog, a user shared this:

    | get license.key -i
    | uniq --count
    | rename license
    
    This outputs the following:
    
    ╭───┬──────────────┬───────╮
    │ # │    license   │ count │
    ├───┼──────────────┼───────┤
    │ 0 │ bsd-3-clause │    23 │
    │ 1 │ apache-2.0   │     5 │
    │ 2 │              │     2 │
    ╰───┴──────────────┴───────╯
    
    










  • Another vote here for Fastmail. I also like Posteo, Mailbox and mxroute, but these are not as fully featured - which may be perfect for you if you’re after email only. What I really like about Fastmail is that on top of being a customer-focused business (rather than a customer is the product business), they offer a really snappy web interface with excellent search - and they are extremely compliant with email standards, building everything on JMAP.

    I do not like Proton or Tutanota. I have used both, including using Proton as my main email account for the past two years. I do believe they are probably the best when it comes to encryption and privacy standards, but for me it’s at far too much cost. Encrypted email is almost pointless - the moment you email someone who isn’t using a Proton (or PGP encryption), then the encryption is lost. Or even if they just forward an email to someone outside your chain. I would argue that if you need to send a message to someone with enough sensitivity to require this level of encryption, email is the wrong choice of protocol.

    For all that Proton offer, it results in broken email standard compliance, awful search capability and reliance on bridge software or being limited to their WebUI and apps. And it’s a shame, because I really like the company and their mission.









  • The same reason a lot of companies support a community edition. It means that people can use, learn and become experienced with the product without forking over a tonne of money.

    This results in a larger number of developers, add-ons and community surrounding the product.

    This makes it a more appealing product for companies looking to build a business using it.

    It’s the same reason you can use AWS for free, get some JetBrains products for free and often find community editions for similar products to Magento.






  • Care to give a summary on why you think they should be blocked ahead of any bad acting? Yes, there is some concern about Meta attempting EEE, but ultimately they’re a large platform that can bring a lot of users and attention to the Fediverse. There’s nothing preventing large instances from blocking them down the line, and with user level instance blocking coming in 0.19 to Lemmy (not sure if Mastodon et al have something similar), you can block them personally yourself if you wish, rather than having that thrust upon you by your instance admins.