Hmm. SO I'm looking at implementing tags and mentions in Agora. Not sure exactly how I want to do it though. I think the way that it automatically @'s everyone is kind of clumsy, but I'm not sure how far I can deviate from that and have it still work with mastodon, or how I'd do things instead. Any thoughts? :/

· · Web · 0 · 5 · 3

Oh! I never did get any responses to this. Seriously, should I adopt Mastodons conventions for tags and mentions or should I try and roll my own? I'm pretty sure everyone else mostly just uses masto's, except freindica I guess? :/

Show thread

@a_breakin_glass It takes @'s and makes those into tags, and delivers the post to anyone thus tagged, including @'s in the post. Right now Agora does none of that, so while the post will federate it won't appear in notifications, and thus people usually won't see it when it's a response to their posts. I also don;t use the conversation tag, which I'm not sure on the details of but is probably important. :/

@Angle I saw your previous toot with the question but I didn't understand it as formulated. Perhaps some additional background would be needed in a long form post so that other programmers understand the problem you're trying to solve.

@Angle Sorry forgot to reply…
I think you should try to avoid differing much from mastodon, but for pleroma it basically doesn’t care about the formatting and we can adapt what we’re getting if needed for ourselves.

@lanodan Mmm, works for me. Though! I don;t think I have the thing federating properly with Pleroma. I should work on that. :/

@Angle Haven’t tried on my side. Anyway if you need some adaptation on the side of pleroma, feel free to ask.

@lanodan Thank you! The main problem I see that is that I can;t get the json for a post by querying it's id the same way I can with mastodon. How should I do things instead? :/

@lanodan Hmm. I'm getting "Error: request to failed, reason: write EPROTO 139651400279872:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:../deps/openssl/openssl/ssl/s23_clnt.c:802: "

I tried going and changing the header from "ld+json" to "activity+json", but it's still not working. :/

@lanodan The full header right now is: Accept: 'application/activity+json; profile=""', maybe the problem is elsewhere? :/

@lain @lanodan Huh. So does pleroma not like my ssl? Or is that just that particular server? :/

@lanodan @lain Ah, gotcha. So nothing I need to do? Though it seems like I should still try and make it so that my code can deal with the error, as it seems most other servers are able to manage. :/

@Angle @lain You should still try to fix it, your software should not reject my TLS configuration unless you’re working with software that is like from more than 3~4 years ago.

@lanodan @lain Where would I look for that? I'm guessing it's the libraries that I use for my https request? :/

@lanodan @lain I'm using meteor, which is using node.js. My dependency trees are a little upsetting. :/

@Angle @lain I remember TheKinrar had some issue with NodeJS used by but I’m pretty sure the error is different as it was a curve issue.

@lanodan @lain I think it's just that one of my dependencies is outdated. Or my dependencies dependencies is outdated, or something like that... :/

@lanodan @lain Argh. Well, I took a crack at it, but I have no idea how to fix this, or even what the problem is in specific. I'll try again later. :/

@Angle Sounds like a SSL/TLS error.
You should not get this other than with a seriously oudated/misconfigured OpenSSL.
Here are my ciphers (the version note is outdated):
Sign in to participate in the conversation
ACP 🎉🍰

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!