Crossposted from https://lemmy.nz/post/38380382

I find posts and comments from Mastodon to be almost unreadable because they are loaded with hashtags in-line with the content.

Would it be possible to strip those out when viewed through Piefed?

New posts should be in a general, catch-all section. OP could suggest a community/tag but it wouldn’t appear there right away. Other users can tag the post for a particular community or label it SPAM/Troll/Abuse.

If enough users tag a post for a community, it shows up in that community feed.

New users can’t tag until they reach a threshold of comments/posts that are positively received—not SPAM, has upvotes, replies.

This will enforce a level of moderation even when the community mods have ghosted.

There would be no cross-posting per se. Posts could be tagged for multiple communities but must reach a certain amount of tags for each community before it appears there.

I find the inclusion of every federated instance in ‘All’ fairly annoying. New tiny/niche/vanity instances get added by default when federated. There ends up being too much duplication and stuff I’m not interested in.

I’d much rather a system that only includes the local instance by default with a way to discover and add other instances.

My instance block list is long but there’s always new instances to block. For me, this a design flaw of the fediverse.

I locked up a vampire. While chained he was struck with melancholy. I released him but kept him locked in his cell. I had to deconstruct the chain to get him actually released. So, alone and struck with melancholy he wraps himself in the chain that bound him.

Crossposted from https://lemmy.dbzer0.com/post/62518932

As evidence, the lawsuit cites unnamed "courageous whistleblowers" who allege that WhatsApp and Meta employees can request to view a user's messages through a simple process, thus bypassing the app's end-to-end encryption. "A worker need only send a 'task' (i.e., request via Meta's internal system) to a Meta engineer with an explanation that they need access to WhatsApp messages for their job," the lawsuit claims. "The Meta engineering team will then grant access -- often without any scrutiny at all -- and the worker's workstation will then have a new window or widget available that can pull up any WhatsApp user's messages based on the user's User ID number, which is unique to a user but identical across all Meta products."

"Once the Meta worker has this access, they can read users' messages by opening the widget; no separate decryption step is required," the 51-page complaint adds. "The WhatsApp messages appear in widgets commingled with widgets containing messages from unencrypted sources. Messages appear almost as soon as they are communicated -- essentially, in real-time. Moreover, access is unlimited in temporal scope, with Meta workers able to access messages from the time users first activated their accounts, including those messages users believe they have deleted." The lawsuit does not provide any technical details to back up the rather sensational claims.

On the web, I see no downvote buttons on posts. In third party apps, downvoting does nothing. This affects all instances.

Comments are not affected, just posts.

Any idea what causes this?

The past couple of weeks I’ve noticed a lot of sites redirect to report.error-report.com if you have an ad blocker. Reader mode is broken, too. The sites constantly reload when in reader mode. Is this a new anti-ad-blocker technique that my ad blocker just hasn’t caught up with, yet?