Fediverse Embeds vs Hosted Content Importer (HCI)

This plugin lets you optimize and customize embedded posts from fediverse platform that support this feature. Please visit the GitHub repo for instructions on how to embed posts and for general FAQ and troubleshooting tips. Learn more | View source Privacy notice When embedding a post from a fediverse server, the content of the post needs to be fetched from that server, which is then stored in your site’s database. Based on the way you configure the plugin, additional requests will be made periodically to refresh the cached data. When making requests to a third party server in general, the server will receive and may record the IP address of the server hosting your website. Please consult the privacy details and terms of use of each server you are embedding content from. (Example for mastodon.social: About Mastodon, Privacy policy) Development The complete source code for this plugin, including unminified JavaScript and SCSS files, is publicly available on GitHub: https://github.com/stefanbohacek/fediverse-embeds-wordpress-plugin To build the plugin from source you will need Node.js (v18+) and npm. Run the following commands from the plugin root: npm install npm run dev The build process uses Gulp with Browserify and Babel to bundle and minify the JavaScript files located in the src directory, and compiles SCSS to CSS. The compiled output is placed in the dist directory.

It imports third party hosted contents within WordPress blog. You can define from which url/resource to fetch the content. The original source may be editable by anyone else whom you trust. Thus, it logically empowers you to allow other users to externally edit a particular section of your blogs. And, you do not have to give them any access credentials of your website. After installation, use shortcode tag [third] with few parameters as: [third source="markdown" id="https://goo.gl/UpclKH" section=""] source is a content processor type. id is a URL or ID given by the third parties. section is an optional parameter to access deeper content. cache is a boolean directive whether to reuse the cached content. It will then embed remote markdown content inside your blog. Additionally, it will convert the text into HTML using Parsedown. Parameters source: Where to seek the data (eg. Content Hosting Server). Examples: analytics: ✔ implemented (Google Analytics) file: ✔ implemented (Read from local file) gist: ✔ implemented (Embed Gist Snippets) jotform: ✔ implemented (Embed Web Forms) markdown: ✔ implemented (Parse remote markdown files) qr: ✔ implemented For Custom Data, For current page’s URL youtube: ✔ implemented (Embeds a YouTube Video) database: Partially implemented, and left for developers url, api: Work in progress wikipedia: Work in progress, Strategy: Content JSON to Data Section The list is not limited, you expand it. Join/Fork Development id: Content ID (unique identifier) of the data you want. Often: Full URLs Database IDs Resource IDs provided by Service Providers eg. YouTube Video ID, JotForm Form ID, … Full Path of a Local File section: Additional parameter to identify the specific section of the content. Example: Parsing a remote .md file [third source="markdown" id="https://goo.gl/UpclKH" section=""] Learn to write your .md file. Example: Embedding a gist code from GitHub [third source="gist" id="000000000000" section="filename.php"] Create your gists at GitHub. Example: Embedding a JotForm [third source="jotform" id="000000000000" section=""] Create your own web form at JotForm website. Example: Reading a server’s local file [third source="file" id="/tmp/readme.txt" section=""] It has to be a static file for security reasons. For example, if you read the .php file, it will NOT process it, rather read its contents only. Your can contain valid HTML data, css and javascripts. Example: Accessing database – Expand it yourself [third source="database" id="0" section="recent"] Detailed implementations are left for the developers because of the nature. It is a proof of concept work. Please feel free to modify/expand it. Example: Custom QR Code [third source="qr" id="YOUR DATA" section=""] Example: QR Code for Current Page (Full URL) [third source="qr" id="url" section="internal"] The above example is a full code. If you embed it anywhere, it lets your users copy that page’s URL into their mobile. Example: Embedding a YouTube Video [third source="youtube" id="v00000000000" section=""] Choose your video from YouTube. Personalized Content Processors You may often consider writing your own Content Processor. Refer to Custom Content Processor section in [Other Notes] tab. Custom Content Processors If you want to develop your own Content Processor, it is much easier now. Just create a tiny class file inside classes/processors as like one of the existing one. Simple examples are YouTube, JotForm and Gist processors. Minimum requirements File name: class.processor_YOURNAME.inc.php Method: public function fetch($form_id = null, $section = null). Process your content. Return HTML string. For references, see class.processor_none.inc.php Use as: [third source="YOURNAME" section=""] Click for real examples. Just that much easy drop-in replacement. Banner Image Used from unsplash.com Cable Cars and Rope: Represents contents coming from various sources.