• 1 Post
  • 173 Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle


  • I’d recommend video streams from BBC, Sky News and Channel 4 all in the UK. Channel 4 is partnering with CNN for data and shared stories, and their UK election coverage earlier this year was well regarded. TV news in the UK has to be impartial by law so they will not take a side in the election. They will however voice opinions from both sides.

    Having said that though all coverage will endlessly speculate all night on what ever result means because that’s the nature of elections and filling air time.

    Regarding the Guardian, that is not regulated but it is a good quality broadsheet. It is left leaning and effectively supports Harris but it’s coverage will still be good quality and not as partisan in the style of US media. But expect it to be biased somehwta in Harris’ favour.




  • I don’t have specific experience with the tools you list, however on googling it looks like Ableton Live does work under wine. Wine is what underpins playing windows games on Linux too; it’s very powerful and effective.

    You can install Mint into a VM environment on your current PC (such as Virtual Box) and see how you get on with software you really can’t live without. It won’t run as fast as real life in a VM but you should get an idea whether any tools you can’t live without can work.

    As for OneDrive there are unofficial clients to get it working with Linux if you want to sync to your local filesystem. However Microsoft doesn’t officially support it beyond Web browsers, so if you want something slick and supported you probably would be better migrating to other solutions. You’d certainly be able to migrate with the unofficial clients but I’m not sure I’d want to rely on them long term as things xna break if Microsoft unilaterally changes something.


  • There are PPAs with different builds of ffmpeg for Ubuntu. It also depends what codecs are needed as to whether this is even relevant?

    Bearing in mind some (many) encoding codec libraries are not installed by default as most people don’t need them but can readily be added from the official repos via apt or synaotic. Each codec is usually provided as a library of its own; ffmpeg is more than just one set of binaries. There is a big difference between an incomplete build and incomplete default install of all available libraries/codecs. Most people don’t need or want every possible encoding codec installed by default.

    However some codecs are more strictly licensed and may need to be installed or acquired via different routes - that is the nature or proprietary software (as on Windows).

    Which codes are you saying are not available in Ubuntu official repos?


  • One significant difference that has been missed here is that Laptops can and often do run on the power supply, while phones usually use the power purely to charge the battery.

    It’s a significant difference as the laptop needs a stable electricity supply to supply all it’s components or the laptop would crash. That means not only does the brick need to dissipate heat, but it also needs to be able to deliver a stable continuous DC current. So as well as a transformer and rectifier (that together convert AC to the correct DC needed) there are smoothers and potentially capacitors to ensure a smooth continuous output even if the wall supply is janky.

    If you turn off the power at the wall / unplug you often see any light on the power brick stay on - that is because of the capacitors and there is still a small amount of energy available to the laptop as it discharges.

    While phones are mini computers they are usually designed to always run on the battery. Even when charging, the phone draws it’s power from the battery and it’s in built circuits to smooth the current; there isn’t usually the redundancy in a phone to switch between different supplies in the same way as a laptop. There isn’t also the expectation that they need to run off the wall continuously by users (even if users might plug their phone in and expect to continue to use it, they will find their phone shuts down if its at 0% and they push it beyond what the recharging battery can supply; a laptop would be expected to run solely on the wall not shut off).

    Things are blurring now with USB C power supplies for laptops - but you will find the plug itself has more of the electronics built in or some of the functions of the power brick have moved into the laptop to reduce charger bulkiness. Look at how bulky a USB c charger plug is for a Mac - they’re not simple USB chargers you’d use for a phone or tablet, they’re bulky because they are also doing the smoothing and stabilisation people expect for their laptops.

    Tl:Dr they’re different sizes because they’re doing different things. Basic chargers purely charges a battery, while laptop chargers both charge a battery and provide good quality supply to keep a laptop running optimally.




  • Flatpak is supposed to be a sandbox, so if there is a vulnerable dependency then in theory any attack would be limited to the sandbox.

    However, it depends on the software - some Flatpak need quite low level access to use, and in that case an attack or mlaware could get into the main system. And unfortunately Flatpak itself has vulnerabilities which cna negate the whole idea of a sandbox.

    Flatpaks should be using up to date secure dependencies, but the reality is many do not. I would not rely on Flatpak for security. Even fully up to date Flatpaks can be insecure, and Flatpak itself have vulnerabilities that have needed fixing. And for many Flatpaks it’s not even clear who is maintaining them.

    Flatpaks are useful for deploying software that’s just not available in your distros repos. But when deploying any software outside your repos - including App Image, build from source or 3rd party repos - you are opening your system up to security vulnerabilities. That’s the nature of installing 3rd party software. Flatpak offers some reassurance compared to some methods but it’s far from perfect.

    If security is your prime concern, then Virtual Machines may be more secure route to sandboxing software (if done properly). Building from source would be the other option, as it means you take ont he responsibility for security by using the latest code including for dependencies. But there is no perfect option, it’s always about balancing risk vs convenience.

    It’s also worth noting that software repos are also not perfect. But good distros invest a lot of time and effort in keeping them as up to date and secure as possible, usually via the hard work of volunteers.





  • Then you have to trust the person you are communicating with has turned off windows recall. That has to be the starting position.

    Tools will come to block or break windows recall but it will still be based on trust that the recipient is using them. Privacy centred apps like Signal wouldn’t want windows screen shotitng every message for example. There are many apps and tools including in the professional sphere that would not want their data leaking via recall so it will come.

    Unfortunately it may come late in the professional realm probably after scandals break. Employers using recall data to investigate staff for example - it’s bound to happen eventually.

    My own organisation, a huge health organisation, has opted in to CoPilot. It’s crazy in my view, even if our data is ring fenced in some way. I don’t want private patient information being used to train Microsoft shitty tools, or stored on their servers. Regulation and the law is way behind when it comes to this stuff.






  • Is there a reason you gave /var it’s own partition? Or is the problem that your entire root file system is full?

    As others have said if you have a /var partition, resizing should fix the problem but the other solution would be to migrate the contents back to your main file system partition. Presumably at present there is a symbolic link folder pointing to your /var partition? Copy the /var partition contents into a new folder then boot in to recovery mode and delete the symbolic link and rename the new folder to /var. However presumably you have a good reason for splitting /var out.

    If you don’t have a separate partition then the issue may be your root system itself is full and that partition needs resizing if possible or cleaning our to make space.

    Finally, Flatpak does also use the /var directories in the home users folders (it uses this for single user installs of software vs system wide installs). It’s possible it’s axtually the home folder/partition that is full and that needs resizing or cleaning out to make space .