fupio

Fupio is the easiest way to share online Learn more »

Join Fupio

#wassup

Tantek Çelik
Tantek Çelik
How to add MapQuest with a search shortcut to your Firefox:
1. open Firefox Preferences ("Firefox" menu, "Preferences" item)
2. select "🔍 Search" from the left column
3. click the [ + Add search engine ] button
4. enter "MapQuest" into the Search engine name field (without quotes)
5. enter "https://www.mapquest.com/search/%s" into the URL field (without quotes)
6. enter "m" into the Keyword field (without quotes)
If you already had an "m" search shortcut for another search engine, you may

#wassup#wassup2026#mapquest#search#searchshortcut#firefox#firefoxsearch#searchengine

tantek.comHow to add MapQuest with a search shortcut to your Firefox: 1. open Firefox Preferences ("Firefox" menu, "Preferences" item) 2. select "🔍 Search" from the left column 3. click the [ + Add search engine ] button 4. enter "MapQuest" into the Search engine name field (without quotes) 5. enter "https://www.mapquest.com/search/%s" into the URL field (without quotes) 6. enter "m" into the Keyword field (without quotes) If you already had an "m" search shortcut for another search engine, you may need to first edit that search engine (click the pencil ✏️ icon next to it) in the list of "Additional search engines", and remove/replace the existing "m" with something else. Now when you want to look up something on a map, you can type an 'm ' (without the quotes) into the browser URL/adress bar, enter an address or venue name, press return and get a result in MapQuest. This is my third #WASSUP #WASSUP2026 post, and second useful web tip for September. #MapQuest #search #searchShortcut #Firefox #FirefoxSearch #searchEngine #map #maps #GoogleMaps #AppleMaps #LakeOntario #tip #webTip #browserTip #webBrowserTip #searchTip - Tantek
Tantek Çelik
Tantek Çelik
If you find a wiki page seemingly from a MediaWiki, but without a "View History" link, here’s a tip for how to find it.
Example: the old HTML Working Group (WG) wiki at W3C
  • https://www.w3.org/html/wg/wiki/Main%5FPage
Note the warning at the top: “This wiki has been archived and is now read-only.”
Aside: many years ago, each group at W3C had their own MediaWiki install, in a different path and disconnected from both every other group’s wiki, and the top level general W3C wiki

#wassup#wassup2026#wiki#wikipage#mediawiki#viewhistory#w3c#htmlwg

tantek.comIf you find a wiki page seemingly from a MediaWiki, but without a "View History" link, here’s a tip for how to find it. Example: the old HTML Working Group (WG) wiki at W3C * https://www.w3.org/html/wg/wiki/Main_Page Note the warning at the top: “This wiki has been archived and is now read-only.” Aside: many years ago, each group at W3C had their own MediaWiki install, in a different path and disconnected from both every other group’s wiki, and the top level general W3C wiki (http://www.w3.org/wiki). I pointed out this made no sense, since groups more often than not had overlaps in documentation, technology, practices and would of course benefit from wiki-syntax interlinking. This was never really fixed at an infrastructure level, it had to be fixed at a cultural level, convincing working groups one by one to use the general W3C wiki, and ignore any WG-specific wiki. The other apparent hazard of having a WG-specific wiki is they can be (and have been) shutdown or frozen (like the example given), breaking any chance of fixing typos, other minor errors, or creating redirects to where the work has been restarted subsequently. Note also the lack of a "View History" link as a tab top right adjacent to the content area (or anywhere else on the page). This is likely because the page has been archived as static HTML, preserving the markup and styling, but removing any editing or history browsing or diffing or any other form submission based features that would require a dynamic backend like MediaWiki. Here is how to find such a page’s history: 1. Find the “last modified” date in the footer and note the year, month, day. 2. Check for the page in the Internet Archive, e.g. prepend its URL with "https://web.archive.org/web/" 3. If there’s (presumably) still no "View History" link, look at the year month day numbers in the URL — the first 8 digits after "/web/" E.g. "20260512" for this page as of today. 4. Replace those 8 digits with the year, month, day noted in step 1, with 4, 2, 2 digit numbers respectively. E.g. "20150623" for this page. Press return to load that. 5. You may have to "close toolbar" the (x) in the top right of the page content. 6. Note the "View History" link, click it. Presto, view history on a former MediaWiki page that’s been archived to static HTML. This is my second #WASSUP #WASSUP2026 post, and first useful web tip. #wiki #wikiPage #MediaWiki #ViewHistory #W3C #HTMLWG #wikiArchived #readOnly #staticHTML #InternetArchive #WaybackMachine #LastModified - Tantek
Tantek Çelik
Tantek Çelik
Welcome to September! Time for a new blogging challenge for the month. After some ideation, here’s my proposed September blogging challenge, on topics I find myself reading and posting about, with an emphasis on pragmatism:
The Web And Standards September Useful Posts blogging challenge
Or the #WASSUP challenge for short.
I really enjoyed the #Blaugust blogging challenge last month (31 posts ✅ — summary in another post), and not feeling a resonance with the two prior September challenges

#wassup#blaugust#wassup2026#blog#blogging#bloggingchallenge#september#web

tantek.comWelcome to September! Time for a new blogging challenge for the month. After some ideation, here’s my proposed September blogging challenge, on topics I find myself reading and posting about, with an emphasis on pragmatism: The Web And Standards September Useful Posts blogging challenge Or the #WASSUP challenge for short. I really enjoyed the #Blaugust blogging challenge last month (31 posts ✅ — summary in another post), and not feeling a resonance with the two prior September challenges noted on the IndieWeb wiki, decided to come up with my own. Iterated on some ideas yesterday until arriving at WASSUP (yes, as a backronym, inspired somewhat by WHATWG which also has WHATNOT and WHATUP meetings). Similar to Blaugust: * 30 posts during the month of September (1 per day if you wish, or double/triple-up to get ahead or catch-up) Topic: * Anything *useful* (features, tips) about open web standards, the open web as a whole, web browsers, or web services like search engines. Hashtags: * #WASSUP #WASSUP2026 And that’s it. If those are topics you already blog about, great, join in using the hashtags and share what you find useful about them! Otherwise, take a look at how you frequently use the Web, and post what you have found useful, especially the most useful for you. Blog clever tips about how you have made better use of the Web, web browsers, search engines etc. If you’re a web developer or designer, share what you find most useful about web standards, your choice, either in their entirety or of individual features, like HTML elements, attributes, CSS properties, Selectors, DOM features, WebAPIs, standard media formats on the web, etc. Let’s see what positive pragmatic things we can share with each other about the web and how it works in practice. Glossary: Blaugust: * https://indieweb.org/Blaugust blogging challenge: * https://indieweb.org/blogging_challenge September blogging challenges: * https://indieweb.org/September#Challenges standards * https://indieweb.org/standards #blog #blogging #bloggingChallenge #September #web #openWeb #webStandards #openWebStandards #webDev #webDevs #webDeveloper #webDevelopers #webDesign #webDesigns #webDesigner #webDesigners #useful #pragmatic This is post 20 of #100PostsOfIndieWeb. #100Posts #indieweb ← https://tantek.com/2026/243/t1/many-paths-indieweb-custom-domain → 🔮 - Tantek

Posts tagged #wassup appear here.