Really? I live in Lausanne and it’s getting a bit crowded. The buses and trains are completely packed to the point of over flowing, the city as well. Sure there’s a lot of land but that doesn’t mean we need to maximize its use at the expense of the environment and the nature it supports.
Find the TV’s MAC address and block it on your router. My brother home network had this system where your MAC address had to be whitelisted on the router to communicate with the network, as the days go by I see how in hindsight how this might be for the best in the end.
I’m paranoid that actually blocking internet access to the TV will result in filling up the TV’s disk with all of this intrusive data they have collected waiting to be uploaded, eventually run out of space and brick the TV. This could be just bad software or actually malicious where they intentionally break something if it loses connectivity for too long and they can see you using it with other connected devices.
We really need normies to care enough about this to the point manufacturers will need to think they need to advertise on their TVs that they are privacy-friendly and don’t collect anything as a selling point. Until then, they don’t really care. I just wish someone like Apple made a TV with their Apple TV functionality baked in that I could trust.
Lot's of people do it and I haven't seen nobody reporting this. Given the miser hardware specs most smartvs have, if this was a problem, it wouldn't take years to fill up the small storage space most of those TVs come with.
Indeed, but some scoundrel is probably scraping this page and having an LLM prepare their pitch as to how manufacturers could improve Ad / Data collection revenue by bypassing these suggestions :/
I split my network(s) into subnets (sharing the same wire, not to be confused with the actual subnets which don't share the same wire) which correspond to routability policies. This in turn involves firewall rules, routing table entries, and DHCP configs corresponding to those subnets.
I give away the software which does the following. I get this (and a lot more) for every host on my network, and I know what every host is.
I have been using resolve since they added editing functionality (it used to only be for color correction) and I have never had any of those issues. I have the paid studio version and have used it for commercial and private work. It is also a lot less crash happy than premiere which I ditched for resolve and never looked back.
Unlikely. This has been the case on 3 different laptops and multiple macOS versions and Resolve versions.
I use it pretty infrequently nowadays and I admit I didn’t see the startup freeze in a couple months (either I am lucky or they finally fixed it in a recent update), the undo glitch is alive as ever though.
Some other things off the top of my head:
• UI freezes for a second or two when you switch to Fusion tab.
• If you adjust speed in a Fusion node, timeline clip remains the same length, so if you slow it down 2x you can only see the first half. To say Fusion in general is half-baked is to be very, very generous.
• Export location gets reset every launch.
• Can’t copy-paste a node or its settings, in case you want to test between two different configurations.
Even the aforementioned RawTherapee (which is made using Qt I think and which is far from a shining example of usability) is more pleasant to use for me.
Performance, clipboard behaviour, and file browser persistence seem like fairly typical OS-specific issues. Obviously not great if they're not properly testing macOS, but I don't think it's an "even bigger red flag" for those to be OS-specific.
Grouping close-together changes of the same control for undo sounds probably intentional to me, like how Ctrl+Z in a textbox doesn't go one character at a time, and if I move something with arrow keys I'd expect that to be one "movement" once I stop rather than one per key repeat. Whether it's grouping too aggressively to the point of being recognized as an issue is probably down to personal preference, though I would lean towards agreeing that less grouping would be better.
> Grouping close-together changes of the same control for undo sounds probably intentional to me
I explained how it happens. Intentional or not, it just takes us between buggy software and poorly designed software and even then losing changes (not all of what is undone is redone and you are left in an inconsistent state) remains a bug.
> Ctrl+Z in a textbox doesn't go one character at a time
Retyping text is not comparable to readjusting different fine color controls on different pages of the UI across different nodes.
By comparison, the aforementioned RawTherapee (despite being powered by Qt and looking pretty barren) in fact works more reliably with no such issues, and it’s also cross-platform software that is free to boot.
> The aforementioned RawTherapee has no such issues
I don't mean to claim that the mentioned issues are unavoidable or that some piece of software is more likely than not to have these issues, just that when there are OS-specific issues it's this kind of thing I expect. Clipboard handling is pretty much an entirely different implementation on each platform unless you're using something like Electron that already handles it for you, for instance.
There’s no use case for system clipboard, given it’s a monolithic piece of software that doesn’t allow multiple projects to be simultaneously open in different instances. There’s nowhere else to paste except the same window.
Meanwhile, open-source, non-Electron, multi-platform software that handles copy-paste via system clipboard exists just fine (VCV Rack comes to mind).
There are many things it makes sense to copy/drag-drop between applications. There are cases where you might not need to, but using the system clipboard is still common.
> Meanwhile, open-source, non-Electron, multi-platform software that handles copy-paste via system clipboard exists just fine (VCV Rack comes to mind)
VCV Rack seems to just use GLFW to handle it, but again I'm not claiming these issues are unavoidable or more likely than not to occur. For any given issue with some software, 99% of other software will not have that same issue.
This starts to look like a waste of time and not a useful discussion. There are frameworks and libraries that handle 100% of clipboard OS specifics, and the app in question has no use for system clipboard in the first place. In my experience the app is buggy and a pain to use relative to other software, that’s the entirety of my point.
> There are frameworks and libraries that handle 100% of clipboard OS specifics
They're sufficient in many cases, but you'll still sometimes need the control of working with COM/etc. directly, and those libraries don't fully save you from platform-specific bugs (e.g: https://github.com/glfw/glfw/issues/2644).
> the app in question has no use for system clipboard in the first place
What do you expect to happen when you copy some text from an external editor into a text field?
That’s a terrible analogy because you’re describing bugs and not usage patterns.
• UI freezes for a second or two when you switch to Fusion.
- that’s weird
• If you adjust speed in a Fusion node, timeline clip remains the same length, so if you slow it down 2x you can only see the first half. To say Fusion in general is half-baked is to be very, very generous.
- Again never had this issue
• Export location gets reset every launch.
- It remembers my last export settings per project
• Can’t copy-paste a node or its settings, in case you want to test between two different configurations.
- I have copy pasted many fusion and color nodes without issues
Have you reported these issues to Black Magic?
I have used a lot of editing software like old school Final Cut Pro, premiere, Sony Vegas (yuck!) and even movie maker. Resolve in my opinion has the least amount of friction to use. What do you use to edit?
What I do now can be done using a mix of free software (ffmpeg, etc.) and if I were to go pro and have less time for tinkering then it’d be FCP for me.
Interesting. I’m in the process of making a node based image editor myself so I’ll see what this does right and what points of friction still remain. The main reason I want to do is to make automating tasks easier, batch processing in photoshop is ok, but it could be so much better.
Maybe I’m an outlier but I don’t want my drives encrypted at all. I rather have all my data be accessible if things go catastrophic, I.E. having to pull the drive out of a broken computer and put it in another computer to access the files. I just want it to be plug and play.
Cool. Everyone's threat model is different. As long as we're not writing passwords on sticky notes attached to the monitor, I don't think there's any need to be throwing stones.
Sensitive data written down on a sticky note is arguably more secure than that same data sitting on an unencrypted hard drive, at least in a home setting.
Secure rot* variants require UTF-8 and mappings that shift characters between {1,2,3,4}-byte encoded-character-sizes. That varies the message length, which prevents any message-length or traffic analysis.
The Snowden leaks revealed that the NSA is flummoxed on how to tackle variable character lengths. However, they've cracked rot26 using custom ASIC supercomputers, so it should be considered insecure even though it's twice as good as rot13.
Are you saying you bring your desktop on a train ride as well? Laptops with encryption make sense; if you need to encrypt your desktop, I have questions.
I would. It doesn't even require theft. The naive burglary mitigation is just a happy accident.
I want the crypto-shredding retirement of each storage device. I don't assume I can delete/scrub/overwrite at the time a device goes out of service. I have a box of older HDDs that I still have to get around to destroying properly, because they exist from before the days of practical FDE.
I encrypt my desktop. What if someone breaks in and steals it? My tax returns are on there, banking and investment info, etc. And what if I'm careless about disposing of an internal drive in an old machine that's in the closet, etc. I usually drill or sledge drives, but what if I forget? Encrypting all drives makes sense.
My inference machine is the only drive I leave unencrypted, but that's because it has the models on it, llama.cpp, and nothing else, and I want it back up and running services after a power-failure. My other desktops are encrypted to make hard drive disposal easy.
Simple hypothetical: "A disaster hits and the workstation owner is unable to return to the location the workstation is stored. During that time period the workstation is stolen by a gang of looters."
Also a reason to have off-site backups. Many people have done backups to local servers, only to discover that they have no way to recover their data because thieves stole everything.
My data is mundane and mostly my art projects and photography. I don’t believe I am important or interesting enough for someone to do anything with my data if they somehow managed to get it also I don’t have emails, saved passwords, banking info or that kind of sensitive info on my computers so meh I guess.
If "things go catastrophic" your hard drive is not usable at all anymore. At the very least some files can't be recovered at all. So you need backups in any case. Once you have backups, you might as well encrypt your hard drives, especially if you store these in different locations (which you should).
An advantage of encryption is that it makes it easier to give away or resell devices. With recent encryption schemes (well the ones on Linux, given this article), I feel confident that overwriting the encryption keys gets me close enough to not leaking my data once I get rid of an old hard drive.
That’s not true. I’ve had many computers that refuse to turn on and I was able to recover the files by removing the drive and loading it into a USB hard drive reader and recover the files.
Additional problem is if physical access is obtained, illegal material could be covertly added to the drive then picked up by the built in scanners in your OS. Depends on how important you are.
What's not plug and play if using some sensible fde like idk, dm-crypt? You are only a passphrase away from mounting that drive in any other system you plug it into.
That's my question, because my root is encrypted, I move encrypted disks all the time, and have a couple of encrypted external drives. It's trivial.
But I'm sure that some of the millions of things that I've missed as windows has become what it has become makes this simplicity seem like a scifi absurdity. I don't think that they can even log into their own computers without asking Microsoft for permission over the network. I'm sure the idea of encryption must have been overcomplicated to the point of absurdity in order to trap customers too, I just don't know about it.
I suppose you should just count your blessings (of ignorance) and be available to help your friends with cryptsetup if they decide to flee windows.
* Split the recovery key in two, store each half with a different friend. (If you're feeling fancy, XOR the halves and store that with a third friend, then any two out of three will work.)
* Sneak the key into something you know friends/family won't throw away while you're still alive, like stuck to the back of a sentimental photo in a frame.
____
That said, I think I'm wandering from the original "accumulating dusty old drives in a box" scenario, which has a simpler solution: Keep a growing old_drives_keys.txt file on your current (encrypted) main device.
Yep, this is the way. It survives human memory and doesn't depend on software.
If you keep it in a dark environment that's not super humid the ink should last a really long time. Even in non-optimal conditions (NY summers with high humidity, etc.) I've had regular pen ink last for decades with no signs of fading away.
Same here. If anything happens I want a decent chance to be able to recover my data. The most I may do is create encrypted files, and some of them I've forgotten the passwords for, which makes me even more wary.
I was happy to give up my side-hobby of drilling drives after FDE became standard everywhere. Plug and play is great, but you don't want it to be plug and play for whoever pulls your drive out of the trash.
I mean... you can use an encryption scheme compatible with this (if you know the password).
I suppose this makes some sense for home computers (burglars and police raids are rare) but for a laptop, you really don't want thieves getting all your details.
Ironically -- this probably was paranoid a few years ago, but now -- "ChatGPT, use this prepared prompt to extract all useful info from this hard drive"
reply