Fair point. Though if nothing else stripping out usernames from vote counts would maybe save some bandwidth or database queries for the instance.

I wrote a script that does just this.

People raise a good point that in countries where political dissent can actually be dangerous, this would very much dissuade people from voting on things they believe in, or even coming anywhere near Lemmy period.

A better approach I think would be to have the user’s host instance save their votes (the database obviously needs to remember what you voted on), but when federating those votes with other instances just hand over a cumulative total, e.g., “here on vlemmy.net we have +18 votes for this comment”, which the other instances can then add. There’s no need to send user information with that data.

Also just received this error.

18:00:42.092 XHRGET
https://vlemmy.net/api/v3/post/list?page=1&limit=40&sort=Active&type_=All&auth=keyHidden
[HTTP/1.1 400 Bad Request 0ms]

	
GET
	https://vlemmy.net/api/v3/post/list?page=1&limit=40&sort=Active&type_=All&auth=keyHidden
Status
400
Bad Request
VersionHTTP/1.1
Transferred0 B (29 B size)
Referrer Policyno-referrer-when-downgrade
Request PriorityHighest

    	
    alt-svc
    	h3=":443"; ma=2592000
    content-length
    	29
    content-type
    	application/json
    date
    	Tue, 27 Jun 2023 17:01:07 GMT
    referrer-policy
    	no-referrer-when-downgrade
    strict-transport-security
    	max-age=31536000; include-subdomains;
    vary
    	Origin, Access-Control-Request-Method, Access-Control-Request-Headers
    x-content-type-options
    	nosniff
    X-Firefox-Spdy
    	h2
    x-frame-options
    	DENY
    x-robots-tag
    	none
    x-xss-protection
    	1; mode=block
    	
    Accept
    	*/*
    Accept-Encoding
    	gzip, deflate, br
    Accept-Language
    	en-GB,en;q=0.5
    Connection
    	keep-alive
    Cookie
    	jwt=[hidden]
    DNT
    	1
    Host
    	vlemmy.net
    Referer
    	https://vlemmy.net/?dataType=Post&listingType=All&page=1&sort=Active
    Sec-Fetch-Dest
    	empty
    Sec-Fetch-Mode
    	cors
    Sec-Fetch-Site
    	same-origin
    User-Agent
    	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/114.0

Seems to only happen when I open the Local/All feeds; Subscribed is fine.

The only official way is for the admin of your instance to defederate from the instance you want blocked, but that affects every registered user on your instance, even if they’re against the action.

I just released a user script that lets you block instances yourself on the client-side as a regular user - basically just removes post and comments from the HTML if they match your block list.

Cool, and thanks for posting the update!

This means you’re targeting these classes/ID’s at your own peril, and they may break in a future update.

Me who’s just released a script using CSS selectors:

See my edit to the above comment, I misunderstood at first.

Yep I’m hoping we get more user-level control over the instances we see. This script is a naive client-side approach of just removing the HTML nodes of matching posts, but having it done on the server side would be ideal.

Nope it can block other instance’s communities. This script will block all posts at an instance level though, rather than having to keep adding blocked communities when people create more on that instance.