$ docker
! www.der-postillon.com - hide steady floating button | |
www.der-postillon.com###steady-floating-button-wrapper | |
! www.youtube.com - hide Premiere garbage (hides any premiering/announced videos until they are an actual video) and shorts [https://www.reddit.com/r/uBlockOrigin/comments/143mdqv/code_to_block_youtube_shorts_june_2023/] | |
youtube.com##:xpath(//ytd-rich-item-renderer[descendant::span[contains(text(),"UPCOMING")]]) | |
youtube.com##:xpath(//ytd-rich-item-renderer[descendant::p[contains(text(),"PREMIERE")]]) | |
youtube.com##:xpath(//ytd-rich-item-renderer[descendant::span[contains(@aria-label,"Shorts")]]) | |
youtube.com##:matches-path(/feed/subscriptions) ytd-rich-grid-row, #contents.ytd-rich-grid-row:style(display:contents !important;) | |
youtube.com##:matches-path(/feed/subscriptions) ytd-rich-section-renderer:has-text(Shorts) | |
youtube.com##:matches-path(/feed/subscriptions) ytd-rich-shelf-renderer:has-text(Shorts) |
<?php | |
//API URL | |
$url = ''; | |
$ch = curl_init($url); | |
$jsonDataEncoded = file_get_contents('php://input'); | |
curl_setopt($ch, CURLOPT_POST, 1); | |
curl_setopt($ch, CURLOPT_POSTFIELDS, $jsonDataEncoded); |
WordPress is popular because it's easy to setup without much technical know-how. However, to build a more robust PHP project with command line deployments, updates and ongoing maintenance, working with WordPress out-of-the-box raises specific challenges:
- How can we make our WordPress projects portable between developers?
http://ogp.me/ | |
https://moz.com/blog/meta-data-templates-123 | |
https://search.google.com/structured-data/testing-tool | |
https://developers.facebook.com/tools/debug/og/object - https://developers.facebook.com/docs/reference/opengraph | |
https://cards-dev.twitter.com/validator - https://dev.twitter.com/cards/types | |
https://developers.pinterest.com/tools/url-debugger/ - https://developers.pinterest.com/docs/rich-pins/overview/ | |
https://developer.linkedin.com/docs/share-on-linkedin |
I've been looking for the best Linux backup system, and also reading lots of HN comments.
Instead of putting pros and cons of every backup system I'll just list some deal-breakers which would disqualify them.
Also I would like that you, the HN community, would add more deal breakers for these or other backup systems if you know some more and at the same time, if you have data to disprove some of the deal-breakers listed here (benchmarks, info about something being true for older releases but is fixed on newer releases), please share it so that I can edit this list accordingly.
- It has a lot of management overhead and that's a problem if you don't have time for a full time backup administrator.
var url = 'http://www.google.com'; | |
var load = $('<div>'); | |
var content = ''; | |
load.load(url, function(result){ | |
content = load.html(); | |
}); |
<?php namespace Vendor\Library; | |
use Another\Vendor\Library\ClassName; | |
abstract class ClassName extends AnotherClass implements Countable, Serializable | |
{ | |
const CONSTANTS = 'top'; | |
use someTrait, anotherTrait { | |
anotherTrait::traitMethod insteadof someTrait; |
function string_to_slug (str) { | |
str = str.replace(/^\s+|\s+$/g, ''); // trim | |
str = str.toLowerCase(); | |
// remove accents, swap ñ for n, etc | |
var from = "àáäâèéëêìíïîòóöôùúüûñç·/_,:;"; | |
var to = "aaaaeeeeiiiioooouuuunc------"; | |
for (var i=0, l=from.length ; i<l ; i++) { | |
str = str.replace(new RegExp(from.charAt(i), 'g'), to.charAt(i)); | |
} |