Mikaela/gist
1
0
Fork 0
mirror of https://gitea.blesmrt.net/mikaela/gist.git synced 2024-11-24 20:29:24 +01:00
Code Issues Projects Releases Wiki Activity
8f2785af38
gist/irc/limnoria/titlefetching.md

2.3 KiB
Raw Blame History

A bit opinionated titlefetching

Preparation

load Web
config plugins.web.snarfMultipleUrls True
config plugins.web.snarferShowDomain False
config plugins.web.snarferShowTargetDomain False
config supybot.protocols.http.userAgents "Limnoria UrlPreviewBot"
config supybot.protocols.http.peekSize 1048576
  • enables the plugin (shipped with Limnoria)
  • enables titlefetching for all links on line, not just the first one
  • disables showing domain (small protection against multiple titlesfetcherrs entering a loop or simply not annoying users with clientside link previews (Matrix/Telegram bridges/relays included))
  • disables showing redirect target -||-
  • sets user-agent to “Limnoria UrlPreviewBot” instead of ‘Mozilla/5.0 (compatible; utils.web python module)’ from 2005
    • I have heard that it’s bad to pretend to be something you aren’t and Twitter will only give you HTMl <title>s if your user-agent contains UrlPreviewBot thanks Tulir’s Synapse patch
  • search for html titles from the first MEGABYTE of the webpage as modern web is horrible (looking at you hs.fi & youtube.com)

Actually enabling it

config channel #CHAN plugins.web.titleSnarfer True
  • enables titlefetching per-channel, on #CHAN to be accurate (avoiding unwanted channels in case of botloop)
    • "channel #CHAN" could also be replaced with network NETWORKNAME for every channel on network or config (or omitted entirely) for everywhere (channel takes priority over network which probably takes priority over global)

Excluding domains from titlefetching

config supybot.plugins.Web.nonSnarfingRegexp m/(t.me|matrix.to|facebook.com|instagram.com|imgur.com)/
  • regexp to block the listed domains, which are the first useless examples I have encountered recently. I just stole the regexp from canonical Limnoria

Titlesnarfing ignored users

While I personally don’t like to do this, it’s possible by

config channel #CHAN plugins.web.checkignored False

I may have the bot on multiple sides of relay or the user may be ignored due to abuse so this may result into spam.