Archive for 2023
Posted by jpluimers on 2023/07/07
Need to check out which of these filters still work:
[Wayback/Archive] How To Use Twitter Search – Advanced Guide by @Luca – Fresh van Root
| Operator |
Description |
| since:2019-05-06 |
Tweets published at or after the date. (UTC +0) |
| until:2019-05-07 |
Tweets published before the date. (UTC +0) |
| from:Luca |
Tweets that are not marked as sensitive media. Tweets published by a specific user. |
| to:Luca |
Replies and mentions for a specific user. |
| lang:de |
Tweets in a specific language. Language is detected by Twitter on a Tweet basis. “und” for Tweets where Twitter was unable to determine a language. |
| near:Berlin within:5km |
[unreliable] Tweets that were posted in specific locations and optionally within a certain range. |
| min_faves:5 |
Tweets with at least that amount of faves. |
| -min_faves:100 |
Tweets that have fewer faves than specified. |
| min_retweets:10 |
Tweets that were at least retweeted that many times. |
| -min_retweets:3 |
Tweets that were retweeted less than that many times |
| min_replies:70 |
Tweets that got a minimum amount of replies. |
| -min_replies:8 |
Tweets that got fewer replies. (max_replies does not work) |
| filter:follows |
Tweets by accounts you follow. |
| list:Luca/Science |
Tweets by accounts on a specified list. |
| filter:verified |
Tweets by verified accounts. |
| filter:images |
Tweets with an image. |
| filter:links |
Tweets with an URL. |
| filter:media |
Tweets with a video or a photo. |
| filter:retweets |
[only works with the API or with “include:nativeretweets”] Retweets. |
| filter:quote |
Tweets that contain a quoted Tweet. |
| filter:replies |
Tweets that are a reply. |
| filter:mentions |
Tweets that mention a user. |
| filter:videos |
Tweets that contain a video. |
| filter:native_video |
Tweets that contain a video, that was directly uploaded to Twitter. |
| filter:news |
[unreliable] Tweets that contain a URL to a news source. |
| filter:safe |
[unreliable] Tweets that do not contain sensitive material. |
| include:nativeretweets |
It allows you to search through retweets as well. Especially useful in combination with from:account or filter:follows. |
–jeroen
Posted in Power User, SocialMedia, Twitter | Leave a Comment »
Posted by jpluimers on 2023/07/06
Some links on the unexpected turn of events after [Archive] Jeff Geerling (@geerlingguy) / Twitter posted
First his site got more traffic because of the post, then within an hour traffic exploded because of a DDoS overflowing both his Raspberry Pi cluster and his mobile data capacity.
Jeff will likely do blog posts on these and update the underlying GitHub repository at [Wayback/Archive] geerlingguy/turing-pi-2-cluster: Turing Pi 2 Cluster , but until then (since his Tweets were not threaded), this is what happened on 20220209 as it taught me a few bits:
Read the rest of this entry »
Posted in Cloud, Cloudflare, Containers, Development, Docker, Hardware Development, Infrastructure, Internet, Kubernetes (k8n), LifeHacker, OpenSpeedTest, Power User, Raspberry Pi, SpeedTest | Leave a Comment »
Posted by jpluimers on 2023/07/05
In Another difference between the and element in HTML&XHTML, I mentioned Stephan Kämper taught be about the W3C HTML NU validator in [Archive] Stephan Kämper on Twitter: “I try to write fairly simple & #valid #HTML ➙ …gist..Validating it with …online HTML-Validator…, I get the error ‘No p element in scope but a p end tag seen.‘ What? Why? Removing the list from the HTML, gets rid of the error… Why?!? I. don’t. get it. 1/2″ / Twitter.
Upon closer inspection, there are actually two w3c.org HTML validators, each operating in three modes:
- Default checker which is DTD-based:
This validator checks the [Wayback/Archive] markup validity of Web documents in HTML, XHTML, SMIL, MathML, etc. If you wish to validate specific content such as [Wayback/Archive] RSS/Atom feeds or [Wayback/Archive] CSS stylesheets, [Wayback/Archive] MobileOK content (now retired), or to [Wayback/Archive] find broken links, there are [Wayback/Archive] other validators and tools available. As an alternative you can also try our [Wayback/Archive] non-DTD-based validator.
- [Wayback/Archive] The W3C Markup Validation Service:
#validate_by_uri mode (without #validate_by_uri URL fragment) and
default: checks the HTML of a URL
- [Archive] The W3C Markup Validation Service: #validate_by_upload mode
you upload a file of which the HTML then gets checked
- [Archive] The W3C Markup Validation Service: #validate_by_input mode
you enter the HTML to be checked into a text box
- NU checker which is non-DTD-based:
- [Wayback/Archive] Ready to check – Nu Html Checker;
#address mode (without #address URL fragment) and
default: checks the HTML of a URL
- [Archive] Ready to check – Nu Html Checker:
#file mode
you upload a file of which the HTML then gets checked
- [Archive] Ready to check – Nu Html Checker:
#textarea mode
you enter the HTML to be checked into a <textarea> element
Notes:
- that all three above modes get selected by a URL fragment (after a
# hash) which the Wayback machine cannot individually save, but Archive.is can, hence the non-default URLs are not saved only in Archive.is, and not in the Wayback machine.
- The DTD-based checker seems non-functional and redirects all requests to the non-DTD-based checker.
I also took a look at the Wayback machine saved pages under the direct URLs of both checkers:
- https://web.archive.org/web/*/https://validator.w3.org/*
- https://web.archive.org/web/*/https://validator.w3.org/nu/*
I learned that the NU validator accepts at least these arguments:
Note that you cannot do this directly with HTML files saved in a gist or GitHub repository because it serves all RAW files as
[Wayback/Archive] text/plain MIME type. You can work around this by using a raw.githack.com trick I explained before at:
I also amended my above reply with more information using the ?doc= parameter with RAW gist files and archived that thread at [Wayback/Archive] Thread by @jpluimers on Thread Reader App – Thread Reader App.
–jeroen
Posted in Development, HTML, HTML5, Software Development, Web Development | Leave a Comment »
Posted by jpluimers on 2023/07/02
I quickly hacked together this JavaScript Bookmarklet today, so it is without any checks and assumes you have enabled one Mastodon account for publishing, that you are hosting your blog on WordPress.com, and using the Classic Editor:
javascript:(function(){
publicizeFormEditHref = document.getElementById('publicize-form-edit');
publicizeFormEditHref.click();
mastodonCheckboxes = document.getElementsByClassName('wpas-submit-mastodon');
mastodonCheckboxes[0].checked = true;
publicizeFormHideHref = document.getElementById('publicize-form-hide');
publicizeFormHideHref.click();
updateButtonHref = document.getElementById('publish');
updateButtonHref.click();
})();
The above code is the state of [Wayback/Archive] JavaScript Bookmarklet for the WordPress classic editor which enables mastodon publishing (assuming you have one mastodon publishing account enabled … ) and due to be improved in a later blog post.
This will enable the currently edited post to be published to Mastodon, then update/publish the post.
On enabling one Mastodon account for publishing:
Read the rest of this entry »
Posted in Bookmarklet, Development, HTML, JavaScript/ECMAScript, Mastodon, Power User, Scripting, SocialMedia, Software Development, Twitter, Web Browsers, Web Development, WordPress, WordPress | Leave a Comment »
Posted by jpluimers on 2023/07/01
In other news since yesterday [Wayback/Archive] Twitter now requires an account to view tweets | TechCrunch
Like many of Twitter’s recent changes, this could easily backfire. If tweets aren’t publicly accessible, search engine algorithms could rank the site’s content lower, meaning that fewer people would be directed to the site from Google.
This not only hampers SEO, but any anonymous access to tweets resulting in Twitter to have become a walled garden without any prior announcement.
As of yesterday, this for instance makes it way harder for researchers to access Twitter in a non-biased way (the Twitter Algorithm will always bias the timeline for an account). It also prohibits the Wayback Machine from archiving Tweets (which I rightnow cannot archive):
https://twitter.com/jpluimers/status/1675070261274484736
Twitter is now more restricted than LinkedIn or Facebook, so I think it is a next step of burning the Twitter Equity to the ground followed after many other steps scaring Twitter users away, for instance as of:
Read the rest of this entry »
Posted in Facebook, LinkedIn, SocialMedia, Twitter | Leave a Comment »
Posted by jpluimers on 2023/07/01
Posted in About, Personal | Leave a Comment »
The Wiert Corner - irregular stream of stuff 