Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

+content tag. #111

Open
ValwareIRC opened this issue Aug 26, 2023 · 5 comments
Open

+content tag. #111

ValwareIRC opened this issue Aug 26, 2023 · 5 comments

Comments

@ValwareIRC
Copy link

Building on #108, +content seems a better choice because it means you can specify custom tag values, including values which indicate the media content is explicitly safe to view, as well as values which indicate other things like gore or whatever.

This allows users to specify their own tags, or suggest tags based on previously seen tags on their network, as the tag values may vary from network to network due to different languages. Essentially these could be considered a similar functionality to hashtags where the user is in control over which custom tags they use and which they want to automatically display or not display.

This allows clients to build a UI which lets people add tag values and choose how/if to display media with certain tag values.

A few examples of this:

+content=sfw,kittens,cute
+content=nsfw,gore
+content=farm,animals,cute,uplifting

Of course clients can have some intuition around meaningful or common tags like nsfw and hide them or not hide them based on user preference.

@GIJack
Copy link

GIJack commented Aug 30, 2023

Oppose. IRC doesn't support inline media.

IRC should not support inline media.

IRC is IRC.

@nektro
Copy link

nektro commented Aug 30, 2023

this feels very overkill for a chat protocol

@ValwareIRC
Copy link
Author

Oppose. IRC doesn't support inline media.

IRC should not support inline media.

IRC is IRC.

IRC already supports being able to post links to media.
Several IRC clients support inline images.

Why should we not be able to know more about the media, and why should we not be able to specify our media as such?

this feels very overkill for a chat protocol

This is using client-to-client tags and is just information pertaining to what the user posted.

@acidvegas
Copy link

The beauty of IRC is the features it lacks in comparison to other social platforms, making its simplicity appealing to those trying to escape the "norm" or social media platforms.

IRC is king due to the fact that it is simply text based. It removes the distractions of a bunch of Memes and YouTube videos etc, and focuses simply on "having a conversation".

I for one am just giving my 2 cents. IRCv3 seems like they just want to turn IRC into Slack to try and modernize it tbh.

@ValwareIRC
Copy link
Author

The beauty of IRC is it can be whatever you want it to be, featureless or featureful. I think it's important to keep up with other messaging apps and protocols, pretty much all of which allow sharing photos at the very least.

What IRCv3 is trying to do is provide extensions rather than change up the protocol, so people who want to run a modern chat with modern features can do so while others are still able to use the exact same software to run a "classic" server without anything modern.

I think it's important to look at other messaging platforms and their different purposes and take the best things and implement them in IRC, knowing that someone out there would like to use those specific features. I think it's also important to note that IRC is open-source and not paywalled.

Anyway, this is not the best place for this conversation perhaps :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants