Going to https://gui.fediseer.com/instances/censured and clicking the 'Filter' button without typing anything into the text field causes an error message saying "Error There was an api error: undefined" to appear. You can keep doing this to make as many error messages appear as you desire.

https://gui.fediseer.com/instances/censured

Currently someone anonymous can only see the reaosns, but no receipts

Likewise, instance details should provide the receipts along with the censures: Example: https://gui.fediseer.com/instances/detail/1611.social

Some subpages don't have a link to the glossary yet and maybe we should adjust that

as an example, I noticed the following when translating:

"app.guarantee_restricted.info": "You can do this only if your instance is guaranteed by some other instance.",

it seems that the button is not loaded reliably when the list is very long.
Maybe a problem with the cache?

Introduction

Synchronization feature is a very good tool for many instances. But it has some flaws.

For example, not every instance blocks any other which is considered "bad", but still wants to use benefits of community-driven moderation lists. Some just limits them leaving their users a freedom of information and ability to still manually follow users from the "bad" instance.

So here's an idea: list mapping.

Examples

So for example you can set your own sync profile by selecting sanctions and strategies for fediseer list. For example:

Sync settings 1 (default):

Sync setting 2 (custom)

Sync setting 3 (custom)

Explanation

Strategies

• overwrite - completely synchronizes all data with fediseer by overwriting existing list entries on the instance
• merge / append only - adds entries which do not currently exist in the list on the instance
• merge with deletion - adds entries which do not currently exist in the list on the instance, but also removed entries which were previously synchronized from fediseed, but removed after that
• some other strategies with another direction priorities for example

Instance sanctions

• Limit - removed content from such instances from public timelines, but allows users to follow users from limited instance
• Suspend - completely disables any interaction with users from suspended instance
• Reject media - do not sync media from remote instance
• Other domain block options which are currently present

It would be a good feature to enable admins/moderators to search for an instance in the GUI. It will come in useful when looking for receipts while vetting a server for potential blocking.

It would be great if in the "Synchronization from Mastodon to Fediseer" part of synchronization it was possible to choose the mapping of Mastodon limits vs suspends onto, for example, hesitations vs censures, much like it is possible to do in the other direction. My very long Mastodon list has a mix of both and I don't want to import them all as censures.

The user should be able to select if they want to use a PM proxy when claiming an instance, for those software which I haven't developed direct messaging as @[email protected]

The claim instance allows to pass the pm_proxy key as either "NONE" or "MASTODON" currently, but in the future more might be added.

The PATCH on /api/v1/whitelist also allows setting a pm_proxy for the whole instance. This will be stored for the whole instance and will be used for future PMs to all its admins.

Currently in the blacklist syncronization when I add endorsed instances in there to pull blocks from, there can be a community that is blocked that I dont want blocked (e.g. due to rule change in the blocked instance but not everyone has updated their censures accordingly yet)

Adding an input field where you can put domains to ignore for the blacklist would prevent that

When I press Account Switch, I see the following window:

Since there is a lot of whitespace:

You could add some info to that list such as the amount of censures, amount of hesitations and maybe top 3 tags?
lemmy.world - censures: 78 - hesitations: 2 - tags: fascism, unmoderated, spam

Please add the possibility to import block-lists that have been exported from Mastodon.

The exported csv contains the following:

domain,severity,reject_media,reject_reports,public_comment,obfuscate

example:
domain.tld,suspend,false,false,"racism, discrimination, lolicon",true

I suppose we'll only need domain, severity and public_comment for Fediseer.
severity is either suspend (censor) or silence (treat as hesitated?)
public_comment is in the format "free string", and could be treated as "reason 1, reason 2, reason 3"

(referring to https://matrix.to/#/!vzuoKDBMbcFToIJwxv:discuss.online/$E4paE0mlzpYm1sKfeuG0Gy2b1ysIqV22PJ2Rpl-c4R0?via=matrix.org&via=lemmy.world&via=aria-net.org)

The API allows you to see previous entries in the log by using the ?page= query

On the one hand you would know how many you can still spend, on the other hand it would prevent confusion because it is not easily apparent that there may only be 20 pieces.

would it be possible to add filters for the following lists, so that you can search for e.g. a reason?

it would also be cool if you could do this by post so that you can send a filter

instances/censured
instances/hesitated

Fediseer allows admins of censures/hesitates instances to issue a rebuttals to their own defense.

Then allow them to swap between them

The "guarantee" label is causing confusion, because people (including admins!) don't read the docs.

I propose changing the label to "no spam" to make it immediately clear that it's not an endorsement.

it seems it's trying to pull something from the API that doesn't exist, but I'm not sure what

https://a.lemmings.world/lemmings.world/post/2063962

An instance which solicits a guarantee may receive one from an unknown/potentially untrustworthy instance. Ability to revoke may be important, especially in these early adoption days, to avoid larger issues in the future.

Revoking your own guarantee is possible via the API but not yet in the GUI, as far as I can tell.

Method explained here:

Fediseer/fediseer#24 (comment)

Thanks!

I'm trying to claim lazysoci.al but I get "The api returned this error: Internal Server Error "

Reproduction steps: Click on suspicious instances and click on the first result, www.jrz.city. Get taken to https://gui.fediseer.com/instances/detail/www.jrz.city
See this:

Would be nice to have a "one click" option to move an instance from your hesitations to your censures list and the other way around.

Preferably also the same with an instance that is in your guarantees. Maybe add a drop-down list to choose the list the instance should be in so we can easily revoke the guarantee on an instance when it becomes a problem.

The password reset endpoint supports returning the new API key directly to the user (as opposed to PMing it to the admin), by setting "return_new_key": true on the PATCH.

This is used when the admin does not receive the PM for any reason, or if they need to reset it without getting the password stored in their DB

If I set a filter type to something, then put it back to ---, the url becomes https://gui.fediseer.com/action-log/log?page=1&type=null and that causes an error

Hi, isn't an overview page missing for the rebuttal option?
You can send some from your instance but where can you find them?

Similarly to the pagination done on the public pages.

When I got to the sync page to bring the censures into my Mastodon instance, it seems only the first page of blocks is processed, meaning that most blocks aren't even shown as missing on Fediseer and that Fediseer is unable to see the blocks it creates.

In the network panel it also seems like a single request is made, which ends up only returning the first results.

Fediseer API allows one to filter by source instace, target instance, report type and report activity. Would be nice to be able to do that in the gui as well

If I tag to only follow for example "csam" and "spam" this will be ignored for hesitations. Instead the GUI will add all the hesitations.

Example:

• Feddit.uk and Lemmy.one are currently in my censures as "inactive admins".
• For Filter by reasons I fill: "csam"

As you see they are both added in the Preview.

I think it would be quite good if there was a language selection.

On the one hand, you are now forced to use the browser language.
On the other hand, you can find translation errors.

Looking at https://pangora.social/join made my creative juices flow. I am thinking the following

Once Fediseer/fediseer#34 is implemented, create new subdomain (maybe even re-use the pangora source), or a tab on the fediseer: "Join Fediverse"

The list will be populated by our instance list.

1. The first choice: Type: Microblogging / Threadiverse / Pictureblogging (what is the verb for instagram-styl?e) / Videos. With popup explanation of each

2. Second choice: Software: Have a small popup screenshot description of the software next to each choice

   • Microblogging: Mastodon, Pleroma, Firefish etc.
   • Threadiverse: Lemmy, Kbin
   • etc

3. Third choice: Tag cloud: We provide a clickable tag cloud on the top (or perhaps a better way to display tags). On the bottom, we provide the list of guaranteed instances which have all the selected tags assigned, ordered by descending order of endorsements. When a user selects a new tag, the instance list below is re-filtered. Eventually the user should pick one of the instances below, which will direct them to that instance's frontpage.

1. I add an intance to my Exclude list:
   
2. I press synchronise
3. The list is empty again:
   

Would be nice to add a hyperlink to the fediseer frontpage on the Glossary: https://fediseer.com/

Likewise a link to the devlog announcing it would be nice: https://dbzer0.com/blog/overseer-a-fediverse-chain-of-trust/

Currently there's almost no caching of data and stuff is needlessly fetched over and over.

• lemmy.one is currently in my hesitations

I'm not sure if it's the same for hesitations from other instances as I can not see the difference here.

Just an idea to help people notice there's instances asking for a guarantee.

Now and then poll the solicitations in the background. When a new one is found, put a short-lived popup that asks the user to take a look at new solicitaitons

The popup should not appear if the user has maxed out their guarantees (so, dependent on me adding Fediseer/fediseer#31 first. The popup should not appear if you have the instance hesitated/censured.

Perhaps to filter it a bit more, have the popup only appear if the solicitating instance is not censured/hesitated by any of your instances's endorsements either.