• 0 Posts
  • 15 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle
  • JustEnoughDucks@feddit.nltoLinux@lemmy.mlBazzite or Suse?
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    2 hours ago

    Is your printer network attached and scanning via flatpak packages?

    Network printing works fine, USB printing and scanning works also, it is just anything having to use saned that flatpaks can’t seem to use

    I have hopped through multiple distros and I have never once had scanning not work on a “normal” one after correctly setting up saned. Only bazzite because of the flatpak/system split (also why any embedded programming needs distrobox)





  • I think the issue is more that large tech firms can absolutely deal with external security in their applications. The amount of times gmail or Microsoft 365 has been hacked and leaked a bunch of client data is statistically zero when looking at their attack area.

    Joe Dirt self hosting a mail server for his neighbors on a salvaged rack server is 1000x more likely to get hacked or lose a ton of his neighbors’ data than a big tech firm.

    That is kind of the trade off for community hosting. There are very very few backup and security-literate people in communities.



  • I have written a more detailed comment on it before, but 2d printing is much more technically complicated than 3D printing, and the resolution is literally an order of magnitude difference (0.2mm vs <42um) and the printer has to print full color on any surface with microdots in a very very short time. People would throw the printer out if it took 10 minutes for a single paper like a large first layer takes in 3D printing.




  • The few things I don’t like about flatpaks (which become a problem on atomic distros that use almost all flatpak by design):

    • Some types of embedded development is essentially impossible with flatpaks. Try getting the J-link software connected with nrftools and then everything linked to VScodium/codeoss

    • Digital signing simply doesn’t work, won’t work for the foreseeable future, and is not planned to get working,

    • Flatpaks sometimes have bugs for no reasons when their package-manager counterparts don’t (e.g. in KiCAD 8.0, the upper 20% or so of dialog boxes were unclickable with the mouse, but I could select and modify them with the keyboard, only the flatpak version)

    • The status on whether it is still being actively developed or not (at least I hear a fair amount of drama surrounding it)

    But besides those small things, it seem great to me.


  • Some drives are worse than others and higher capacities get worse and worse, in my experience, Seagate drives are extremely loud.

    If you get helium drives (like wd red plus > 8TB i think),or 2nd hand hgst/ WD enterprise drives) they are significantly quieter.

    But, having an ssd is cheaper probably. I have an SSD for the boot drive and all databases, configuration folders, etc… In docker so general IO is fast, then media, documents, pictures, etc… On the big HDDs.



  • KNX.

    Everything is decentrally programmed, and you can do extra automations and stuff from home assistant, but KNX devices are wired (generally) and will always Just Work™. More expensive that the cheaper retrofit options, but if you factor in manual overrides or getting the “better” wireless smart devices it is comparable. They generally also have a manual override at the panel. For core functions like lights, HVAC, roll shutters or blinds, etc… That is honestly the best option (unless you want every light to be an RGB light for some reason, then you still need smart bulbs)