• 0 Posts
  • 243 Comments
Joined 3 months ago
cake
Cake day: August 21st, 2024

help-circle
  • i can chime in with some actual experience!

    my current problems with KDE are

    • the greeter only accepts my password on the secondary monitor
    • the compositor shuts down whenever something uses the GPU even though the setting is off
    • my primary desktop randomly shunts itself to the right, plopping on top of the desktop on the secondary display and leaving a big black void on half my primary until plasmashell is restarted
    • my panels keep collapsing their content down to the width of a single pixel until i resize them
    • Wayland just crashloops and is completely unusable (no, i don’t have an nvidia card)
    • i still can’t get the acrylic transparency to work :(

    and what’s fun about this is, the issues are so intermittent and random that i never know what i’m going to get on a given day!




  • in the health sector specifically, IT is a mess because you can’t stop people from working or there will be deaths. one thing you should take away from this is that their jobs are important and it is crucial that they can do them. it is your job to support them; anything that stops them doing their job or makes it take longer, even once, is dangerous. improving infra for its own sake is not a good idea because it comes at the risk of peoples lives. the details don’t matter in the face of that.

    if this stresses you out, you can absolutely change jobs. i did.

    if you think you can work within those parameters, and you think you can find ways to improve the system in-place while mitigating the risks, then you will be highly respected.










  • if I’m reading this right, it’s a bit like ipfs+dht. is this a content-addressable system?

    anyway, you should probably have demos of

    • large files (like a Linux disk image), to demonstrate consistency in transfer.
    • Video stream, to demonstrate performance and low latency.
    • multiple files shared with many peers at once, to demonstrate scalability
    • sharing with low bandwidth and high latency, to demonstrate possible mobile use cases.

    thoughts:

    • the logo is very close to wireguard’s.
    • if the data is stored on peers, that means there must always be people with free storage online for it to work? how much storage is needed? is that data in plaintext? could a bad actor push illegal content to peers without them knowing?

    also, please convert the whitepaper to a format that is actually readable. rtf? really?







  • everyone focuses on the tooling, not many are focusing on the reason: python is extremely dynamic. like, magic dynamic you can modify a module halfway through an import, you can replace class attributes and automatically propagate to instances, you can decompile the bytecode while it’s running.

    combine this with the fact that it’s installed by default and used basically everywhere and you get an environment that needs to be carefully managed for the sake of the system.

    js has this packaging system down pat, but it has the advantage that it got mainstream in a sandboxed isolated environment before it started leaking out into the system. python was in there from the beginning, and every change breaks someone’s workflow.

    the closest language to look at for packaging is probably lua, which has similar issues. however since lua is usually not a standalone application platform it’s not a big deal there.