Now that v5 is requiring a closed tag system, which I appreciate, I believe it is time for a proper tag editor system should be built (at least a plugin, if trying to push v5 out). Paying $30 for one in a marketplace that is now closed and that has known bugs with elastic search enabled should not be our only option. Even an API would be something, although not the best method for many administrators. I have 720 tags that need to be entered, maintained, and viewed, and you can see how tedious that would become.

I just remembered v5 cannot use plugins... But I think you all get the point.

Edited December 31, 2024Dec 31 by Code Name Jessica

v5 doesnt use plugins, but that doesnt mean the ability to modify has gone away. It mean they simply need to be created as applilcations.

You appear to have asked for something here, without providing any details as to what you are actually asking for.. You would need to ask for specific features to be added, rather than "a proper tag system" 🙂 

9 minutes ago, Marc said:

You would need to ask for specific features to be added, rather than "a proper tag system"

Yeah, you are correct. Honestly... I think it could be extremely simple. Import/Export probably CSV would be the most understandable for most people. But I think there should be something a little more. So, let's say I have 1872 tags in a csv. I need to change 1 of them, or just add 1, I can edit the spreadsheet, make my changes, and reupload. That way I don't have to have a series of different csv.

Generally speaking, with the way the new tag system works, we'd not encourage 1800 tags.

What do you use tags for?

2 hours ago, Matt said:

What do you use tags for?

Yeah. I turned them off. To answer this question, that would probably be too hard to explain what goes through my mind. Honestly, I have no idea, I created a script with several base words: ("programming", "system admin", "development", "scripting", "cli", etc...). Then I added action words: ("help", "pay", "question", etc) and finally I added assist words: ("guide", "tips", "document", etc)

This script would then concat each of these into:
programming
programming help
programming guide
programming help guide

This caused an output of 1800 words: Here are a few base words, then imagine adding each of the action and assist words (which there are about 20 action, and 12 or so assist):

academic
administrative
ai
android
app
application
arch
automation
backup & recovery
bash
best practices
blog
c
c#
c++
career
cd/ci
centos
certification
challenge
cloud
cloud administration
coding
community
comparisons
compliance
containers
cotd
css
cybersecurity
data science
database
debian
deployment
development
devops
discussion
distribution
distro
embedded
enterprise
fonts
forensics
frameworks
game development
gem
general discussion
girls who code
go
governance
gui
hardware
hiring
html
iac
incident
incident response
infrastructure
ios
iot
iot
iot help
iot requirements
java
javascript
job
job board
julia
kali
kotlin
kubuntu
linux
linux servers
lounge
machine learning
macos
matlab
meet and greet
mentorship
mint
mobile
mobile development
mobileos
monitoring
networking
nosql
open source
opensuse
operating systems
optimization
pen test
penetration testing
performance
perl
php
pipeline
plan9
popos
powershell
professional
professional development
programming
python
pytorch
r
rails
response
retro
reviews
rhel
rocky
ruby
scala
scalability
scripting
security
server administration
software
sql
sql
sql help
sql requirements
support
suse
swift
system/low-level
tensorflow
threat
threat intelligence
tips
tools
training
trends
troubleshooting
ubuntu
unity
unix
unreal
virtualization
vm
vulnerability
web development
windows
windows server
women in technology

 

I guess my overall thought was if they had the forum in list view, they could filter by tag words. (Just thought of that when I went looking)

Edited January 3Jan 3 by Code Name Jessica