Conversation

Notices

1. verified neko :verified::verified::verified::makemeneko: (roboneko@bae.st)'s status on Tuesday, 10-Jan-2023 20:59:54 JST verified neko :verified::verified::verified::makemeneko:
   @hazlin@squid.kids I'm confused. my account unfollowed your old one when you migrated. I don't recall that happening in the past. does that vary by backend or am I just :brainlet:
   
   and also why TF would it do that :blobfoxannoyed:
   •  (mint@ryona.agency)'s status on Tuesday, 10-Jan-2023 20:59:52 JST 

     in reply to
     @roboneko Sapphire forgot to pay for domain once again, I think it might still be available though hosts, that's how they did the migration.
   • verified neko :verified::verified::verified::makemeneko: (roboneko@bae.st)'s status on Tuesday, 10-Jan-2023 20:59:53 JST verified neko :verified::verified::verified::makemeneko:

     in reply to
     wait is shorstackran.ch completely kill? what happened?
   •  (mint@ryona.agency)'s status on Tuesday, 10-Jan-2023 21:01:09 JST 

     in reply to

     • 
     @roboneko Also TLD list bundled with Linkify was last updated three years ago, and a bunch of new TLDs that popped up (like this .kids) can not be tagged until it gets updated.
     https://git.pleroma.social/pleroma/elixir-libraries/linkify/-/blob/master/priv/tlds.txt
   • verified neko :verified::verified::verified::makemeneko: (roboneko@bae.st)'s status on Tuesday, 10-Jan-2023 21:14:53 JST verified neko :verified::verified::verified::makemeneko:

     in reply to

     • 
     @mint omg I didn't even notice that it didn't do the tag earlier. are accounts there literally unmentionable from pleroma then?
     
     why is linkify even needed the grammar with the leading @ is unambiguous and the local server is already aware of the remote account. this is everything that's wrong with modern software and ICANT all rolled in to one :cry:
      likes this.
   •  (mint@ryona.agency)'s status on Tuesday, 10-Jan-2023 21:17:07 JST 

     in reply to
     @roboneko I've made an MR that adds I2P/Loki/Ygg to the list and also allows tagging arbitrary domains (when validate_tld set to false) and IP addresses (there's at least one instance facing the network with only IP, 23.95.115.204), but it's yet to be merged.
     https://git.pleroma.social/pleroma/elixir-libraries/linkify/-/merge_requests/49
   •  (mint@ryona.agency)'s status on Tuesday, 10-Jan-2023 21:18:28 JST 

     in reply to

     • 
     @roboneko Side effect of validate_tld set to false is that some symbols get treated as part of link as well, like here with closing parenthesis. Doesn't bother me much.
   • verified neko :verified::verified::verified::makemeneko: (roboneko@bae.st)'s status on Tuesday, 10-Jan-2023 21:34:58 JST verified neko :verified::verified::verified::makemeneko:

     in reply to

     • 
     @mint wait but. for remote accounts specifically, not just free standing urls. this shouldn't be necessary at all. because there's a much more constrained grammar and the account is either known to exist or it shouldn't be tagged ... right?
     
     I can appreciate the issue with parsing out urls from plain text but a known account that I picked from the popover not getting tagged seems pretty crazy
      likes this.
   •  (mint@ryona.agency)'s status on Tuesday, 10-Jan-2023 21:40:02 JST 

     in reply to
     @roboneko That's just how it is on this bitch of an earth. Took another look at my changes, and setting some arbitrary scheme to `valid_tld?` during mention processing could make it work without necessarily disabling TLD validation at all, but it sounds rather hacky.