You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PSYC is a pretty cool protocol, but the other clients currently available are a mess and not updated. Many PSYC servers have a lot of features (email, jabber, IRC, and other gateways), but aren't very well maintained. If Echoplexus became a solid PSYC platform (since it is both a server and client), it could attract others to create build off of Echoplexus and/or create other PSYC platforms to federate with Echoplexus. It also already has many of the desired features of Echoplexus defined in its protocol. It would also put Echoplexus in the position of being able to shape the future of the protocol.
This could help solve all of the following issues:
Federation: Issue #133
Conversation threading: Issue #152
P2P file transfer: Issue #157
Nick handling: Issue #223 & #225
Hashtag support (maybe): Issue #156
IRC gateway/hooks (maybe): Issue #217
And this could be part of the refactoring effort #198
The text was updated successfully, but these errors were encountered:
PSYC is a pretty cool protocol, but the other clients currently available are a mess and not updated. Many PSYC servers have a lot of features (email, jabber, IRC, and other gateways), but aren't very well maintained. If Echoplexus became a solid PSYC platform (since it is both a server and client), it could attract others to create build off of Echoplexus and/or create other PSYC platforms to federate with Echoplexus. It also already has many of the desired features of Echoplexus defined in its protocol. It would also put Echoplexus in the position of being able to shape the future of the protocol.
http://about.psyc.eu/PSYC
http://about.psyc.eu/Comparison
http://about.psyc.eu/IRC#The_Good_and_the_Bad_about_IRC
http://about.psyc.eu/Jabber#Technical_Problems_with_XMPP
The protocol is defined here:
http://www.psyc.eu/tech.en.html
This could help solve all of the following issues:
Federation: Issue #133
Conversation threading: Issue #152
P2P file transfer: Issue #157
Nick handling: Issue #223 & #225
Hashtag support (maybe): Issue #156
IRC gateway/hooks (maybe): Issue #217
And this could be part of the refactoring effort #198
The text was updated successfully, but these errors were encountered: