[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f4zpwm4YFTOrpwfvcy4X1u1LbwQNmgRuykIHxka-efhI":3},{"slug":4,"display_name":5,"profile_url":6,"plugin_count":7,"total_installs":8,"avg_security_score":9,"avg_patch_time_days":10,"trust_score":11,"computed_at":12,"plugins":13},"edhynan","EdHynan","https:\u002F\u002Fprofiles.wordpress.org\u002Fedhynan\u002F",2,40,85,30,84,"2026-04-04T20:58:02.405Z",[14,36],{"slug":15,"name":16,"version":17,"author":5,"author_profile":6,"description":18,"short_description":19,"active_installs":10,"downloaded":20,"rating":21,"num_ratings":21,"last_updated":22,"tested_up_to":23,"requires_at_least":24,"requires_php":25,"tags":26,"homepage":32,"download_link":33,"security_score":9,"vuln_count":21,"unpatched_count":21,"last_vuln_date":34,"fetched_at":35},"swfput","SWFPut – SWFlash Put","3.1.0.1","\u003Cp>SWFPut provides ‘responsive’ video for posts and pages.\u003Cbr \u002F>\nSWFPut makes the presentation of video reliable for your\u003Cbr \u002F>\nvisitors: several conditions are handled well, such as\u003Cbr \u002F>\nthe uneven support for HTML5 video formats in the major\u003Cbr \u002F>\nbrowsers, the possible lack of support for either HTML5\u003Cbr \u002F>\nvideo or flash video in the visitor’s browser, and even\u003Cbr \u002F>\nthe possiblilty that JavaScript might be disabled in your\u003Cbr \u002F>\nvisitor’s browser.\u003C\u002Fp>\n\u003Cp>In addition to video for posts and pages, SWFPut provides\u003Cbr \u002F>\na video widget for use in widget areas, such as a sidebar.\u003C\u002Fp>\n\u003Cp>SWFPut video is ‘responsive’: it should display at a\u003Cbr \u002F>\nsuitable size on your visitor’s device, whether large\u003Cbr \u002F>\nor small (a responsive WordPress theme is necessary).\u003C\u002Fp>\n\u003Cp>SWFPut makes video setup easy and flexible by providing\u003Cbr \u002F>\nan easy dialog based setup similar to (and based on)\u003Cbr \u002F>\nthat used by WordPress core media, and also an\u003Cbr \u002F>\nadvanced form with additional settings, which\u003Cbr \u002F>\nappears in a new “metabox”\u003Cbr \u002F>\non the editor page. For widgets, the form appears with\u003Cbr \u002F>\nthe usual drag and drop widget interface. After adding\u003Cbr \u002F>\nvideo objects, the form will continue to be useful for\u003Cbr \u002F>\nmaking changes (or, if you wish, to delete the video).\u003C\u002Fp>\n\u003Cp>In WordPress versions 3.3 and greater, video added by\u003Cbr \u002F>\nSWFPut will be visible in the post\u002Fpage visual editor.\u003C\u002Fp>\n\u003Cp>As many video objects as you wish can be placed in posts\u003Cbr \u002F>\npages, and of course the widget supports as many instances\u003Cbr \u002F>\nas you wish.\u003Cbr \u002F>\nYou may specify HTML5 or flash video, or both with one\u003Cbr \u002F>\nbeing primary content and the other as fallback.\u003C\u002Fp>\n\u003Cp>Here are some features of SWFPut to consider:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>SWFPut works directly with media file\u003Cbr \u002F>\nURL’s; that is, SWFPut does \u003Cem>not\u003C\u002Fem> embed\u003Cbr \u002F>\nthe video players of providers such as YouTube or Vimeo.\u003Cbr \u002F>\nSWFPut is for video files which are accessible by URL,\u003Cbr \u002F>\nwhether hosted at your site or off-site.\u003Cbr \u002F>\nThe setup form provides two media selection lists.\u003Cbr \u002F>\nThe first is a selection of files found (recursively)\u003Cbr \u002F>\nunder your wp-content\u002Fuploads directory. This list\u003Cbr \u002F>\nhas the advantage that it does \u003Cem>not\u003C\u002Fem> use the\u003Cbr \u002F>\nWordPress media library — it will find files that\u003Cbr \u002F>\nyou upload ‘by hand’ (with ftp, ssh, etc.). This feature\u003Cbr \u002F>\nwill work around upload size limits that might prevent\u003Cbr \u002F>\nyou from uploading large video files to the media library.\u003Cbr \u002F>\nThe second is a selection of files found in the\u003Cbr \u002F>\nWordPress media library and is presented with the\u003Cbr \u002F>\nfile name and the ‘attachment id’. This refers to files\u003Cbr \u002F>\nby ID, so it might be helpful if you manipulate media\u003Cbr \u002F>\nand expect ID associations to be valid. Files selections\u003Cbr \u002F>\nare filtered by name extension: FLV and MP4 for flash,\u003Cbr \u002F>\nand MP4, OGG and OGV, and WEBM for HTML5 video.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Video resources do not need to be on your site:\u003Cbr \u002F>\nany URL can be specified, so you may present players\u003Cbr \u002F>\nfor off-site of 3rd party resources.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>SWFPut does not interfere with the appearance of\u003Cbr \u002F>\na site: a video is presented jsut as an image\u003Cbr \u002F>\n(such as .png or .jpg) is, with the same sort of\u003Cbr \u002F>\nstyle, and optional caption. The appearance of the\u003Cbr \u002F>\nvideo control interface, or control bar, is simple\u003Cbr \u002F>\nand quiet so it should not clash with site design.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>SWFPut allows you to set the display aspect ratio\u003Cbr \u002F>\nfor the video. Some video is ‘anamorphic’ in that\u003Cbr \u002F>\nthe pixel width and height do not match the intended\u003Cbr \u002F>\nproportion of display width and height. You might\u003Cbr \u002F>\nfilm your child’s school play as 16:9 ‘widescreen’\u003Cbr \u002F>\nbut use a space saving feature of your recorder that\u003Cbr \u002F>\nsaves the video at 480×360 (which is not 16:9). You can\u003Cbr \u002F>\nset SWFPut to display the video at the intended 16:9\u003Cbr \u002F>\naspect ratio. You may set any aspect ratio (make it\u003Cbr \u002F>\ndistorted if you wish).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>The core features of the flash video player program\u003Cbr \u002F>\nincluded with SWFPut have been verified to work with\u003Cbr \u002F>\nthe Gnash free-software browser plugin, which is good\u003Cbr \u002F>\nif you care about free\u002Flibre software users. (At the\u003Cbr \u002F>\ntime of this writing, Gnash does not handle the MP4\u003Cbr \u002F>\nvideo container format, so it is preferable that you\u003Cbr \u002F>\nprepare flash video in the FLV container, even using the\u003Cbr \u002F>\nh.264 and AAC codecs. Of course, you may use MP4 if\u003Cbr \u002F>\nyou must.)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>The flash video player program included with SWFPut\u003Cbr \u002F>\nis written and compiled with the \u003Cem>Ming\u003C\u002Fem> PHP extension,\u003Cbr \u002F>\nand the code is included, so you may modify the player.\u003Cbr \u002F>\nThe HTML5 player is written JavaScript, and the original,\u003Cbr \u002F>\nun-minified version is included, so you may modify it.\u003Cbr \u002F>\nIn fact, the zip archive available at the WordPress\u003Cbr \u002F>\nrepository includes all sources, although a POSIX\u002FUnix\u003Cbr \u002F>\nenvironment with certain tools is required to build.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Localization sources are included; hopefully, polyglot\u003Cbr \u002F>\nusers will help with translations.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n","SWFPut provides video players for posts and pages and widget areas, as both HTML5 and flash video.",8050,0,"2020-08-12T12:00:00.000Z","5.5.18","4.3","",[27,28,29,30,31],"flash-video","graphics","html5-video","video","video-player","\u002F\u002Fagalena.nfshost.com\u002Fb1\u002Fsoftware\u002Fswfput-html5-flash-wordpress-plugin\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fswfput.3.1.0.1.zip",null,"2026-03-15T15:16:48.613Z",{"slug":37,"name":38,"version":39,"author":5,"author_profile":6,"description":40,"short_description":41,"active_installs":42,"downloaded":43,"rating":21,"num_ratings":21,"last_updated":44,"tested_up_to":23,"requires_at_least":45,"requires_php":25,"tags":46,"homepage":52,"download_link":53,"security_score":9,"vuln_count":21,"unpatched_count":21,"last_vuln_date":34,"fetched_at":35},"spam-blip","Spam_BLIP","1.0.8.1","\u003Cp>Spam BLIP stops comment and ping spam from being posted, primarily by\u003Cbr \u002F>\nchecking the IP address attempting to post a comment in one or more\u003Cbr \u002F>\nof the public DNS blacklists. A number of options are available\u003Cbr \u002F>\nto refine the check, and with the option defaults, a DNS lookup\u003Cbr \u002F>\nis only performed the first time an address \u003Cem>attempts to post\u003C\u002Fem> a\u003Cbr \u002F>\ncomment; thereafter, the address might quickly ‘pass’ because it\u003Cbr \u002F>\nwas not listed, or quickly be rejected because it was listed.\u003Cbr \u002F>\nSpam BLIP creates, and maintains, a database table for this purpose,\u003Cbr \u002F>\nand database lookups are quite fast. Therefore, concerns about\u003Cbr \u002F>\nDNS lookup time can be limited to an initial comment attempt.\u003C\u002Fp>\n\u003Cp>Here are some features of Spam BLIP to consider if you are\u003Cbr \u002F>\nnot yet falling over yourself to get it installed:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>When WordPress is producing a page for a visitor, it checks\u003Cbr \u002F>\nwhether comments are open for each post, and it allows plugins\u003Cbr \u002F>\nto “filter” the check. Spam BLIP uses that filter, but \u003Cem>does not\u003C\u002Fem>\u003Cbr \u002F>\ndo DNS lookups at this stage, because DNS lookups can take\u003Cbr \u002F>\nperceptible time. Spam BLIP \u003Cem>does\u003C\u002Fem> check optional user-set\u003Cbr \u002F>\nblack and white lists, and optionally existing comments that\u003Cbr \u002F>\nare marked as spam, and of course Spam BLIP’s own database records.\u003Cbr \u002F>\nThose checks are fast, so they should not have a perceptible\u003Cbr \u002F>\neffect on page loading. Furthermore, on pages with multiple\u003Cbr \u002F>\nposts, WordPress runs the filter for each, but Spam BLIP\u003Cbr \u002F>\nstores the first result, so even the fast checks are not\u003Cbr \u002F>\nrepeated.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>When a comment is actually submitted, Spam BLIP does the above\u003Cbr \u002F>\nchecks, then the DNS lookup only if necessary. At this stage,\u003Cbr \u002F>\nif the DNS lookup causes a perceptible delay, a real human\u003Cbr \u002F>\n(or \u003Cem>very\u003C\u002Fem> clever pet) making the comment should perceive it\u003Cbr \u002F>\nas mere server-side processing. As for spammer robots . . .\u003Cbr \u002F>\nlet them wait.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Spam BLIP comes configured with blacklist domains that have\u003Cbr \u002F>\nworked well during development, so a user should not need to\u003Cbr \u002F>\nbe concerned with the blacklists, but there is an advanced\u003Cbr \u002F>\noption to add or delete, activate or disable (yet save)\u003Cbr \u002F>\nlist domains, and configure the interpretation of a return\u003Cbr \u002F>\nfrom a successful lookup.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Spam BLIP provides user-set whitelist and blacklist options.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Spam BLIP provides options to check for pings\u002Ftrackbacks, and\u003Cbr \u002F>\nfor user registrations. (The option to blacklist-check user\u003Cbr \u002F>\nregistration is off by default. See “Tips” under the help\u003Cbr \u002F>\ntab on the Spam BLIP settings page.)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Spam BLIP provides options to configure a ‘Time To Live’ (TTL)\u003Cbr \u002F>\nfor its database records, and a maximum number of records.\u003Cbr \u002F>\nThe TTL is important because, generally, an IP address should\u003Cbr \u002F>\nnot be marked permanently. Consider an ISP that quickly\u003Cbr \u002F>\ndisables any account that is found to be spamming. An honest\u003Cbr \u002F>\nISP is also a victim of spammer abuse, and will need to reuse\u003Cbr \u002F>\naddresses. DNS blacklist operators provide means for IP\u003Cbr \u002F>\naddress owners to get records removed — Spam BLIP provides\u003Cbr \u002F>\na configurable TTL for its records. (Database table maintenance\u003Cbr \u002F>\nis triggered approximately hourly by a WordPress cron event.)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Spam BLIP will optionally check if a commenter address is a\u003Cbr \u002F>\nTOR exit node. TOR (The Onion Router) is an important protection\u003Cbr \u002F>\nfor people who need or wish for anonymity. You may want to\u003Cbr \u002F>\naccept comments from TOR users (you should), but unfortunately\u003Cbr \u002F>\nspammers have exploited and abused TOR, which has led some\u003Cbr \u002F>\nDNS blacklist operators to include TOR exit node addresses\u003Cbr \u002F>\nwhether or not it is known that the address is spamming. If you\u003Cbr \u002F>\nenable this option (you should), it might let some spam get\u003Cbr \u002F>\nthrough. In this case, mark the comment as spam, and use the\u003Cbr \u002F>\nSpam BLIP option to check existing comments marked as spam; or\u003Cbr \u002F>\nuse Spam BLIP in concert with another sort of spam filter, such\u003Cbr \u002F>\nas one that analyzes comment content. (Please report any\u003Cbr \u002F>\nconflict with other, non-DNS blacklist type spam plugins.\u003Cbr \u002F>\nNote that Spam BLIP is not expected to work in concert with\u003Cbr \u002F>\nother DNS-type anti-spam plugins.)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Spam BLIP includes a widget that will show options and records\u003Cbr \u002F>\ninformation. The widget might or might not be an enhancement\u003Cbr \u002F>\nto your page, but in any case it should provide feedback\u003Cbr \u002F>\nwhile you evaluate Spam BLIP, so it might be used temporarily.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n","Spam BLIP stops comment spam before it is posted, using DNS blacklists, existing comments marked as spam, and user defined lists.",10,2711,"2020-09-25T15:46:00.000Z","4.2",[47,48,49,50,51],"anti-spam","blog-spam","comment-spam","spam","spam-comments","\u002F\u002Fagalena.nfshost.com\u002Fb1\u002Fsoftware\u002Fspam-blip-wordpress-comment-spam-plugin\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fspam-blip.1.0.8.1.zip"]