daisyUniverse · July 22, 2026 10:05
diff --git a/chat embeds.md b/chat embeds.md
diff --git a/oembed.py b/oembed.py
 # oEmbed is quite a lot more powerful, especially in the case of Discord embeds
 # Though it is a bit more complex to implement. 
 # With OG tags, you are able to just place those right in the HTML of the page being served, not so with oEmbed
 # oEmbed basically tells the client (in our case, the discord embed scraper bot) to make a request to a seperate endpoint specified in the file
 # The endpoint can either provide a .json response, or .XML, though I've only experimented with .json personally, they should be basically interchangable

 # A typical setup is to have your oEmbed endpoint take several URL paramters that are generated with the content of the page being previewed
 # Technically there's nothing stopping you from having a single oembed endpoint that generates the content the same way your main page does, but
 # it does seem to be fairly atypical to do so

 # A typical oembed header line
 url = "https://fluxerselfhosting.universe.dog"
 parameters = [ f"{url}/somepage", "json" ]
 oembed_line = f'<link rel=alternate type="application/json+oembed" href="{url}/oembed.json?url={parameters[0]}&format={parameters[1]}"'

 # oEmbed support in discord is slightly hit or miss. While it does support most of the features (title, description, and a few more fields)
 # discord explicitly blocks arbitrary iframes from being embedded via the html oEmbed attribute for all but a specific whitelist of websites
 # Hopefully with Fluxer these limitations will be able to be worked around on self hosted instances though!

 oembed = {
    _type            = ""       # photo, video, link, rich
    version          = 1.0      # The oEmbed version number. This must be 1.0.
    title            = ""       # A text title, describing the resource.
    author_name      = ""       # The name of the author/owner of the resource.
    author_url       = ""       # A URL for the author/owner of the resource.
    provider_name    = ""       # The name of the resource provider.
    provider_url     = ""       # The url of the resource provider.
    thumbnail_url    = ""       # A URL to a thumbnail image representing the resource.
    thumbnail_width  = ""       # The width of the optional thumbnail
    thumbnail_height = ""       # The height of the optional thumbnail
    cache_age        = 86400    # The suggested cache lifetime for this resource, in seconds.
    width            = 600      # The width of the embed. Sometimes respected
    height           = "null"   # This is usually not respected
    html             = ""       # The HTML required to display a rich resource (ie iframe)
 }

 oembed_photo = {
    _type   = "photo"   # When using a photo type, these are the minimum required fields
    url     = ""        # the URL of the photo
    width   = ""        # the Width of the photo
    height  = ""        # the Height of the photo
 }

 oembed_video = {
    _type   = "video"   # When using a video type, these are the minimum required fields
    html    = ""        # Typically this would be an embedded video player, but this isn't respected in most apps
    width   = ""        # the Width of the video
    height  = ""        # the Height of the video
    url     = ""        # Technically optional, but required to embed videos in discord
 }



 # This is the basic structure of an oembed
diff --git a/opengraph.py b/opengraph.py
 # Embeds the simple way: OpenGraph tags
 # Simply embedding og:whatever tags in the header of the site itself is usually sufficient for discord embeds
 # this allows you to embed an image, a description, and a title. For a basic pretty embed this is usually fine

 # Most of this data is pulled from https://ogp.me/

 # While most of the experimentation here will be in regards to these systems interaction with discord and the like, I will be trying to document as
 # much of these standards as I can. who knows, maybe I stumble upon some weird undiscovered tricks along the way?

 # og:
 # Base OpenGraph tags
 OpenGraph = {
    title               = "" # The title of your object as it should appear within the graph, e.g., "The Rock".
    _type               = "" # The type of your object, e.g., "video.movie". Depending on the type you specify, other properties may also be required.
    image               = "" # An image URL which should represent your object within the graph
    audio               = "" # A URL to an audio file to accompany this object.
    description         = "" # A one to two sentence description of your object.
    determinier         = "" # The word that appears before this object's title in a sentence. An enum of (a, an, the, "", auto). If auto is chosen, the consumer of your data should choose between "a" or "an". Default is "" (blank).
    locale              = "" # The locale these tags are marked up in. Of the format language_TERRITORY. Default is en_US
    locale_alternative  = "" # An array of other locales this page is available in
    site_name           = "" # If your object is part of a larger web site, the name which should be displayed for the overall site. e.g., "IMDb"
    video               = "" # A URL to a video file that complements this object
    url                 = "" # The canonical URL of your object that will be used as its permanent ID in the graph, e.g., "https://www.imdb.com/title/tt0117500/".
 }

 # og:image:
 # The standard supports using multiple of these elements to make an array, but as far as I know Discord does not recognize more than one.
 OpenGraph_Image = {
    image       = "" # The URL of the image
    width       = "" # The Dimensions of the image
    height      = "" # The Dimensions of the image
    secure_url  = "" # An HTTPS url for the image
    _type       = "" # The MIME Type of the image (for example 'image/jpeg')
    alt         = "" # The images alt text
 }

 # og:video:
 # Has the same properties of the image type, but this method does not work in discord
 OpenGraph_Video = {
    video       = "" # The URL of the video
    width       = "" # The Dimensions of the video
    height      = "" # The Dimensions of the video
    secure_url  = "" # An HTTPS url for the video
    _type       = "" # The MIME Type of the video (for example 'application/x-shockwave-flash')
 }

 # og:audio:
 # This would be used to embed audio, but I don't know of any chat service that supports this.
 OpenGraph_Audio = {
    audio       = "" # The URL of the audio file
    secure_url  = "" # An HTTPS url for the audio
    _type       = "" # The MIME Type of the audio (for example 'audio/mpeg')
 }

 # There are also some types dedicated to media metadata, as seen in IMBD headers
 # None of these are used for discord embeds but I want to have them all documented anyways


 ### MUSIC ###
 # These operate under a namespace system following a URI found here: https://ogp.me/ns/music#

 OpenGraph_Music_Song = {
    duration        = 1     # TYPE: Integer           # Length of the song in seconds
    album           = ""    # TYPE: Music.album Array # The album the song is from
    album_disc      = 1     # TYPE: Integer           # Which disc of the album this song is on
    album_track     = 1     # TYPE: Integer           # Which track this song is
    musician        = ""    # TYPE: Profile Array     # The musician that made this song. Takes a profile object
 }

 OpenGraph_Music_Album = {
    song            = ""    # TYPE: Music.song  # The song on this album
    disc            = 1     # TYPE: Integer     # The disc this song is on  
    track           = ""    # TYPE: Integer     # The track this song is on
    musician        = ""    # TYPE: Profile     # The musician that made this song
    release_date    = ""    # TYPE: Datetime    # The date this album was released
 }

 OpenGraph_Music_Playlist = {
    song    = "" # TYPE: Music.song         # The song on this album.
    disc    = "" # TYPE: Music.song:disc    # The disc this song is on
    track   = "" # TYPE: Music.song:track   # The track
    creator = "" # TYPE: Profile            # The creator of this playlist
 }

 OpenGraph_Music_Radio_Station = {
    creator = "" # TYPE: Profile # The creator of this station
 }

 ### VIDEO ###
 # These operate under a namespace system following a URI found here: https://ogp.me/ns/video#

 OpenGraph_Video_Movie = {
    actor           = "" # TYPE: Profile Array # Takes an array of profile objects
    actor_role      = "" # TYPE: String        # The role that they played
    director        = "" # TYPE: Profile Array # Takes an array of profile objects
    writer          = "" # TYPE: Profile Array # Takes an array of profile objects
    duration        = 1  # TYPE: Datetime      # Takes an array of profile objects
    release_date    = "" # TYPE: Datetime      # Takes a datetime object
    tag             = "" # TYPE: String Array  # Takes a string array of words associated with this movie (ie genres)
 }

 # Identical to video.movie
 OpenGraph_Video_TV_Show = OpenGraph_Video_Movie

 # Identical to video.movie, but with one more tag to indicate TV show
 OpenGraph_Video_Episode = {
    series = "" # TYPE: Video.tv_show # The series this episode belongs to
 }

 # Identical to video.movie
 OpenGraph_Video_Other = OpenGraph_Video_Movie

 ### NON-VERTICAL ###
 # These are globally defined objects that just don't fit into a vertical but yet are broadly used and agreed upon.
 # None have uses in discord as far as I know

 OpenGraph_Article = { # URI : https://ogp.me/ns/article#
    published_time  = "" # TYPE: Datetime      # When the article was first published.
    modified_time   = "" # TYPE: Datetime      # When the article was last changed.
    expiration_time = "" # TYPE: Datetime      # When the article is out of date after.
    author          = "" # TYPE: Profile Array # Writers of the article.
    section         = "" # TYPE: String        # A high-level section name. E.g. Technology
    tag             = "" # TYPE: String Array  # Tag words associated with this article.
 }

 OpenGraph_Book = { # URI : https://ogp.me/ns/book#
    author          = "" # TYPE: Profile Array # Who wrote this book.
    isbn            = "" # TYPE: String        # The ISBN
    release_date    = "" # TYPE: Datetime      # The date the book was released.
    tag             = "" # TYPE: String Array  # Tag words associated with this book.
 }

 # Note: This is still in beta according to OGP
 OpenGraph_Payment_Link = { # URI : https://ogp.me/ns/payment# 
    description     = ""    # TYPE: String      # Description about the payment link. 
    currency        = ""    # TYPE: String      # The currency code ISO 4217 of the payment.
    amount          = 1.0   # TYPE: Float       # An amount requested on the payment link in decimal format.
    expires_at      = ""    # TYPE: Datetime    # The date and time including minutes and seconds on which the payment link expires.
    status          = ""    # TYPE: Enum        # Status of the payment. (Pending, Paid, Failed, Expired)
    id              = ""    # TYPE: String      # The unique identifier associated with the payment link for a given payment gateway or service provider
    success_url     = ""    # TYPE: URL         # A valid URL that gets redirected when payment is success. 
 }


 OpenGraph_Profile = { # URI : https://ogp.me/ns/profile# 
    first_name  = "" # TYPE: String      # A name normally given to an individual by a parent or self-chosen.
    last_name   = "" # TYPE: String      # A name inherited from a family or marriage and by which the individual is commonly known.
    username    = "" # TYPE: String      # A short unique string to identify them.
    gender      = "" # TYPE: Enum        # Their gender. (Male, Female) (bruh)
 }
diff --git a/support matrix.md b/support matrix.md
	# oEmbed is quite a lot more powerful, especially in the case of Discord embeds
	# Though it is a bit more complex to implement.
	# With OG tags, you are able to just place those right in the HTML of the page being served, not so with oEmbed
	# oEmbed basically tells the client (in our case, the discord embed scraper bot) to make a request to a seperate endpoint specified in the file
	# The endpoint can either provide a .json response, or .XML, though I've only experimented with .json personally, they should be basically interchangable

	# A typical setup is to have your oEmbed endpoint take several URL paramters that are generated with the content of the page being previewed
	# Technically there's nothing stopping you from having a single oembed endpoint that generates the content the same way your main page does, but
	# it does seem to be fairly atypical to do so

	# A typical oembed header line
	url = "https://fluxerselfhosting.universe.dog"
	parameters = [ f"{url}/somepage", "json" ]
	oembed_line = f'<link rel=alternate type="application/json+oembed" href="{url}/oembed.json?url={parameters[0]}&format={parameters[1]}"'

	# oEmbed support in discord is slightly hit or miss. While it does support most of the features (title, description, and a few more fields)
	# discord explicitly blocks arbitrary iframes from being embedded via the html oEmbed attribute for all but a specific whitelist of websites
	# Hopefully with Fluxer these limitations will be able to be worked around on self hosted instances though!

	oembed = {
	_type = "" # photo, video, link, rich
	version = 1.0 # The oEmbed version number. This must be 1.0.
	title = "" # A text title, describing the resource.
	author_name = "" # The name of the author/owner of the resource.
	author_url = "" # A URL for the author/owner of the resource.
	provider_name = "" # The name of the resource provider.
	provider_url = "" # The url of the resource provider.
	thumbnail_url = "" # A URL to a thumbnail image representing the resource.
	thumbnail_width = "" # The width of the optional thumbnail
	thumbnail_height = "" # The height of the optional thumbnail
	cache_age = 86400 # The suggested cache lifetime for this resource, in seconds.
	width = 600 # The width of the embed. Sometimes respected
	height = "null" # This is usually not respected
	html = "" # The HTML required to display a rich resource (ie iframe)
	}

	oembed_photo = {
	_type = "photo" # When using a photo type, these are the minimum required fields
	url = "" # the URL of the photo
	width = "" # the Width of the photo
	height = "" # the Height of the photo
	}

	oembed_video = {
	_type = "video" # When using a video type, these are the minimum required fields
	html = "" # Typically this would be an embedded video player, but this isn't respected in most apps
	width = "" # the Width of the video
	height = "" # the Height of the video
	url = "" # Technically optional, but required to embed videos in discord
	}



	# This is the basic structure of an oembed
	# Embeds the simple way: OpenGraph tags
	# Simply embedding og:whatever tags in the header of the site itself is usually sufficient for discord embeds
	# this allows you to embed an image, a description, and a title. For a basic pretty embed this is usually fine

	# Most of this data is pulled from https://ogp.me/

	# While most of the experimentation here will be in regards to these systems interaction with discord and the like, I will be trying to document as
	# much of these standards as I can. who knows, maybe I stumble upon some weird undiscovered tricks along the way?

	# og:
	# Base OpenGraph tags
	OpenGraph = {
	title = "" # The title of your object as it should appear within the graph, e.g., "The Rock".
	_type = "" # The type of your object, e.g., "video.movie". Depending on the type you specify, other properties may also be required.
	image = "" # An image URL which should represent your object within the graph
	audio = "" # A URL to an audio file to accompany this object.
	description = "" # A one to two sentence description of your object.
	determinier = "" # The word that appears before this object's title in a sentence. An enum of (a, an, the, "", auto). If auto is chosen, the consumer of your data should choose between "a" or "an". Default is "" (blank).
	locale = "" # The locale these tags are marked up in. Of the format language_TERRITORY. Default is en_US
	locale_alternative = "" # An array of other locales this page is available in
	site_name = "" # If your object is part of a larger web site, the name which should be displayed for the overall site. e.g., "IMDb"
	video = "" # A URL to a video file that complements this object
	url = "" # The canonical URL of your object that will be used as its permanent ID in the graph, e.g., "https://www.imdb.com/title/tt0117500/".
	}

	# og:image:
	# The standard supports using multiple of these elements to make an array, but as far as I know Discord does not recognize more than one.
	OpenGraph_Image = {
	image = "" # The URL of the image
	width = "" # The Dimensions of the image
	height = "" # The Dimensions of the image
	secure_url = "" # An HTTPS url for the image
	_type = "" # The MIME Type of the image (for example 'image/jpeg')
	alt = "" # The images alt text
	}

	# og:video:
	# Has the same properties of the image type, but this method does not work in discord
	OpenGraph_Video = {
	video = "" # The URL of the video
	width = "" # The Dimensions of the video
	height = "" # The Dimensions of the video
	secure_url = "" # An HTTPS url for the video
	_type = "" # The MIME Type of the video (for example 'application/x-shockwave-flash')
	}

	# og:audio:
	# This would be used to embed audio, but I don't know of any chat service that supports this.
	OpenGraph_Audio = {
	audio = "" # The URL of the audio file
	secure_url = "" # An HTTPS url for the audio
	_type = "" # The MIME Type of the audio (for example 'audio/mpeg')
	}

	# There are also some types dedicated to media metadata, as seen in IMBD headers
	# None of these are used for discord embeds but I want to have them all documented anyways


	### MUSIC ###
	# These operate under a namespace system following a URI found here: https://ogp.me/ns/music#

	OpenGraph_Music_Song = {
	duration = 1 # TYPE: Integer # Length of the song in seconds
	album = "" # TYPE: Music.album Array # The album the song is from
	album_disc = 1 # TYPE: Integer # Which disc of the album this song is on
	album_track = 1 # TYPE: Integer # Which track this song is
	musician = "" # TYPE: Profile Array # The musician that made this song. Takes a profile object
	}

	OpenGraph_Music_Album = {
	song = "" # TYPE: Music.song # The song on this album
	disc = 1 # TYPE: Integer # The disc this song is on
	track = "" # TYPE: Integer # The track this song is on
	musician = "" # TYPE: Profile # The musician that made this song
	release_date = "" # TYPE: Datetime # The date this album was released
	}

	OpenGraph_Music_Playlist = {
	song = "" # TYPE: Music.song # The song on this album.
	disc = "" # TYPE: Music.song:disc # The disc this song is on
	track = "" # TYPE: Music.song:track # The track
	creator = "" # TYPE: Profile # The creator of this playlist
	}

	OpenGraph_Music_Radio_Station = {
	creator = "" # TYPE: Profile # The creator of this station
	}

	### VIDEO ###
	# These operate under a namespace system following a URI found here: https://ogp.me/ns/video#

	OpenGraph_Video_Movie = {
	actor = "" # TYPE: Profile Array # Takes an array of profile objects
	actor_role = "" # TYPE: String # The role that they played
	director = "" # TYPE: Profile Array # Takes an array of profile objects
	writer = "" # TYPE: Profile Array # Takes an array of profile objects
	duration = 1 # TYPE: Datetime # Takes an array of profile objects
	release_date = "" # TYPE: Datetime # Takes a datetime object
	tag = "" # TYPE: String Array # Takes a string array of words associated with this movie (ie genres)
	}

	# Identical to video.movie
	OpenGraph_Video_TV_Show = OpenGraph_Video_Movie

	# Identical to video.movie, but with one more tag to indicate TV show
	OpenGraph_Video_Episode = {
	series = "" # TYPE: Video.tv_show # The series this episode belongs to
	}

	# Identical to video.movie
	OpenGraph_Video_Other = OpenGraph_Video_Movie

	### NON-VERTICAL ###
	# These are globally defined objects that just don't fit into a vertical but yet are broadly used and agreed upon.
	# None have uses in discord as far as I know

	OpenGraph_Article = { # URI : https://ogp.me/ns/article#
	published_time = "" # TYPE: Datetime # When the article was first published.
	modified_time = "" # TYPE: Datetime # When the article was last changed.
	expiration_time = "" # TYPE: Datetime # When the article is out of date after.
	author = "" # TYPE: Profile Array # Writers of the article.
	section = "" # TYPE: String # A high-level section name. E.g. Technology
	tag = "" # TYPE: String Array # Tag words associated with this article.
	}

	OpenGraph_Book = { # URI : https://ogp.me/ns/book#
	author = "" # TYPE: Profile Array # Who wrote this book.
	isbn = "" # TYPE: String # The ISBN
	release_date = "" # TYPE: Datetime # The date the book was released.
	tag = "" # TYPE: String Array # Tag words associated with this book.
	}

	# Note: This is still in beta according to OGP
	OpenGraph_Payment_Link = { # URI : https://ogp.me/ns/payment#
	description = "" # TYPE: String # Description about the payment link.
	currency = "" # TYPE: String # The currency code ISO 4217 of the payment.
	amount = 1.0 # TYPE: Float # An amount requested on the payment link in decimal format.
	expires_at = "" # TYPE: Datetime # The date and time including minutes and seconds on which the payment link expires.
	status = "" # TYPE: Enum # Status of the payment. (Pending, Paid, Failed, Expired)
	id = "" # TYPE: String # The unique identifier associated with the payment link for a given payment gateway or service provider
	success_url = "" # TYPE: URL # A valid URL that gets redirected when payment is success.
	}


	OpenGraph_Profile = { # URI : https://ogp.me/ns/profile#
	first_name = "" # TYPE: String # A name normally given to an individual by a parent or self-chosen.
	last_name = "" # TYPE: String # A name inherited from a family or marriage and by which the individual is commonly known.
	username = "" # TYPE: String # A short unique string to identify them.
	gender = "" # TYPE: Enum # Their gender. (Male, Female) (bruh)
	}
Emoji	Meaning
❓	I genuinely have no clue
✅	I'm pretty sure it works based on what I know
☑️	Redundant, used as a fallback value in case a higher priority tag is unset
🚫	As far as I know, it's not supported
Tag	Discord	Fluxer	Telegram	Purpose
og:title	✅^V	✅^V	❓	The title of your object as it should appear within the graph, e.g., "The Rock".
og:site_name	❓	✅	❓	If your object is part of a larger web site, the name which should be displayed for the overall site. e.g., "IMDb"
og:description	✅^V	✅^V	❓	A one to two sentence description of your object.
og:image	✅^V	✅^V	❓	An image URL which should represent your object within the graph
og:image:alt	❓	✅^V	❓	The images alt text
og:image:description	❓	☑️^V	❓	Another way to enter alt text
og:image:secure_url	❓	☑️^V	❓	An HTTPS url for the image
og:video	🚫¹	✅	❓	A URL to a video file that complements this object
og:video:url	🚫	☑️	❓	The URL of the video
og:video:secure_url	🚫	☑️	❓	An HTTPS url for the video
og:audio	🚫	☑️	❓	A URL to an audio file to accompany this object.
og:audio:url	🚫	☑️	❓	The URL of the audio
og:audio:secure_url	🚫	✅	❓	An HTTPS url for the audio
og:determiner	🚫	🚫	❓	The word that appears before this object's title in a sentence. An enum of (a, an, the, "", auto). If auto is chosen, the consumer of your data should choose between "a" or "an". Default is "" (blank).
og:url	🚫	🚫	❓	The canonical URL of your object that will be used as its permanent ID in the graph, e.g., "https://www.imdb.com/title/tt0117500/".
Tag	Discord	Fluxer	Telegram	Purpose
twitter:card	✅	🚫	❓	summary, summary_large_image, app, player
twitter:creator	❓	🚫	❓	The creator of the content (eg @daisy.universe.dog)
twitter:title	❓	☑️	❓	The title of the content
twitter:description	☑️	☑️	❓	A description that concisely summarizes the content.
twitter:site:name	✅	✅	❓	Same as Provider name, eg 'Bluesky'
twitter:image	❓	☑️	❓	An image URL
twitter:image:src	❓	☑️	❓	An image URL
twitter:image:alt	❓	☑️	❓	The alt text of the image
twitter:video	❓	☑️	❓	A Video URL
twitter:video:url	❓	☑️	❓	A Video URL
twitter:player	❓	❓	🚫¹	A Video URL (i think)
twitter:player:stream	❓	❓	🚫	A Video URL (i think)
twitter:player:height	❓	❓	🚫	The intended height of the player
twitter:player:width	❓	❓	🚫	The indented width of the player
twitter:player:stream:content_type	❓	❓	🚫	The MIME type of the meda, ie 'video/mp4'
Tag	Discord	Fluxer	Telegram	Purpose
type	✅	🚫	❓	photo, video, link, rich
version	✅	✅	✅	The oEmbed version number. This must be 1.0.
title	✅	☑️	❓	A text title, describing the resource.
author_name	✅^V	✅^V	❓	The name of the author/owner of the resource.
author_url	✅^V	✅^V	❓	A URL for the author/owner of the resource.
provider_name	✅^V	☑️	❓	The name of the resource provider.
provider_url	✅^V	☑️	❓	The url of the resource provider.
thumbnail_url	✅^V	🚫	❓	A URL to a thumbnail image representing the resource.
thumbnail_height	🚫	🚫	❓	The height of the optional thumbnail
thumbnail_width	🚫	🚫	❓	The width of the optional thumbnail
cache_age	🚫	🚫	🚫	The suggested cache lifetime for this resource, in seconds.
width	❓	🚫	❓	The width of the embed. Sometimes respected
height	❓	🚫	❓	The width of the embed. almost never respected
url	✅^V	🚫	❓	the URL of the resource (when using photo or video type)
html	🚫	🚫	🚫	The HTML required to display a rich resource (ie iframe)