this post was submitted on 11 Feb 2024
203 points (99.5% liked)
Open Source
31095 readers
491 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There are multiple IRC clients that render inline images just fine and also some very nice web clients that allow posting such images directly from the app.
The main problem of IRC is IMHO that the large networks refuse to implement most of the newer IRCv3 standards or alternatively provide multi-client bouncers to their users.
Adiirc has an option to do inline images. The client pulls the image in on its own. Makes it look similar to Discord.
IRCv3 doesn't bring multimedia as far as I know. There are good changes to the protocol proposed, but they are moving too slow.
This would require an HTML image upload service, which is out of scope for IRCv3 protocol specs.
But nothing stops a server implementation from providing this, and as already said several client+bouncer combinations already support media uploads very well.
The slow moving isn't the problem of the IRCv3 specs, the issue is the adoption by the large networks and subsequently the clients (which rarely implement features the vast majority of their users on the large networks can't use).
Yeah, I'd assume there would be a level of resistance to changes from big networks.