So, mission accomplished?
Customers enduring the long wait for their T1 phone from Trump Mobile might have also had their personal data exposed on the carrier’s website.
TrumpMobile.com apparently contains an exploitable software flaw that can leak data, including emails, physical addresses, and full names, according to YouTubers Coffeezilla and Cr1TiKaL. ……
I wonder if they do it on phones as well. Not everyone has a 256GB+ device, and 4GB would be a significant chunk on even that.
Yes Google intended to stop sideloading but is facing backlash.
Unbuffered ECC DIMMs can be used as-is even on PCs not supporting ECC
Registered DIMMs can be unsoldered and the RAM chips reused in a pinch converting them to unbuffered DIMMs I suppose?
But reports of manufacturing capacity being moved to HBM will not benefit consumers if the bubble bursts.
(The original article is Japanese, here is the first paragraph translated by Microsoft Copilot.) (Wayback Machine link for geoblocked users)
NEC has developed the world’s first walk-through multimodal biometric authentication technology that combines facial recognition and iris recognition, designed for scenarios requiring strict identity verification such as airports and payment systems. By integrating its facial recognition and iris recognition technologies, NEC enables high-precision, high-speed authentication of users while they are walking, both indoors and outdoors. Since authentication cards and other physical items are unnecessary, users can pass through hands-free, helping to ease congestion and enhance security. NEC plans to conduct demonstration experiments during fiscal year 2026, aiming for practical implementation in fiscal year 2027.
Also: Link to NEC’s Japanese Press Release
I am trying to set up a home server. Here is how I’m planning to do it:
/dev/nvme0n1 SSD, Proxmox, VMs & CTs
/dev/sda HDD, Media library
/dev/sdb HDD, Backup
I’ve installed Proxmox on the NVMe SSD and created a few VMs and CTs to play with.
I have also partitioned /dev/sda and created a ZFS partition on /dev/sda1, made a pool /pool and a datastore /pool/data.
I plan to put media files on /pool/data, bind mount it on a container and run Jellyfin to serve them.
I can schedule backup jobs for the VMs and CTs themselves on Proxmox, but I’m not sure how to backup the media files on /pool/data to /dev/sdb.
How would one go about setting up such backups? Do I need to setup something like a cronjob with rsync or is there some easier ready-made solution? Ideally it’d be something like Proxmox’s VM backup jobs that let me prune and keep some copies daily / weekly / monthly / yearly.
What filesystem should I use for the backup drive / partition? Is there advantage of using ZFS to backup ZFS?
Can ZFS snapshots be used on /pool/data for additional protection? If so how do I set up, for example, automatic daily snapshots? Do snapshots take up little space if the files rarely change?
Thanks.
Lemmy.world and piefed.social are two different instances (servers) run by different people. They also run different software (Lemmy and Piefed respectively) which speaks the same protocol and can talk to each other (and other instances as well).
If you look at the same community e.g. !fediverse@lemmy.world under each instance the content should be the same: the protocol should ensure that. The interface, the way it is presented to you, might be different, mostly decided by the software (Lemmy or Piefed, or any reader client you use).
It is also possible some posts or replies made it to one instance but not the other, perhaps due to technical problems, or policy (one instance’s admin might decide to not federate with another), but you should not encounter it very often (but it certainly happens).
People choose one instance over another for different reasons. Perhaps they like one software’s interface better than another. Perhaps they feel one server is faster and more responsive than another. Perhaps they would like to subscribe to a community which is blocked by certain instances. Fortunately there is nothing to stop somebody from signing up at multiple instances, so one can just try each out and find out which one is suitable for them.