Replying to @Jakeypoo3333 @Vlamsss
If they can't fight a war without resorting to war crimes/crimes against humanity then they shouldn't launch terror attacks into Israel to begin with.
I can do much, much worse.
Let's talk about the wonderful world of functions in WordPress.
Function Names
the_title() prints the post's title.
get_the_title() returns it.
Makes sense. Add "get_" and you get the value back.
Except the_title() can return too, if you call it like the_title('', '', false). Why would you do this over just calling get_the_title()? Good question, moving on.
the_permalink() prints the post's permalink.
get_permalink() returns it.
Where did "the" go? Doesn't matter. WP later added get_the_permalink() too, so this is one of the few cases where a naming inconsistency was actually addressed. This will be the last time this happens.
the_content() prints the post's content.
get_the_content() returns the content as a string, minus the filters that render shortcodes and blocks, so the printer and the getter give you two different results.
the_date() prints the post's date. Except if the previous post in the current query loop was posted the same day, then it prints nothing.
get_the_date() always returns the current post's date.
get_the_tags() is plural, and returns an array of WP_Term objects.
get_the_category() is singular, and returns... also an array of WP_Term objects.
is_email() returns the given email string when it's valid and false when it's not (rather than just returning true).
is_home() returns true on the site's generic post index page, not the site's home page.
is_front_page() returns true on the site's home page.
is_admin() checks whether the current request is for a WP dashboard page. The logged in user's role never comes up, let alone checking if that user is an administrator.
is_super_admin() actually checks if the logged in user is an administrator (has never been a "super administrator" role).
sanitize_title() doesn't sanitize a title, it turns it into a slug.
check_admin_referer() doesn't check a referrer, it checks a nonce.
wp_localize_script() is used to pass PHP data to frontend JS, it's almost never used for localization.
wp_get_current_user() has a "wp_" prefix.
get_current_user_id() doesn't.
This one makes sense because get_current_user() is already a PHP built-in function unrelated to WP. This is (probably) the only time a "wp_" prefix will have a good excuse to exist, for the rest of this post they'll be completely arbitrary.
wptexturize & wpautop do not use typical prefix names. Don't ask why.
Function Returns
Many functions return either false, 0, or a WP_Error object to indicate failure. There is barely any rhyme or reason to when this happens. For example:
wp_insert_post() returns the created post ID on success, or the int 0 or a WP_Error object on failure.
add_post_meta() returns the created meta ID on success, or false on failure.
get_template_directory() gives you the current theme's directory. Except if it's a child theme (a theme that relies on another "parent" theme), then it gives you the parent theme's directory instead.
get_stylesheet_directory() gives you the current theme's directory even if it's a child theme.
Both parent & child themes have templates & stylesheets.
get_header() returns nothing. It just includes a theme's "header.php" file (if it exists). Same with get_footer(), get_sidebar(), and get_template_part() with their own related theme PHP files.
Function Parameters
PHP did not have named parameters, only positional ones until PHP 8.0. This meant in the worst cases that functions like get_links() would look like this if you wanted them to return the string rather than print it directly, but otherwise wanted the default behavior (the last parameter is the actual "$display/return" parameter):
get_links(-1, '', '<br />', ' ', true, 'name', true, false, -1, 1, false)
(this function was deprecated, but is still callable/functional)
WP fixed this at the time by making most functions accept a key/value array parameter where you could set specific named parameters clearly and would otherwise get defined defaults.
This generally went fine but various parameter values were not implemented cleanly, e.x:
get_search_form() and wp_nav_menu() print by default, you have to pass array('echo' => false) to have them return instead of print.
wp_get_archives() and wp_list_categories() do the same thing but you have to pass array('echo' => 0) this time.
get_calendar() and the_title() still use positional parameters for their "$display/echo" option.
get_the_terms(post, taxonomy) takes the post first.
has_term(term, taxonomy, post) takes it last.
There are countless examples of weird inconsistent parameter placement like this.
I can go on. There's so much more to talk about when it comes to WP.
(All of the things I discussed above are still present in the latest WP version)
Brink retweeted
You should be extremely cautious about accepting at face value claims by people who believe lying is an acceptable way to advance their cause theatlantic.com/ideas/2026/1…
✡️ Benjamin Netanyahu Toenail Clippings ✡️
Vintage: September 2026 (pre-indictment stress growth)
This quoted post is unavailable.
Is Piker not abetting a genocide by running disinformation & propaganda campaigns for the ones committing it? And you're aware that disinformation campaigns can frequently be more deadly than any bullet or bomb.
So if you're not "defending Piker" then you've got no reason to concede he's abetting at least one genocide.









