Hot answers tagged

8

Thanks for shareing your experience. I will start looking through the tags right now and list suggestions here. Unfortunately, there is no member with the merge-tags privilege yet. Issues identified so far: contracts and smartcontract should be synonyms smartcontract should be renamed to smart-contracts (discuss) statetree should be renamed to state-tree (...


8

You can do it in the following way: gnu-linux. As spaces are taken as delimiters for tag creation, gnu linux would be parsed as two different tags. So, include a hyphen between the words, and you'll be all good!


5

I looked at the api tag today, in a hope of CULLING THE HERD, but I had trouble finding targets! There's several which are reasonable questions about the existence of a given API. For example, a python API, or a webhook API, etc. I'm not sure what a new user is supposed to label their question if not "API". Perhaps that could be the use of the API tag? Or ...


4

Additionally to removing it from all questions as Chenmunka suggested, a moderator can fix this directly: The tag can be merged into one of the correct spelling. Let's say somebody created prove-of-stake, and obviously it should be proof-of-stake. When the moderator merges prove-of-stake into proof-of-stake all questions with the former get retagged to ...


4

Quite a few of the listed tags in my question where already removed, but here are some comments on the remaining: development: Since Ethereum is Software, a lot of very different question topics could be tagged development. It's too broad and ambiguous. Suggestion: Replace with more specific tags such as contract-design, or specific software names e.g. geth-...


4

exceptions is better than errors, but neither is a good tag. The problem is that any software can have them and the tags will get stuck on everything from "human errors to errors in any kind of software in the space". I.e. both errors and exceptions only work well if there is another tag that further specifies them. Then it is better to make the tag more ...


4

Agree. Think we may need to add the support to this question.


4

The short answer is no. Apart from the technical considerations, tag wiki excerpts were not meant to simply define what a word means. Excerpts should describe when and how that tag is to be used on this site specifically. If a tag excerpt says something like "C++ is a programming language created in the early '80s by… etc.", you're probably missing ...


4

I have reviewed how these tags are used in practise to see if they can be broken down logically: security could possibly be broken down into consensus, encryption / cryptography, cold-storage, security best practises for node operation, security best practises for client/wallet usage, security best practises for contract design, attacks offline is in most (...


4

Given that other StackExchange sites with similar version issues do exactly this - have tags for each version - I would say yes. Create the version tags you describe. Leave the existing web3js and change its wiki to state that it for version-agnostic questions only. Ideally existing questions would be retagged with the version tag. However, given that ...


3

Singular or Plural tags? we should point out if we want tags in singular or plural. here is a list of tags: Singular dapp ---> rename dapps blockchain ok wallet ---> rename wallets address ---> rename addresses network ok exchange ---> rename exchanges Plural smart-contracts ok transactions ok accounts ok clients ok economics ok nodes ok forks ok ...


3

I think this is like the api tag, which I am also in favor of deleting. What specific question could actually have "protocol" as a meaningful delimeter? If nothing else, protocol-design seems like it would catch many of the related questions.


3

n It's like if stackoverflow had a "program" tag. Nearly every question will relate to a dapp in some way. I'm not sure what exactly you would learn from browsing the tag, or what you would put in the tag wiki, etc.


3

I agree with this and you are correct that SUICIDE is deprecated.


3

I suggest: smart-contracts for general questions on smart contracts. contract-design, contract-debugging and contract-development for special issues while creating smart contracts. dapp for anything broader on the concept of decentralized apps. remove debugging and development in favour of the more specialized tags mentioned above.


2

To answer the 'remove' part of your question. The system automatically deletes tags that have no questions. This is done by a task that checks every now and again. See this post on SE.Meta. Just remove the tag from all questions and wait.


2

I think this is a distinct category of things that we will probably keep running into. In my industry we call the peocess of making third-party widgets talk to each "Integration" so when there is a clear purpose in someone's question where they take a component like BTCRelay, or Maker's DAI stablecoin, I would think a tag like "Contract-Integration" would ...


2

The use of contract-design and contract-development seems to be more appropriate for the development of a smart contract. And I make a suggestion: We can use contract-development also to refer the debug, so in that way we delete the debugging tag currently working in the site.


2

I generally agree with your suggestion, buy we may continue to get a variety of those tags. Thanks for using my example - lol.


2

As this has been done (status-completed tag), I'm answering this question so it doesn't appear on the list of unanswered questions. If someone can accept this answer it then it will disappear from that list!


2

No problem. I renamed the tags. There are no synonyms needed for this use case. Text completion will show users the correct tags. deni → denial-of-service


2

Since also Christian Reitwiessner in his most recent post also refers to state trie pruning, I would suggest to rename the tags using the term trie. The wikipedia entry also explains why trie is the more correct term. Update: Tag is now state-trie-pruning.


2

IMHO, the network is Ethereum Classic, the currency Ether Classic, and the ticker ETC. (Or ETHC, but that didn't seem to make it as a symbol.) I think the tag should be ethereum-classic. I don't think we would tag a bitcoin question btc.


2

Well, ETC is the most commonly used name that I've seen on the Etherium Reddit: https://www.reddit.com/r/ethereum/ as well as most pool and exchanages that I've ssen. I'd assume that we'd want to keep it at ETC as well. And I think just tagging it with ETC should be sufficient.


2

This post is a community wiki. Start editing tags, writing descriptions, adding wiki entries and update this list along the way. If every user updates one tag per day, we will be done in a week. We all love reputation and credits, so feel free to add your name behind a tag in the list below (not in the tag wiki!) 156 most popular tags (with at least 3 ...


2

Lets nuke it. The tags contract-design, contract-development, contract-invocation and contract-debugging should jointly cover most usage. Update All uses of the smart-contracts tag are retagged. Now we need to figure out what to do with the contracts synonym and smart-contracts itself.


1

Please name it open-zeppelin (and make zeppelin a synonym) and keep zeppelin-os. Dashes are a useful separator and help your eyes to quickly recognize tags.


1

No. At the current point with less than 100 answers tagged with 'mining' it should not be broken down yet. We should re-evaluate this at a later time.


1

Use with great restraint. It's pretty rare that you actually have to 'feature' a post. The system already has processes in place to raise certain meta posts to the main Q&A. The featured tag was intended to be used for exceptional situations only, typically when timely issue comes up that are of broad involvement of the entire site. But be careful ...


1

Tree is the more general term; trie is a more precise term technically since it's a more specific type of tree... Trie is more nitpicky. I think using the general term, "tree", is better for tagging purposes and is accurate enough.


Only top voted, non community-wiki answers of a minimum length are eligible