twtxt

Timeline for https://eapl.me/twtxt.txt

🔄 Refresh timeline

👨‍💻 Login

Following: 16

tkanos https://twtxt.net/user/tkanos/twtxt.txt Remove

eaplme https://eapl.me/twtxt.txt Remove

eaplmx https://eapl.mx/twtxt.txt Remove

lyse https://lyse.isobeef.org/twtxt.txt Remove

prologic https://twtxt.net/user/prologic/twtxt.txt Remove

rrraksamam https://twtxt.net/user/rrraksamam/twtxt.txt Remove

darch https://neotxt.dk/user/darch/twtxt.txt Remove

shreyan https://twtxt.net/user/shreyan/twtxt.txt Remove

movq https://www.uninformativ.de/twtxt.txt Remove

bender https://twtxt.net/user/bender/twtxt.txt Remove

stigatle https://yarn.stigatle.no/user/stigatle/twtxt.txt Remove

darch http://darch.dk/twtxt.txt Remove

xuu https://txt.sour.is/user/xuu/twtxt.txt Remove

jason https://jasonsanta.xyz/twtxt.txt Remove

mckinley https://twtxt.net/user/mckinley/twtxt.txt Remove

eapl-mes-7-daily-links https://feeds.twtxt.net/eapl-mes-7-daily-links/twtxt.txt Remove


bender
Reply to #aajeezq
@mckinley a few points:

Technical:

1. Single point of failure: Relays, though decentralised, could be targeted for censorship or sabotage.
2. Message integrity: Messages are not inherently linked, raising concerns about spoofing and manipulation.
3. Data storage: Clients may need to download large amounts of data, especially historical messages, impacting performance.
4. Limited functionality: Currently focuses on text-based communication, lacking media sharing or advanced features.

Usability:

1. Steep learning curve: It is still young and requires technical knowledge for setup and use.
2. Limited user base: Finding an active community and familiar faces can be challenging.
3. Unintuitive interfaces: Client applications may not be as user-friendly as established platforms.

Also, full of crypto bros, crypto bros wanna be, and, well, worthless crypto (mixed with some porn, nazi crap, etc.). But go ahead, go through the same phases I went (I even ran my own relay), and see it for yourself. :-)
1 month ago
💬 Reply


⏭️ Next