EYERCORD

1. Server Name - The server name should be easy to remember, easy to read, and preferably include only regular letters. If the name is complicated, then most likely even those who saw your advertisement will not remember it, which means that they will not be able to remember your server to find it again or recommend it to friends. Also avoid using "decorative" symbols. Such symbols are not available on the keyboard of any device, so the user simply cannot enter them in the search, and the search algorithm will not be able to correctly index your server due to the fact that it will not be able to break your name into words that users use in search queries.

2. Server description - the server description should look like a small, short essay about what your community has that others do not, features, etc. If you are looking for an audience on a narrow topic, you should add to the description who your server is aimed at. Avoid links to external resources in the description. Links are not clickable in the description, interfere with perceiving the main part of the description and can be perceived as spam. It is also advisable to use literary words and not use obscene language. Users do not often search for communities using such words, so such text is not useful. Instead, try to include as many keywords (tags) that are relevant to your topic as possible, by which users can search for communities similar to yours, but be careful that the text remains readable, which means that it should be read as a regular publication and not a set of tags. Descriptions that are spammy to search algorithms can lead to blocking the community on the platform.

3. Tags - use the tags that are offered by the platform at the stage of adding a server. This will allow you to get a position in the category for a specific tag where the competition is lower than the general top. But choose only tags that really relate to your community. Spamming with tags can lead to blocking the community on the platform.

#catalog_promote_tips

Fixed!

Our network is currently experiencing some issues and errors may occur.

There are currently issues with the EYERCORD Catalog Bot when performing interactions due to instability in the Discord API.

Turkey bans Discord.

Source: Wumpus Central (Discord Guild)

EYERCORD Catalog is now online!

EYERCORD Catalog is down for maintenance.

We are moving our database to a new location. We expect to be back online at October 5 12:00 PM PDT

If you have problems with some functions, reset the browser cache on your device or activate VPN.

On Windows or Linux: Refresh page via Ctrl+Shift+R hotkey
On Mac: Refresh page via Command+Shift+R
On iOS or Android: use InPrivate/Incognito mode

Recently, bots have been found in Discord communities on user accounts that log all messages and media content. This is especially true for popular communities.

We remind you: do not publish personal information in public chats - other people do not need it, and its leak can also harm you.

If you are a community owner, notify your members about this and check for suspicious accounts on the server, as well as users available in EYERCORD Blacklist and/or similar databases. This will help to weed out bots and unwanted users who have already been noticed for harmful activity.

We have completed the migration of Blacklist service media content to our content delivery network (CDN). Most of the media content has been migrated. Some media content could not be migrated due to closed access, deleted files, closed hostings, etc. Such media content will be unavailable and a standard placeholder image will be shown instead, informing about the media loading error.

All new Blacklist media content will be delivered from our CDN.

We have already migrated 40% of media data.

We have begun the process of migrating media content in the Blacklist service to our CDN from third-party storages. Not all media content will be migrated, but we are trying to keep as much data in our cache as possible to keep our database up to date. Media content for new reports will be directly hosted on our CDN, but will have a different URL structure than for older reports media content.

Note: media content migration does not include caching and/or migration of user avatars. We will continue to receive this content from Discord CDN.

Fixed.

The core API of our services does not respond to requests for some users. This may affect some features across our different services. We are already working to resolve the issues!