fmstrat

An interesting tidbit from Mozilla's latest privacy release (https://www.ghacks.net/2023/11/21/firefox-120-ships-today-with-massive-privacy-improvements/):

The first introduces support for the Global Privacy Control in Settings. The privacy feature informs websites that you visit that you don't want your data sold or shared. It is legally binding in some states in the United States, including in California and Colorado.

What's to stop users from utilizing a VPN exit point in California or Colorado to force the binding nature of the request?

Hi all,

I'm not sure how/where to report something like this. I conducted a change of address on USPS.com, and they partner with MYMOVE to handle Voter Registration. However, instead of sending me my VR form, they sent me someone else's, which, considering the "password" was the new zip code, leaves that individual's name and address information exposed, and thus potentially my own to others.

While I have reached out to MYMOVE including requesting any PDF generation and/or delivery of my information, who should I reach out to for reporting something like this?

Thanks.

So I'm doing some testing of USB-C cables using a tester and a constant load (I'll have another post soon with some questions on this). But before running each test, I'm checking the E-mark chip and then enumerating the charge capabilities of each to see what they report being capable of.

I'll use 3 different brands of cables as samples of my question. Power Supply (PS) 1 is an Anker 100W with PPS support. PS2 is a MacBook Pro 94W brick with no PPS support.

• Cable A
  • Emark: 20V@5A USB3.2 Gen 2
  • Max PD using PS1: PD3.0 PPS 29W
  • Max PD using PS2: PD2.0 94W
• Cable B
  • Emark: 20V@5A USB3.2 Gen 2
  • Max PD using PS1: PD3.0 PPS 100W
  • Max PD using PS2: Not tested
• Cable C
  • Emark: 50V@5A USB2.0
  • Max PD using PS1: PD3.0 PPS 29W
  • Max PD using PS2: PD2.0 94W

So the question: What would be limiting Cables A and C to PPS 29W?

As with many others, I've recently needed to do some purging of media in Pict-rs. What I also discovered is that due to an issue with either Lemmy, Pict-rs, or my setup, at some point Pict-rs was not properly removing files from the file system on a purge, leaving about 20GB of media orphaned.

To combat this, I've updated LPP with some additional configuration options to do both direct "purge" of leftover media in Pict-rs not tied to "kept" posts and a forced "remove" of files on the file system that are not properly purged (if using local storage).

You can find all the new options at the GitHub link above.

As a reminder, LPP only removes posts/media older than a specified time if they have not been posted, marked read, voted on, commented on, had comments voted on, or saved by users on your instance.

Hi all, I'm a Lemmy FOSS app contributor that's made a couple of tools for people starting small instances including Lemmy Community Seeder (LCS) for building content on new server's All Feeds and Lemmy Post Purger (LPP) for clearing old posts on smaller instances.

Today I'm releasing Lemmy Defederation Sync (LDS). When launching a new Lemmy instance, administrators may not understand the necessity of defederation with problem instances. Using LDS, you can sync your instance's "blocked instance" list with that of another server(s) whose admins you trust.

I've never had an issue once its set up. Just a 16GB LUKS partition alongside my normal LUKS partition, a small edit to /etc/crontab so I only have to enter the password once, set the RESUME variable, add to fstab, and rebuild init. This method even works with suspend-then-hibernate on every laptop I've used it with.

This would take 5 seconds at install time, but instead you have to install, reboot to the live USB, shrink LV, shrink PV, shrink LUKS, shrink partition, repartition, grow LUKS, grow PV, grow LV, and finally set up the swap partition as above.

Am I the only one? Does anyone else use encrypted drives and hibernate?

Hot on the heels of LCS (https://lemmy.world/post/557346), I bring you Lemmy Post Purger (LPP).

Instances can grow fast, and that can be a problem if you have limited disk space. If you don't mind losing history that your users have not interacted with, LPP can help. It will purge posts along with their comments and media before a certain time period if no comments, likes, or saves exist for users on your instance.

When launching a new Lemmy instance, your All feed will have very little populated. Also as a small instance, new communities that crop up may never make their way to you. LCS is a tool to seed communities, so your users have something in their All feed, right from the start. It tells your instance to pull the top communities and the communities with the top posts from your favorite instances.

How to run manually and in docker is included in the repo.

Let me know if there's anything anyone needs it to do and I'll see if I can fit it in. I'm going to work on a "purge old posts that are unsaved and not commented on by local users" first, since small instances are sure to run out of disk space.

I.E. delete images in the instance that are over X days old and aren't saved by a user?

If not, I will be writing one.