• 1 Post
  • 44 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle
  • Like many others, I have mixed feelings on this. If anyone is stopping by and doesn’t want to read through the linked forum thread, this is frameworks goal:

    This isn’t a program to get people to go to conferences and rep Framework, it’s a program to give people who are already going to conferences and showing off their Framework some swag and opportunities to talk with the team. It’s not assigning work, it’s just saying thank you to people who are excited about Framework and active in the Linux community.


  • Just wanted to add something different from the other posts, definately not recommending it.

    That being said, it is a hardware key. You can set it up as a Fido2 key, making it as secure as any of the other options here, it is not biometrics.

    Like I mentioned, you have to be a little crazy to go that route


  • Great answer, I will add that another major difference between the Apex Flex and the FlexSecure is the FlexSecure comes with factory default signing keys (which you can change), while the Apex Flex does not. This means you can’t add your own applets the Apex Flex. Para_lyzed touched on this but I wanted to emphasize that the flexsecure gives you the ability to fully manage the implant while the Apex Flex doesn’t. There are trade-offs of course.



  • carzian@lemmy.mltoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    11 months ago

    As someone else suggested, there are plenty of kde apps that could use some devs.

    Kde plasma multi-monitor support could also use some love, though its much better than it was a year ago.

    I know that mobile linux could definately use more devs, if you want to stretch the meaning of desktop 😁. Kde plasma mobile specifically needs help porting their stuff to qt6 for the up coming plasma 6 release.






  • They are decommisioned datacenter drives, this could be for a variety of reasons (including errors). There are many discussions online about them wiping smart data.

    It depends on your use case, I have a few of their drives in a nas specifically for media. I received one bad drive that failed my burn in tests, which they exchange without issue. All of my important files are stored on a seporate ssd based store.

    All depends on your risk tolerence and needs.




  • I’m using US Mobile. You can choose between using their GSM network (T-Mobile) or their CDMA network (Verizon). Their prices are fantastic and it’s all prepaid, so you can limit how much personal information you give them. They’ve worked out a deal with Verizon so your data isn’t deprioratized even though you’re not a primary Verizon customer, so there’s no speed penalty. I’ve been very happy with them





  • Opnsense has an arguably better UI, and more frequent updates.

    You can look into the drama about the pfsense devs when opnsource forked it but the tldr is the pfsense devs were openly hostile in a variety of unprofessional and uncalled for ways to opnsense.

    More recently, pfsense devs rushed the wire guard integration which turned out to be so problematic that the wire guard devs had to publicly comment that it shouldn’t be included inorder to prevent it from shipping. One of the reasons why opnsense forked a few years prior was due to bad code quality of pfsense.

    Also my two cents, if you’re going to create this list to benefit the community and you don’t want to include too many options, then you’ll need to make informed decisions on which projects to include and why. Relying on the community is fine, and crowed sourcing knowledge is powerful, but don’t ignore large projects without researching them