AwesomeLowlander

joined 2 days ago
MODERATOR OF
[–] AwesomeLowlander@cozyver.se 1 points 1 minute ago

I'm only pointing out the optics of it aren't great. I do agree Pylova doesn't have a monopoly on a feature just because it implemented it first.

[–] AwesomeLowlander@cozyver.se 1 points 8 minutes ago

There are 3 possibilities:

  1. By accident. That would mean Rimu didn't know about the existence of Pylova's blocklist feature. Lets not go down there.
  2. Forced / without choice. Because he wasn't capable of doing it, or somebody held a gun to his head.
  3. Deliberate. He made a conscious choice to do so. Whether because he felt another approach was preferable, easier, w/e.

You seem to be conflating 'deliberate' with 'malicious'. Those are 2 separate things. Read my original statement again without projecting any of your assumptions onto it.

[–] AwesomeLowlander@cozyver.se 0 points 1 hour ago* (last edited 1 hour ago) (2 children)
{
  "@context": "...",
  "id": "https://example.org/blocklist/general",
  "type": "OrderedCollection",
  "name": "General Blocklist",
  "summary": "Description of the list",
  "attributedTo": "https://example.org/u/admin",
  "published": "...",
  "updated": "...",
  "totalItems": 2,
  "first": "https://example.org/blocklist/general/entries?page=1",
  "inbox": "https://example.org/inbox",
  "visibility": "public",
  "subscriberCount": 10
}

The feature is nothing more than shared basic JSON data. If your thrust is that Rimu is too incompetent to handle that, I don't really think so, but I can accept that too.

[–] AwesomeLowlander@cozyver.se 7 points 11 hours ago (12 children)

You have to admit, deliberately breaking compatibility with Pylova's identical blocklist feature isn't the best look though.

[–] AwesomeLowlander@cozyver.se 1 points 11 hours ago* (last edited 11 hours ago)

LLMs aren’t built for that, for that you’d be a statistical or probability model AI.

Pretty much all current gen LLMs have that capability. They've gone a long way past being just language models.

[–] AwesomeLowlander@cozyver.se 6 points 11 hours ago

Imagine how many new images he could add to his spank bank for that money!

[–] AwesomeLowlander@cozyver.se 2 points 11 hours ago

Yeah, it's practically a stereotype now that they're all great singers

[–] AwesomeLowlander@cozyver.se 1 points 12 hours ago

That I'm not too sure about, but either way it's possible, just a few clicks away.

[–] AwesomeLowlander@cozyver.se 1 points 12 hours ago (2 children)

It sounds like what you want is already available? As I said, you can pick and choose categories when you subscribe to a blocklist

[–] AwesomeLowlander@cozyver.se 1 points 20 hours ago* (last edited 17 hours ago) (4 children)

You have a point. Are you suggesting that for list creators as a voluntary way of organizing, a hard limitation imposed technically, or something else?

Also, note that when subscribing to a list you can choose to enable/disable categories of users, comms, instances, and domains.

[–] AwesomeLowlander@cozyver.se 12 points 1 day ago (3 children)

Come to the Philippines, where every home has a karaoke set.

[–] AwesomeLowlander@cozyver.se 15 points 1 day ago

'GTA goes woke'

 

Violence

Purpose: Filter accounts that frequently call for violence and communities that frequently feature violent subject matter.

Include:

  • Accounts that repeatedly encourage or call for violence.
  • Communities dedicated to violence, violent incidents or graphic depictions of violence. This includes documenting and discussing violence, even if they are against it.
 

I used up my quota of words on the sidebar already :)

 

Unpleasantness

Purpose: Filter accounts and communities associated with consistently unpleasant, hostile, or toxic behaviour, interactions and content.

Include:

  • Accounts that are repeatedly hostile to other users, including personal attacks, harassment or deliberate provocation.
  • Communities where hostility, ridicule, antagonism or outrage are recurring features of their culture.
 

!blocklists@cozyver.se

A place to share and discover Fediverse blocklists

Welcome! This community is for sharing, discovering and discussing blocklists across the Fediverse.

Blocklists can help people shape their own online experience by filtering accounts and communities that don't align with their interests, preferences or the kind of environment they want to participate in.

An important note: Blocklist subscription and sharing functionality is currently a PyLova-specific feature. This community is therefore particularly useful for PyLova users and instance administrators, although anyone interested in blocklists and content filtering is welcome to participate.

Feel free to share your blocklists, announce updates, discuss ideas, ask questions, exchange experiences or simply introduce something you've found useful. Whether you're creating and maintaining lists or looking for ways to customise your own experience, you're welcome here.

We encourage list maintainers to explain what their lists cover, how entries are selected and how frequently they are reviewed. Transparency helps people make informed decisions about what they subscribe to.

Blocklists are personal filtering tools, not universal declarations about who should or shouldn't be part of the Fediverse. Different people have different preferences, and that's perfectly fine.

The goal is simple: make it easier for people to discover useful blocklists and shape their own Fediverse experience.

Community Rules

1. Be clear about your blocklist.

Describe its purpose, intended scope and inclusion criteria. Explain the types of accounts and communities it covers, and the behaviours or content that qualify for inclusion. This helps people understand what they're subscribing to and decide whether the list aligns with their preferences.

2. No targeted harassment or brigading.

Blocklists should help people manage their own experience, not serve as tools for organising harassment, directing attacks or encouraging others to target specific users or communities.

3. Be open to corrections.

If an inclusion is challenged with relevant information or evidence, list maintainers are encouraged to review it. Entries that no longer meet the stated criteria should be reconsidered.

4. Instance rules still apply.

All Cozyverse instance rules and policies apply in this community, in addition to these community-specific rules.

view more: next ›