[nodebb-plugin-iframely] IFramely Embeds

Albus

How to deploy Iframely API to your own servers

Self-host the open-source web embeds parsers for hundreds of domains

Iframely (iframely.com)

I still haven't worked out a few kinks, but I've been able to get it up and running on my site. It's not as effective though for normal sites. Take a look at the link above.

Here's what a non-paid embed for the same page looks like on my site:
http://prntscr.com/amjy3w

I recently posted a topic in the Testing Area with more examples - though things went as expected there.

exodo

how do you use that free domain for testing? i set my dev domain on options and it doesn't work

how do you get the free domain?

julian

@exodo Unfortunately, I don't think the free domain exists, just the free tier with the API key you can get from their site.

I'd ask on their issue tracker or via contact form though, just to be sure!

Bri

@julian is the free tier you're referring to the 1000 hits / mo dev plan? Or is there another API key you have to request?

exodo

@julian said in [nodebb-plugin-iframely] IFramely Embeds:

@exodo Unfortunately, I don't think the free domain exists, just the free tier with the API key you can get from their site.

I'd ask on their issue tracker or via contact form though, just to be sure!

well, anyone can get free api key, not sure what this mean

they authorised a special, completely free domain for use in all* NodeBB forums!

julian

I believe they were planning on allowing unlimited use, although at this time I'm not sure whether that is still in effect. Best to assume that that does not exist anymore

exodo

@julian said in [nodebb-plugin-iframely] IFramely Embeds:

I believe they were planning on allowing unlimited use, although at this time I'm not sure whether that is still in effect. Best to assume that that does not exist anymore

i see
then maybe is better to remove that line from first post
as we have only 1k/month free hits and plans upgrade are expensive I think some new people will be disappointed to see the functionality running on this community and then discover that it is a paid plugin

boomzilla

We've been self hosting the open source iframely version. Very simple and doesn't seem to require much server load.

torn2

@boomzilla Are you able to edit the cards when you self host?

boomzilla

@torn2 Not to my knowledge. It works just like using their service except it all happens on your server (or servers, if you put it on a separate machine).

torn2

@boomzilla You have options on how the card may look when you use their hosting.

teh_g

Is this the expanding plugin being used on these forums?

Trying to figure out which one I want to have my end users experience

tigger

This post is deleted!

pichalite

@tigger There is no NodeBB v1.2.2. You are basically using a snaphot of master branch and it's not an official release.

tigger

This post is deleted!

torn2

@julian is there something you guys had to do to get Iframley working correctly when you upgraded past 1.2.0? Ever since we upgraded to 1.2.1 it wont embed links to articles, but the same link embeds here?

tigger

This post is deleted!

tigger

... and it was our issue (broken css). Deleting the comments to keep the thread clean.

teh_g

Something I've noticed in Iframely is that the number of API hits has been steadily increasing over time. I reached out to Iframely, and they noted that NodeBB appears to be making the majority of the API calls.

I've taken a look at your hits, and as I see the more from API calls than from iFrames. It means your NodeBB is making the most hits.
The way NodeBB folks have it implemented is that they keep the cache for 1 day in server's memory. If you restart the servers, for example, - the cache will be reset. Also, if your RAM is limited, some of the records can be evicted from cache prematurely.
We did helped NodeBB team develop the plugin - but from the point where the link is already extracted and till the point before it needs to be stored. So, basically - connecting to API and UI is our part. However, if you have a pull-request for longer cache times or eliminating the older links - my team should be able to review, merge and push it to NPM.

I am far from a developer, so I'll ask if you guys can take a look at the plugin and try and add some method of lowering API hits. Perhaps if a post is older than x days, don't attempt to cache the Iframely hit until someone loads that post. Maybe going a step further and removing the embed if the post is over a certain age.

PitaJ

@teh_g sounds like a good idea to me, too. Maybe allow for customizing the time it takes for embeds to expire in the settings.