> I really wish the people who put so much effort into software like OpenWRT would put some of that effort into managing multiple devices in a nice, unified manner. The tooling could be so much better.
There is OpenWISP: Leveraging Linux OpenWrt, OpenWISP is an open-source solution for efficient IT network deployment, monitoring & management.
240V AC and 5V DC manage to live close in a charger without problems. Problems with quality does not depend on voltage.
I love the concept of PoE with one exception that it requires constant 1W or similar load to work even if it is not needed for low power device.
> 240V AC and 5V DC manage to live close in a charger without problems.
I mean, yes and no. My laptop case is at 78VAC to ground right now. It gives the tingles. I don't use my laptop much while plugged in. They all skimp on making proper 3-pronged chargers these days. My desktop has a grounded case and doesn't have this issue.
My phone, when plugged into wall AC, the touch screen stops working because the whole phone is at an elevated potential and it messes up the capacitive sensing.
> * A microsoft account is only needed for Windows 11 Home. A "semi-power user" is hopefully not using that edition of Windows...
Both Home and Pro require Microsoft account to install and start using. Then you can create local only users in both editions and delete user joined to Microsoft account. This is standard operation even in OEM installs.
Pro does not. We only use Pro and Enterprise, and Pro certainly does not actually require a Microsoft account (as of last week, anyways). The options given do make it appear to be required, but it is not.
Neither Home nor Pro really require a MS account. You can skip that during setup (for example with "bypassNRO"). This might change in the future, but as of 25H2 the workarounds still work.
This is the ISO I used, which, according to the MS website[1], is still the latest right now: Win11_25H2_English_x64.iso (SHA256: D141F6030FED50F75E2B03E1EB2E53646C4B21E5386047CB860AF5223F102A32)
I installed it offline in a VM, Home edition, US region. Shift+F10, oobe\bypassnro worked (with a warning/error at some step, but the local account was created fine). I read somewhere that it doesn't work if you connect to the internet during setup (which is always a bad idea IMO).
I've used Active Backup and never would have guessed it worked like that. Although, the MS365 security and permissions are so complex that I don't have a hope in hell of understanding them. The suggestions to do your own auditing in that post are moot because the target audience for something like a Synology doesn't have the resources or the ability to do that kind of assessment.
For me, I saw the permissions request along with the 'Synology Active Backup for MS365' app registration in my tenant and assumed everything was local to my tenant and NAS. The redirect back to the private LAN IP of the NAS also makes it seem like the communication is between the NAS and MS only.
I can't even tell if the issue has been fixed.
Ignoring the security stuff, my experience with Synology Active Backup for MS365 as a product hasn't been good for OneDrive backups. I have one setup where I reconcile the backup repo against a live (paused to get a consistent point in time) data set that's synced by the OneDrive client.
The Synology Active Backup for MS365 never reconciles correctly. Some files will randomly have things like '(1)' appended. Some files are simply missing. It seems to struggle with certain characters that Windows and OneDrive allow in filenames. For example, dots (.) appear to be problematic.
I monitor it and once it gets to the point where I think we'd suffer an intolerable amount of data loss if needing to restore, I delete it and restart it.
I would strongly encourage anyone relying on it to take the time to reconcile your OneDrive backups against a set of known good data. Pause your OneDrive syncing, restore the backup into a temporary folder, and use something like Beyond Compare [2] to compare the two directories. You can also map a network drive directly to storage location on the NAS which makes it very convenient to reconcile.
VEEAM used to have the same kind of issues with files missing for no reason, but they seem to be better lately if you ignore the way they append the version number to name of every (versioned) file restored (OMG why?). VEEAM has very slow restores and is much more difficult to reconcile due to the modified file names on restore.
Microsoft won't take responsibility for data loss "in the cloud" and the backup solutions all suck pretty bad IMO. Some of the blame for this kind of thing should fall to Microsoft. They've made everything too complex to be reliable.
Yes it is not perfect. At least in Lithuania you can use government issued personal ID to sign PDFs that pass Adobe/Foxit checks of signature authenticity. Trusted timestamp is part of a valid signature as it allows to check validity of signee certificate at the time of signing.
Adobe says:
Source of Trust obtained from European Union Trusted Lists (EUTL).
This is a Qualified Electronic Signature according to EU Regulation 910/2014.
Foxit says:
Source of Trust obtained from European Union Trusted Lists (EUTL).
This is a Qualified Electronic Signature according to EU Regulation 910/2014.
reply