Conversation

Notices

1. Embed this notice
   Phantasm (phnt@fluffytail.org)'s status on Monday, 06-Jan-2025 08:21:39 JST Phantasm
   A taste of future interactions on Nostr and Meta platforms.
   
   RT: https://clubcyberia.co/objects/67a4f6ba-922b-400f-b419-850ad0c5a865
   • waifu likes this.
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Monday, 06-Jan-2025 08:21:37 JST Phantasm

     in reply to
     Thank you :glussy: for converting to a DoA social media protocol and writing bridges to AP.
     ✙ dcc :pedomustdie: :phear_slackware: likes this.
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Monday, 06-Jan-2025 08:21:52 JST Phantasm

     in reply to

     • Eric Zhang 2: Episode 1
     @eric This is making me annoyed to the point that I might write an MRF to drop these replies to bots and spam mention glussy with them instead. The only thing stopping me is that I'm away from my computer until tomorrow.
     ✙ dcc :pedomustdie: :phear_slackware: likes this.
   • Embed this notice
     Eric Zhang 2: Episode 1 (eric@pl.starnix.network)'s status on Monday, 06-Jan-2025 08:21:53 JST Eric Zhang 2: Episode 1

     in reply to
     @phnt fully automated hellthread
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Monday, 06-Jan-2025 08:21:59 JST Phantasm

     in reply to
     Nostr doesn't have a spam issue, the cuck said.
     The lack of moderation tools and ease of account creation on Nostr isn't a problem, said the cuck.
     ✙ dcc :pedomustdie: :phear_slackware: likes this.
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Monday, 06-Jan-2025 08:22:00 JST Phantasm

     in reply to
     Truly amazing TL.
     Screenshot_2025-01-05-17-42-17-53_43c0f5467188831519c892e38f82621a.jpg
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Monday, 06-Jan-2025 08:22:08 JST Phantasm

     in reply to

     Didn't finish it in time, because there are apparently two activities coming in, probably due to the relay (one as the user and one with the ap_id as the actor, or something like that). The typical with %User{} actor = User.get_cached_by_ap_id(actor) do... isn't effective as the other activity doesn't seem to have the ap_id in the actor and just let's it through.

     And when I thought that might be the issue, I broke it with the error level in logs, which apparently stops processing the activity immediately.

     Anyway, suya..

     ✙ dcc :pedomustdie: :phear_slackware: likes this.