Hello DEV Community!
I'm excited to announce a significant improvement in how we embed rich content (such as Tweets and Youtube videos) in Forem p...
For further actions, you may consider blocking this person and/or reporting abuse
In celebration of this update, I'm gonna embed something here:
I've been really digging this song this AM. ๐๐
oh you just tested this new feature :)
Arit, you crushed this.
Thank you Ben!
Do the new embeds have a way to hide the GitHub README to make the embed more compact? In the other Liquid format, it worked to add
noreadme
to the tag.Thank you Andy. Would you please open a ticket for this?
Issue #16673 ๐
Cool! Thanks for the update! Will we need to update any older content (since the former approach will be deprecated in the future), or will that be handled for us?
Youโre welcome Andy!
Great question! While we have not decided, we will most probably handle the updates of v1 embeds ourselves.
Very handy! Thanks!
Wait โ I already found a bug lol
{% embed https://google.com/ %}
doesnt seem to workHello @siddharthshyniben, the link you used is not currently supported.
You can find a list of currently supported embeds here: dev.to/p/editor_guide#liquidtags
Ooooh coooool ๐ฅณ๐ฅณ๐ฅณ
Hey Arit,
This is brilliant! Thanks for letting us know. Now, all I have to do is find a way to get it into my next post ;)
Thanks for the information!
But what does this mean for user privacy? Won't this enable these companies to do cross-site tracking?
At present, the only embeds you can use are the previous embeds; we've just squashed them into a unified syntax. So this has been a privacy neutral change.
are we going to be reading about this as a security vulnerability in a few months?
What are you seeing as the possible security vulnerability?
At present, the only embeds you can use are the previous embeds. The thing that's changed is you don't need to recall which service you're embedding. We're also working on a fallback (e.g. which would be "render the A-tag you provided" but perhaps more)