Socials Channels about ethereumclassic.github.io HOT 12 OPEN

@HebeBlock appreciate your comments.

There is no official decision making in ETC, so please don't assume that @gitr0n1n represents the whole community. He is a long time contributor to this website, but like everyone here, is acting individually.

We are not against listing external non-etc branded services, as per the apps section. chainlist.org is not listed in the Social Channels page, and we are now just trying to ensure this page remains consistent.

Now we've reverted the mistake I hope we can settle our differences and continue to work together.

from ethereumclassic.github.io.

My thoughts are it's fine to have a community channel run by hebeblock listed on the page. It may be useful to expand upon the "dont trust, verify" disclaimer for the channel page. Something along the lines of "these chat rooms are maintained by volunteers and community members. insert warning about not trusting, always verifying here"

In future we will want to be extra careful of avoiding a conflict of interest while maintaining. Plenty of room for these projects imo.

from ethereumclassic.github.io.

My thoughts are it's fine to have a community channel run by hebeblock listed on the page.

Of course that was not the initial issue, that should simply be listed elsewhere. The category are general ETC channels on different platforms in different languages.

from ethereumclassic.github.io.

This chatroom was removed due to it being a "project specific" chatroom. This is a hebeswap chatroom, not an Ethereum Classic chatroom. It was not a mistake to remove project specific links that misrepresented themselves as Ethereum Classic chatrooms. Nothing was hidden, one of the first links removed in the PR is literally a "hebeswap.com" url. No other project is afforded listing in this chat list. Otherwise Nova, Soy, Classic DAO (Not my project), all the NFT project chats, all erc20 token projects (memecoins), ... would have a links in there. Why is Hebe special?

      chat WeChat:
        __link: https://hebeswap.com/assets/nanli777.jpg
        name: WeChat (中文)

If we are going to add project specific chatrooms, we should be very clear about it. Then add all the other ETC project chats: NFTS, tokens, development projects. I imagine Hebeswap is heavily promoted in these chatroms due to the two people running the project (hebeswap staff). We don't see this from other teams in the ETC ecosystem and adding these without a clear disclaimer that they are hebeswap chatrooms would be a misrepresentation. No other team is trying to do this and they all have chatrooms.

Additionally, upon review I see content that is questionable and confirms my original thoughts that these chats are promotion of a specific product and not ETC chatrooms.

      telegram China:
        __link: https://t.me/chinaetc
        __icon: telegram
        name: 中文

Example 1: When a user joins. The admin is promoting HebeSwap (This is a chatroom ran by hebeswap)

Example 2: The owner of this chatroom is acting in bad faith and spreading misinformation about other ETC products to elevate their own product.

Example 3: Redirecting chinese users to Hebeswap but saying it is ETC Swap

Example 4: These are mostly paid bot accounts to make it seem like its a "big chinese" community. Just scroll through the chat log. This was August 8th. Its the same group of core-HebeSwap accounts.

Example 5: HebeSwap staff selling a personal narrative on long-standing ETC community volunteers. Is this an ETC channel or a propaganda channel?

Solution: Create chinese channels that are legitimate and not hijacked by a single project with a narrative to sell.

Edit: I'll refrain from participating outside of this comment, as myself and projects I have deployed appear to be the target of the misrepresentation (for financial gain) of the owner of these HebeSwap-specific chatrooms.

from ethereumclassic.github.io.

What I suggest, as a start, is to make permanent invitation links for each existing language to the International Community section of the General Discord so there is already that. Next to that we can add other existing and newly formed projects.

from ethereumclassic.github.io.

@w1g0 I like that suggestion

from ethereumclassic.github.io.

So https://chainlist.org/en/chain/61 is also a product of our team? It's funny, it's just that nanli777 doesn't let you promote your product, he talks to you in discord, hope you don't use the etc name, it makes Chinese users misunderstand it is an official product, and you don't take care of it.

Whether the link is deleted or not, we don't care now, from the initial anger to silence, the community did not pay nanli777 to work, he has been maintaining these channels and solved the problems of users including me, r0n1 hope you can use the product to speak, don't use Despicable means to destroy lose your image in society.

Currently in etc, the hebe team has built the most products. This is undeniable. The listed products are only related to users. Now users need to run the etc client of windows. What would you recommend? I think it will only be etcdesktop.

It's too hard for a normal user to run core-geth and the controller to start the node

from ethereumclassic.github.io.

@HebeBlock please consider rejoining the General ETC Discord, thanks.

from ethereumclassic.github.io.

What I suggest, as a start, is to make permanent invitation links for each existing language to the International Community section of the General Discord so there is already that. Next to that we can add other existing and newly formed projects.

There are several issues with this proposal that need to be addressed:

1. people currently can't enter the server without acquiring the "approved" role.
2. the idea is that people can participate that don't speak English so the rules need to be translated.
3. it wouldn't hurt to have a representative to moderate very lightly or at least warn a mod.

I would suggest applying a "language" role so they don't have access to the whole server meaning they miss out on the announcement channels and Community calls at upon joining, only to the rules in their language and 1 chatroom to start with. Maybe a voice room if it is requested by the community for that language. In fact maybe they can build their own sub-server?

ps: In the rules we can add the procedure to open up the whole server ("approved" role) like a stepping stone.

from ethereumclassic.github.io.

What I suggest, as a start, is to make permanent invitation links for each existing language to the International Community section of the General Discord so there is already that. Next to that we can add other existing and newly formed projects.

There are several issues with this proposal that need to be addressed:

1. people currently can't enter the server without acquiring the "approved" role.
2. the idea is that people can participate that don't speak English so the rules need to be translated.
3. it wouldn't hurt to have a representative to moderate very lightly or at least warn a mod.

I would suggest applying a "language" role so they don't have access to the whole server meaning they miss out on the announcement channels and Community calls at upon joining, only to the rules in their language and 1 chatroom to start with. Maybe a voice room if it is requested by the community for that language. In fact maybe they can build their own sub-server?

ps: In the rules we can add the procedure to open up the whole server ("approved" role) like a stepping stone.

This discussion is revealing that solutions are more a Discord issue than a website issue. Are we in the appropriate venue for this discussion to take place?

from ethereumclassic.github.io.

What I suggest, as a start, is to make permanent invitation links for each existing language to the International Community section of the General Discord so there is already that. Next to that we can add other existing and newly formed projects.

There are several issues with this proposal that need to be addressed:

1. people currently can't enter the server without acquiring the "approved" role.
2. the idea is that people can participate that don't speak English so the rules need to be translated.
3. it wouldn't hurt to have a representative to moderate very lightly or at least warn a mod.

I would suggest applying a "language" role so they don't have access to the whole server meaning they miss out on the announcement channels and Community calls at upon joining, only to the rules in their language and 1 chatroom to start with. Maybe a voice room if it is requested by the community for that language. In fact maybe they can build their own sub-server?
ps: In the rules we can add the procedure to open up the whole server ("approved" role) like a stepping stone.

This discussion is revealing that solutions are more a Discord issue than a website issue. Are we in the appropriate venue for this discussion to take place?

It would make sense to open a new repo to manage the Discord if that is something that @mikeyb supports.

from ethereumclassic.github.io.

Ref #952

from ethereumclassic.github.io.