Distribution of solar, uranium, and oil densities across nations. Data are from EIA (2019) for oil; OECD (2019) for uranium; UNdata (2019) for area; and OpenEI (2019) for solar illumination. The x- and y-axes share the same logarithmic scaling. Countries with land area below 5000 km2 are not included.
Nice! These are the underlying sources of data for the image shared on twitter
7 Most Popular JavaScript Libraries in 2021
Some call them the lifecycle methods of elements which I think is an apt description.
MAFF files are standard ZIP files containing one or more web pages, images, or other downloadable content. Additional metadata, like the original page address, is saved along with the content.
Unlike the related MHTML format, MAFF is compressed and particularly suited for large media files.
There is no need for metadata, attributes, properties, opening and closing tags or whatever fancy words or concepts we can come up with, we just need simple objects with key-value information.
Trying to consolidate [[SGML]]'s lack of key-value paid & arrays vs [[JSON]]'s lack of attributes and spanning extents.
Die-hard developers are waging an endless holy war against the ignorant lowlifes who refuse this concept in a quest to convert everyone to their cause.
Here it is an typicall article mocking everybody not respecting HTML semantics that i didn't even know existed - but it had a point!
[2020] Basics of Module Bundlers for web development
Modern browsers that support the File System Access API (Edge and Chrome today) allow web pages to access the local file system (with your permission).
The work done must be measured and must be part of a pre-existing environmental strategy.
This implies uniformity in how you report it. If you have an attributional approach for measuring impact at an organisational level, you'll need a way to convert between the two if you are using a consequential method for a project.
Web Browser Engineering by Pavel Panchekha & Chris Harrelson https://browser.engineering/
A Web Browser Built for Me by Robin Rendle https://www.robinrendle.com/notes/a-web-browser-built-for-me/
I think of the Kindle and what enormous potential that browser had to change our relationship with the internet, to push it towards a web that you read (instead of one that tries so very hard to read you).
I love the phrase "a web that your read instead of one that tries so very hard to read you."
Manage citations for your research
Organizations today typically must assess their spending records and then look up tables that estimate the average emissions associated with them. This falls far short of what the world really needs, which is the ability to pull accurate and near real-time data directly from the emissions sources themselves.
OK, so this suggests they're intending to eventually replace the extended environmental input output models that are the defaults in most carbon accounting tools with their own models.
My guess is this would be their moat in many cases.
a way to transparently discover related blogs that avoids hidden algorithms
Bristly pop cultural misuse of the term "algorithm" notwithstanding, a better solution that I haven't come across anyone else mention: make them explicit, not hidden.
When it look like Dat might've had enough steam to take off (ca. 2017–2018), I wrote a draft straw proposal for how to solve the "discovery problem" with e.g. Fritter—i.e. the problem that because you only "receive" replies and other messages by checking the feeds of the people you're following, you'll be unable to reply engage with strangers who appear (or have a stranger engage with you in their thread) unless something happens like a mutual acquaintance alerting you out of band ("hey, did you see @foo's reply dat://foo.example.net/posts/ukifxdgbh.json?").
The idea is that there is a special kind of feed operated by some service provider that specializes in doing exactly that. If you find Facebook valuable, for example, then you are free to opt in and subscribe to the Facebook analog that pays attention to all feeds and works to surface interesting content for you. Under this model, unlike the Facebook regime, "leaving" is as simple as unsubscribing to that feed (and going with a different provider if you want).
There will be three billion gamers by next year, according to a Newzoo study. And as Loftus puts it: “People are going to need to wear something.”
THIS is it - web 3 is making consumers mutiplicitous - opens marketts WITHIN games, subworlds that can be exploited / marketed to / fashion trends will sweep games, online subcultures (maybe) - people have markeable personas on and off the web, new context for targeted advertising / commerce.
Will cannabalize physical economies?
Accessorize for a zoom meeting - digital suits, etc digital costumes. Something to wear at digital concerts, in games; your Perona will not be birthed into the metaverse clothed, accessorized...
Assets will be portable across platforms.
NFTs are compatible with anything built using Ethereum. An NFT ticket for an event can be traded on every Ethereum marketplace, for an entirely different NFT. You could trade a piece of art for a ticket!
There - opens up GIGANTIC barter economy possibilities - will shut out old middle men & create new ones - swap airline tickets / hotel reservations for concert tickets or memorabilia
We did most of the heavy lifting for you to provide a default stylings that incorporate our custom components.
(The English here sounds awkward.)
Gyuri Lajos, in the Stop Reset Go team, recommended using Materialize CSS.
If it is based on Google’s Material Design, there are a lot of resources available to explore the possibilities. If I was building a Progressive Web App, this might be the place to start.
The project appears to be at an early stage of development, with a 1.0.0 release.
No annoying focus ring
hiss-boo. i like the accessibility.
How to Create a Social Media Platform: Technologies, Features, and Cost
Ensuring that the regional market is competitive and that there are incentives for companies to buy local cloud infrastructure is a role that only government actors can fulfill. Moreover, it is a responsibility that is clearly within their mandate. Not coincidentally, such an approach clearly aligns with the European Commission’s and some European Union member state governments’ laudable competition and antitrust strategies, echoing attempts to safeguard the European market and uphold strong values throughout the EU.
This is literally the opposite of how it works right now, with some procurement specifying AWS
It’s true! None of these tactics, on their own, will address complex, deep-rooted social problems. But each of them represents a potential pathway that we can ascend when other routes are blocked.
Useful framing in the syllabus.
We have some idea of the goals, and talking in terms of methods provides options to suite the context
Private links One must be able to add one's own private links to and from public information. One must also be able to annotate links, as well as nodes, privately.
# 21:30 @voxpelli ↩️ Better to name things for what they are rather than trying to make it into something else through deceptive names like "web 3.0". I mean, eg. the IndieWeb could also have called itself "web 3.0", I guess Mastodon could as well. There truly must be a better name? (twitter.com/_/status/1442601857105346560)
The conversation here makes me wonder about the idea of a more humanist web following onto the humanist movement in the 1400-1500s.
Bibleref is a simple approach to automatically identifying Bible references that are embedded in blog posts and other web pages. This enables search engines, content aggregators, and other automated tools to correctly label the references so they're more easily searchable. Bibleref is part of a general movement toward markup that expresses more semantic, rather than presentational, element.
You can choose the displayed language by adding a language suffix to the web address so it ends with e.g. .html.en or .html.de. If the web address has no language suffix, the preferred language specified in your web browser's settings is used. For your convenience: [ Change to English Language | Change to Browser's Preferred Language ]
you're guilty of making the same mistake as people who used to say that templates and styles and JavaScript should be in separate files
At last, another one realizing that they ha dbeen structuring MVC web-apps counter-intuitively for decades.
This is not a published Chrome extension and it uses an odd workaround to circumvent Chrome security. So I'm not sure how safe it is. Keep an eye on it; if it develops enough, it could be quite useful.
Around 1:48:00
What if every library that you use had, like, some interactive documentation or interactive representation? [...] The author could maybe add annotations.
目录结构
test
playing house
This is how I feel about most people's personal websites. Few people have homepages these days, but even for people who do, even fewer of those homes have anyone really living there. All their interesting stuff is going on on Twitter, GitHub, comments on message boards...
Really weird when this manifests as a bunch of people having really strong opinions about static site tech stacks and justifications for frontend tech that in practice they never use, because the content from any one of their profiles on the mainstream social networks outstrips their "home" page 100x to 1.
2020 is the year in which the current Dutch subsidy scheme for renewable energy, the Renewable Energy Production Incentive Scheme (de stimuleringsregeling duurzame energieproductie (SDE+)), will change. From 2020 onwards, the SDE + will be broadened to achieve the target of a 49 percent reduction in CO2 emissions in the Netherlands by 2030 (or at least to keep this goal within reach). The broadened SDE+ focuses on the reduction of greenhouse gas emissions (CO2 and other greenhouse gases). This will change the focus from energy production to energy transition. The broadened subsidy scheme is therefore called the Renewable Energy Transition Incentive Scheme (SDE++).
So, this is the expanded version that is focussed on a more holistic, systemic approach
Ensure there's only one version of your site running at once. That last one is pretty important. Without service workers, users can load one tab to your site, then later open another. This can result in two versions of your site running at the same time. Sometimes this is ok, but if you're dealing with storage you can easily end up with two tabs having very different opinions on how their shared storage should be managed. This can result in errors, or worse, data loss.
I wonder how can we identify issues like this when they occur
Web I Projects: 2015 - 2020
Which of the projects listed on this webpage that you have liked? and why?
if(document.getElementById('myIframe').readyState == 'complete')
But those inline scripts will be “render blocking”, so not the best regarding overall page performance.
render blocking
I looked at workflows that were similar to GitHub Pages. I realized that what I was craving was very simple: Write text. Put on internet. Repeat.
building software visualization tools as web ap-plications can help in making them available to a larger audi-ence
I need a solution for auto-adjusting the width and height of an iframe to barely fit its content. The point is that the width and height can be changed after the iframe has been loaded.
resize the iFrame after the contents are modified
All solutions given thus far only account for a once off resize.
Make iframe automatically adjust height according to the contents without using scrollbar? [duplicate] Ask Question
onload="setIframeHeight(this)"
With JavaScript, you can actually calculate the width of the scrollbar and whether it’s visible by comparing two properties—window.innerWidth and document.body.clientWidth. If these are equal, the scrollbar isn’t visible. If these are different, we can subtract the body width from the window width to get the width of the scrollbar:const scrollbarWidth = window.innerWidth - document.body.clientWidthWe’ll want to perform this both on page load and on resize, in case someone resizes the window vertically and changes the overflow. Then, once we have the scrollbar width, we can assign it as a CSS variable:document.body.setProperty("--scrollbarWidth", `${scrollbarWidth}px`)
missing feature: vw/vh can't be used "directly" because doesn't account for scrollbars
I'm wondering exactly what problem that LOUD standard is meant to be solving exactly? It doesn't appear that any of the meta data they're listing is over and above anything that's already extant?
If you're going to propose a new set up, why not add some bits to fix the newer problems that have popped up like for paying creators? Being able to inject ads? Better track the number of listens? How far into the file did the listener get? How many ads did they hear?
And let's not forget:
DCOP
there's some other good little nuggets about but a DCOP shout out is probably the best. today the only programmable/malleable software we have is the web, and DCOP was a more extensive hooks into the heart of a system than what we can do with the web.
Hire Dedicated Developers
A subscription to a paper journal provides the library with an archival copy of the content. Subscribing to a Web journal rents access to the publisher's copy.
It's hard to convey what a difference it makes to the development experience to cut out this massive tumor of complexity.
making the web an alive medium again and not a preprocessed nightmare nightmare is critical
alas: typescript.
The resilience of any such ecosystem is equal to it's diversity + interconnectedness.
Also see
https://benmyers.dev/blog/on-the-dl/
Curious double entendre title here.
Note to self: I should use these patterns more.
The web should be a two-way thing
We hoped that posting anonymous discussion notes made the barrier to engagement even lower, as it allowed people to engage asynchronously and to catch up before the next discussion.
Was this hope born out?
Funnily enough, I've been on an intellectual bent in the other direction: that we've poisoned our thinking in terms of systems, for the worse. This shows up when trying to communicate about the Web, for example.
It's surprisingly difficult to get anyone to conceive of the Web as a medium suited for anything except the "live" behavior exhibited by the systems typically encountered today. (Essentially, thin clients in the form of single-page apps that are useless without a host on the other end for servicing data and computation requests.) The belief/expectation that content providers should be given a pass for producing brittle collections of content that should be considered merely transitory in nature just leads to even more abuse of the medium.
Even actual programs get put into a ruddy state by this sort of thinking. Often, I don't even care about the program itself, so much as I care about the process it's applying, but maintainers make this effectively inextricable from the implementation details of the program itself (what OS version by which vendor does it target, etc.)
the Web has graduallyevolved from the original static linked document modelwhose language was HTML, to a model of intercon-nected programming environments whose language isJavaScript
All rights reserved © Wireframes Corporation 2021 About Company Services Testimonials Get in Touch
Make these Footer Links Work
Sign up to our newsletter
Create a General List in Mautic and setup a Broadcast Email Segment. Create a Mautic form for the broadcast list and link form data in here
You're amazing. Start Acting Like It. Live a limitless life of your own design. Step up and answer a few questions on the form to connect!
What text should I put here?
Live your best life. In a collaboration with Rooz Yavari of Boundless Embodiment, this weeklong event will get you over your fears, inner demons, and push you to step up to the next level of your potential.
Put a button below this that Links to the Advanced Seminar Landing Page
Come for the weekend in a city near you and work with David and his coaches to crush inner doubts and fears, releasing you to the next level.
Put a button below to link to the schedule page
Come get the limitless experience live.
Put a button below this that leads to the Week Long Advanced Landing Page. See Github Issue #4
that's why I bolded "same column" with the or query. I can delete the comment altogether, but thought it would be helpful for people perusing "or" query SO questions.
Express yourself with an O'Reilly book-cover.
real or virtual
interesting taxonomy; useful for communicating about a concerted effort towards a more document-oriented correction to the modern Web?
“But how can I automate updates to my site’s look and feel?!”
Perversely, the author starts off getting this part wrong!
The correct answer here is to adopt the same mindset used for print, which is to say, "just don't worry about it; the value of doing so is oversold". If a print org changed their layout sometime between 1995 and 2005, did they issue a recall for all extant copies and then run around trying to replace them with ones consistent with the new "visual refresh"? If an error is noticed in print, it's handled by correcting it and issuing another edition.
As Tschichold says of the form of the book (in The Form of the Book):
The work of a book designer differs essentially from that of a graphic artist. While the latter is constantly searching for new means of expression, driven at the very least by his desire for a "personal style", a book designer has to be the loyal and tactful servant of the written word. It is his job to create a manner of presentation whose form neither overshadows nor patronizes the content [... whereas] work of the graphic artist must correspond to the needs of the day
The fact that people publishing to the web regularly do otherwise—and are expected to do otherwise—is a social problem that has nothing to do with the Web standards themselves. In fact, it has been widely lamented for a long time that with the figurative death of HTML frames, you can no longer update something in one place and have it spread to the entire experience using plain ol' HTML without resorting to a templating engine. It's only recently (with Web Components, etc.) that this has begun to change. (You can update the style and achieve consistency on a static site without the use of a static site generator—where every asset can be handcrafted, without a templating engine.) But it shouldn't need to change; the fixity is a strength.
As Tschichold goes on to say of the "perfect" design of the book, "methods and rules upon which it is impossible to improve have been developed over centuries". Creators publishing on the web would do well to observe, understand, and work similarly.
it is impossible to build a new web browser
Perhaps it's not possible. (Probably not, even.) It would be very much possible to build a web browser capable of handling this page, on the other hand, and to do so in a way that produces an appreciable result in 10 minutes of hacking around with the lowliest of programming facilities: text editor macros—that is, if only it had actually been published as a webpage. Is it possible to do the same for if not just this PDF but others, too? No.
It's great to enhance the Internet Archive, but you can bet I'm keeping my local copy too.
Like the parent comment by derefr, my actual, non-hypothetical practice is saving to the Wayback Machine. Right now I'm probably saving things at a rate of half a dozen a day. For those who are paranoid and/or need offline availability, there's Zotero https://www.zotero.org. Zotero uses Gildas's SingleFile for taking snapshots of web pages, not PDF. As it turns out, Zotero is pretty useful for stowing and tracking any PDFs that you need to file away, too, for documents that are originally produced in that format. But there's no need to (clumsily) shoehorn webpages into that paradigm.
If you do the print-to-PDF workflow outlined earlier in the thread, you'll realize it doesn't scale well, requiring too much manual intervention and discipline (including taking care to make sure it's filed correctly; hopefully you remember the ad hoc system you thought up last time you saved something), that it's destructive, and that it ultimately gives you an opaque blob. SingleFile-powered Zotero mostly solves all of this, and it does it in a way that's accessible in one or two clicks, depending on your setup. If you ever actually need a PDF, you can of course go back to your saved copy and produce a PDF on-demand, but it doesn't follow that you should archive the original source material in that format.
My only reservation is that there is no inverse to the SingleFile mangling function, AFAIK. For archival reasons, it would be nice to be able to perfectly reconstruct the original, pre-mangled resources, perhaps by storing some metadata in the file that details the exact transformations that are applied.
web application for business
By making the storage and organization of information everyone’s responsibility and no one’s, the internet and web could grow, unprecedentedly expanding access, while making any and all of it fragile rather than robust in many instances in which we depend on it.
You can use LibreOffice's Draw
Nevermind LibreOffice Draw, you can use LibreOffice Writer to author the actual content. That this is never seriously pushed as an option (even, to my knowledge, by the LibreOffice folks themselves) is an indictment of the computing industry.
Having said that, I guess there is some need to curate a set of templates for small and medium size businesses who want their stuff to "pop".
I’m not confident I’ll be able to keep a server running to serve up my notes, so I bundled them up into an archive of pregenerated HTML, which anyone who has a copy can unpack and read, without requiring any online resources.
A great overview of some of the various definitions of small web and what it might entail.
Another interpretation of the “Small Web” concept is that it refers to the use of alternative protocols to the dominant HTTP(S), lightweight ones like the older Gopher and newer Gemini. For example, the blog post Introduction to Gemini describes these collectively as “the Small Internet”.
Maybe the idea of a "personal internet" is what we're all really looking for? Something with some humanity? Something that's fun? Something that has some serendipity?
I’m quite interested in concepts of the “Small Web” and adjacent topics, but it is definitely true that “small web” itself is a vague term that different people use to talk about different kinds of projects. What unites all these different concepts is the kind of web they define themselves against; that kind of bloated, corporate, algorithm-ruled and ad-ridden mess that constitutes the majority of highly-trafficked websites these days.
It would definitely be better if there were also a proactive, positive definition of what the small web were for rather than against.
It's better to have definitions in both directions to better delineate what's included and what's excluded.
Some of the best customers of such a service will be academics.
Indeed. Web literacy among the masses is pitifully low. Browsermakers are certainly to blame for being poor stewards. Hot Valley startups are responsible as well. (See https://quoteinvestigator.com/2017/11/30/salary/.)
But here's the twist. That edit window is wired to your personal cloud. That's where your words land. Then you syndicate your words back to the site you're posting to.
This is more or less how linked data notifications work. (And Solid, of course, goes beyond that.)
If they did I think there would actually be some quality of discussion, and it might be useful
I used to think this. (That isn't to say I've changed my mind. I'm just not convinced one way or the other.)
Another foreseeable outcome, relative to the time when the friend here was making the comment, is that it would lead to people being nastier in real life. Whether that's true or not (and I think that it might be), Twitter has turned out to be a cesspool, and it has shown us that people are willing to engage in all sorts of nastiness under their real name.
Award Winning SEO Agency London
Award Winning SEO Agency London! As a dedicated London SEO agency, we provide proven SEO services for a whole range of clients while performing white hat techniques. #1 page ranking experts in local SEO. Get your free audit today!
Cambridge SEO Nerds
SEO Services Cambridge Dedicated SEO agency, Nautilus Marketing provides proven SEO services while performing white hat techniques 1 page ranking experts in local SEO Get your SEO audit today
Mentioned by Heather Staines
Some conventions may be emerging in a new batch of personal knowledge management tools, or amenable to them; for the duration of this document, we'll refer to these tools as [[personal knowledge management]] tools, [[roam like]] or (preferred as of the time of writing) [[wiki like]].
It would be incredibly useful to have a list of these [[Roam Research like]] tools so that they can be documented as to what level of input they can/could take and remain compatible from text, to text+[[wiki links]], to the various flavors of markdown up to full HTML perhaps.
I know a handful are documented at indieweb.org/commonplace_book
The salary for each profession varies from similar factors. What determines the salary of software developers? After reading this article, I concluded that the greatest role is played by the country in which the developer works. For example, there are countries where developer salaries are much lower, although skills are not inferior. Skills, background and many other points also affect. Enjoy reading!
The ecosystem behind React gave you too many choices of this sort, which fragmented the tech stack and caused the infamous “Javascript fatigue”.
To me, the reason React ruined web development is because it homogenized & centralized the practice, in an abstraction that is decoupled & non-interoperable with other techniques & styles.
The author is arguing that React didn't centralize enough, but to me, it sucked all the oxygen out of the diverse interesting place that was web development. That it didn't try to solve all problems in the stack is, if anything, a most relief. It succeeded because it didn't bundle in a data-layer. It succeeded because it didn't bundle in state. It succeeded because it didn't bundle in routing. Each of these areas have evolved independently & seen great strides across the last half decade. That's a huge win, that's why React is so strong: because it didn't try to form opinions.
Alas React itself implies a strong opinion, has a big abstraction that de-empowers & de-inter-operates with the DOM, that keeps it from working in concert with any other technology. It has enormous diversity, but only under it's own umbrella. It has crushed a much livelier sporting aspect of web development.
I'm so tired of weenies complaining about fragmentation. Get lost and fuck off. This medium is flexible & diverse & interesting. Stop applying your industrial software want, your software authoritarianism, "why can't everyone just do it my way/the right way" horse shit. Such a shitty attitude, from people selling FUD & clutching at the idea that everyone's gonna be happy & productive if we can just make the right framework. How uncreative & droll.
If you find a suitable archive URL, then you can add it to the citation. If the citation uses one of the common templates (e.g. {{cite web}}, {{cite news}}, {{Citation}}), then you can edit as follows: Leave the |url= unchanged, pointing to the source URL. Add |archive-url=, pointing to the archive URL. Add |archive-date=, specifying the date when the archived copy was saved. YYYY-MM-DD format is usually easiest but any format can be used. Add or change |url-status=. Use |url-status=dead if the old URL does not work. Use |url-status=unfit or |url-status=usurped if the old URL has been usurped for the purposes of spam, advertising, or is otherwise unsuitable. Use |url-status=live if |url= still works and still gives the correct information, but you want to preemptively add an |archive-url=. Leave the |access-date= unchanged, referring to the date when a previous editor last accessed the |url=. Some editors believe |access-date= should be removed once a working |archive-url= is established since the |url= is no longer available, maintaining an |access-date= is redundant clutter.
La forme de cet écrit est multisupport : à l’écran et imprimée, mettant en action les outils développés par les designers que j’étudie dans cette réflexion. Et, le propos sur l’édition à plusieurs est actionné par les commentaires de chaque lecteur disponibles sur la version numérique.
Les commentaires et échanges ne sont donc visibles que sur la version numérique ? Puisqu'on parle de web to print, ce serait intéressant que l'écrit augmenté soit aussi présent dans la forme imprimée. En terme de mise en page, cela pourrait donner lieu à une forme intéressante des échanges : en fin d'ouvrage ? ou entrecoupant les différents chapitres ? ou encore directement en face de l'écrit d'origine pour confronter deux textes ? Chaque nouvelle impression serait comme une réédition, une édition qui s'écrirait sans cesse dans le temps.
<picture> <source type="image/avif" media="(-webkit-min-device-pixel-ratio: 1.5)" srcset="2x-800.avif 800w, 2x-1200.avif 1200w, 2x-1598.avif 1598w" sizes=" (min-width: 1066px) 743px, (min-width: 800px) calc(75vw - 57px), 100vw " /> <source type="image/webp" media="(-webkit-min-device-pixel-ratio: 1.5)" srcset="2x-800.webp 800w, 2x-1200.webp 1200w, 2x-1598.webp 1598w" sizes=" (min-width: 1066px) 743px, (min-width: 800px) calc(75vw - 57px), 100vw " /> <source media="(-webkit-min-device-pixel-ratio: 1.5)" srcset="2x-800.jpg 800w, 2x-1200.jpg 1200w, 2x-1598.jpg 1598w" sizes=" (min-width: 1066px) 743px, (min-width: 800px) calc(75vw - 57px), 100vw " /> <source type="image/avif" srcset="1x-743.avif" /> <source type="image/webp" srcset="1x-743.webp" /> <img src="1x-743.jpg" width="743" height="477" alt="A red panda" /> </picture>
just shy of 1k. ;)
network requests are a big deal, and having to deal with this kind of thing is one of the prices of switching away from server-side rendering to a distributed system
it’s also the case that the web was first built in the 90s to share complicated academic work and make it editable by its readers
This guy gets it.
I tried all the different static site generators, and I was annoyed with how everything was really complicated. I also came to the realization that I was never going to need a content management system with the amount of blogging I was doing, so I should stop overanalyzing the problem and just do the minimum thing that leads to more writing.
Great way to put it. One thing that I keep trying to hammer is that the "minimum thing" here looks more like "open up a word processor, use the default settings, focus on capturing the content—i.e. writing things out just as you would if you were dumping these thoughts into a plain text file or keeping it to, say, the subset of Markdown that allows for paragraph breaks, headings, and maybe ordered and unordered lists—and then use your word processor's export-to-HTML support to recast it into the format that lets use their browser to read it, and then FTP/scp/rsync that to a server somewhere".
This sounds like I'm being hyperbolic, and I kind of am, but I'm also kind of not. The process described is still more reasonable than the craziness that people (HN- and GitHub-type people) end up leaping into when they think of blogging on a personal website. Think about that. Literally uploading Microsoft Word-generated posts to a server* is better than the purpose-built workflows that people are otherwise coming up with (and pushing way too hard).
(*Although, just please, if you are going to do this, then do at least export to HTML and don't dump them online as PDFs, a la berkshirehathaway.com.)
For dynamic routes, such as our src/routes/blog/[slug].svelte example, that's not enough. In order to render the blog post, we need to fetch the data for it, and we can't do that until we know what slug is. In the worst case, that could cause lag as the browser waits for the data to come back from the server. We can mitigate that by prefetching the data. Adding a sveltekit:prefetch attribute to a link... <a sveltekit:prefetch href="blog/what-is-sveltekit">What is SvelteKit?</a> ...will cause SvelteKit to run the page's load function as soon as the user hovers over the link (on a desktop) or touches it (on mobile), rather than waiting for the click event to trigger navigation. Typically, this buys us an extra couple of hundred milliseconds, which is the difference between a user interface that feels laggy, and one that feels snappy.
makes your app inaccessible to users if JavaScript fails or is disabled (which happens more often than you probably think).
Whether or not digital gardens should follow any standards is an interesting question.
What features/functionality should a digital garden have? Is there a canonical list yet?
I wish more supported Webmention to enable the Memex dream...
The conversational feed design of email inboxes, group chats, and InstaTwitBook is fleeting – they're only concerned with self-assertive immediate thoughts that rush by us in a few moments.
The streamification of the web had already taken hold enough by this point. Anil Dash had an essay in 2012 entitled Stop Publishing Web Pages which underlined this point.
Project management alternatives
many people have attached sensors
This differs from LDN, where the the annotation service is squarely under the control of the document author. This is also using sensor attachment in a different sense that the way it first appears above. The application is more akin to RSS. With RSS, the links exist in some other "document" (or something like it; generall can be modeled as OPML, even if it's really, say, an sqlite store).
So she writes an explanatory note for Jack, links the note to the Parallel Compiling report, and then links the note to Jack's mailbox: in this open hypertext system, a mailbox is simply a publicly readable document to which the owner has attached a sensor.
Okay, so this is back to looking like LDN, except the (novel?) idea that after sending the annotation to the annotation service responsible for annotations to the report, her final annotation gets sent to that that annotation service corresponding to a different document—Jack's mailbox. Interesting!
(Maybe this is explicitly laid out as a possibility in one of the several pieces associated with LDN and I just never noticed?)
a hypermedia server might use sensors to alert users to the arrival of new material: if a sensor were attached to a document, running a new link to the document would set off the sensor
Linked data notifications?
(I like the "sensor" imagery.)
This looks cool! I can think of some interesting applications, but the example here is pretty slick.
Charlotte Jee recently wrote a lovely fictional intro to a piece on a “feminist Internet” that crystallized something I can’t quite believe I never saw before; if girls, women and non-binary people really got to choose where they spent their time online, we would never choose to be corralled into the hostile, dangerous spaces that endanger us and make us feel so, so bad. It’s obvious when you think about it. The current platforms are perfectly designed for misogyny and drive literally countless women from public life, or dissuade them from entering it. Online abuse, doxing, blue-tick dogpiling, pro-stalking and rape-enabling ‘features’ (like Strava broadcasting runners’ names and routes, or Slack’s recent direct-messaging fiasco) only happen because we are herded into a quasi-public sphere where we don’t make the rules and have literally nowhere else to go.
A strong list of toxic behaviors that are meant to keep people from having a voice in the online commons. We definitely need to design these features out of our social software.
A former FB executive and long-standing friend of Zuckerberg emailed him in 2012 (page 31) to say “The number one threat to Facebook is not another scaled social network, it is the fracturing of information / death by a thousand small vertical apps which are loosely integrated together.”
And this is almost exactly what the IndieWeb is.
Draft notes, E-mail, plans, source code, to-do lists, what have you
The personal nature of this information means that users need control of their information. Tim Berners-Lee's Solid (Social Linked Data) project) looks like it could do some of this stuff.
editor-browser tool sets
This hasn't happened yet, and is unlikely to happen anytime soon. We seem to be moving away from a read/write web, with authors only being able to edit content they've created on domains that they control. The closest I've seen to this is the Beaker Browser.
It remains a blank page –a means of getting human clusters of infinite variety on the same page.
the Web as a way to have a conversation
The Web is not, first, what Tim Berners-Lee thought he was designing in the early ’90s: a collaborative medium for researchers working together at a distance. That part, for a variety of technical and legal reasons, just didn’t work. Neither is the Web a superhighway of anything, if the highway motif makes you think of concrete, steel, and fixed routes to anywhere. The Web is not, and must never be, the avenue of a monoculture. It is not the outline of a universal brain that will reduce human beings to mere neurons in a Global Mind. It is not a monument to the “Me Decade.” That is, it’s not all about expressive blogging. Or rather: it’s equally about listening and learning. It is about them as much as it’s about us. It is not, he insists, a structure. It is not an active agent
The Web is not ...
A historical indicator of the reason why early web buttons were 88x31 as the result of Netscape Now buttons.
why do we have an <img> element? Why not an <icon> element? Or an <include> element? Why not a hyperlink with an include attribute, or some combination of rel values? Why an <img> element? Quite simply, because Marc Andreessen shipped one, and shipping code wins.That’s not to say that all shipping code wins; after all, Andrew and Intermedia and HyTime shipped code too. Code is necessary but not sufficient for success. And I certainly don’t mean to say that shipping code before a standard will produce the best solution.
Shipping code is necessary, but not sufficient for success.
a redesign lately that adds a bunch of crud obscuring the content
Garimella, K., Smith, T., Weiss, R., & West, R. (2021). Political Polarization in Online News Consumption. ArXiv:2104.06481 [Cs]. http://arxiv.org/abs/2104.06481
This is the other kind of novelty-seeking web developer, one who seeks to build on the history and nature of the web instead of trying to transform it.
What I am attempting to do is to highlight a div with a certain id, when It has been referred to by an anchor on another page IE: User clicks link href="qw.html#test", when the page is loaded, then the div with the id="test" is highlighted so that the user can see it clearly.
You need to use the :target pseudo-class: :target { background-color: #ffa; }
A common practice in email marketing is to use images for everything in the email: graphics, illustrations, copy, links, and buttons. Although this can be efficient (slice, dice, and send it on its way), it’s another huge problem for subscribers relying on screen readers. The typical image-based email has a lot of information that can’t be parsed by a machine. What’s more is that a lot of email clients disable images by default, too.
However, since we’re using tables purely for structural purposes, we need screen readers to ignore those tables. This is where ARIA roles can help us out. By applying the role="presentation" attribute to a table, we can instruct the screen reader to skip over those elements and move straight into the content.
And what’s more, a growing number of email readers are even voluntarily turning off images in their emails to reduce load time and improve email speed. Google recently revealed that 43% of Gmail users actually don’t read emails with background images on.
Email tools/clients are inconsistent in how they render HTML and CSS. A designed email might look great in Gmail, broken in Outlook, and unreadable in Apple Mail. Half of all emails are opened on mobile devices (according to one study). Email looks good in different clients? Great, now make it work on a 4" screen just as well as on a desktop.
My assertion is based on the observation that a great deal of learning does take place in connective environments on the world wide web, that these have scaled to large numbers, and that often they do not require any institutional or instructional support.
I wrote some thoughts on this here: Without anyone's permission: The open web and online learning.
Over the years, the machinery of targeted advertising has frequently been used for exploitation, discrimination, and harm. The ability to target people based on ethnicity, religion, gender, age, or ability allows discriminatory ads for jobs, housing, and credit. Targeting based on credit history—or characteristics systematically associated with it— enables predatory ads for high-interest loans. Targeting based on demographics, location, and political affiliation helps purveyors of politically motivated disinformation and voter suppression. All kinds of behavioral targeting increase the risk of convincing scams.
a succinct summary of the harms of tracking and adtech
The power to target is the power to discriminate. By definition, targeted ads allow advertisers to reach some kinds of people while excluding others. A targeting system may be used to decide who gets to see job postings or loan offers just as easily as it is to advertise shoes.
You should have a right to present different aspects of your identity in different contexts. If you visit a site for medical information, you might trust it with information about your health, but there’s no reason it needs to know what your politics are. Likewise, if you visit a retail website, it shouldn’t need to know whether you’ve recently read up on treatment for depression. FLoC erodes this separation of contexts, and instead presents the same behavioral summary to everyone you interact with.
Documents should offer the same granularity.
That neither content creators nor browser vendors are particularly concerned with the production and consumption of documents, as such, is precisely the issue. This is evident in the banner that the majority of the work has occurred under over the last 10+ years: they're the Web Hypertext Applications Technology Working Group.
No one, not even the most well-intentioned (such as the folks at Automattic who are responsible for the blogging software that made Christina's post here possible), see documents when they think of the Web. No, everything is an app—take this page, for example; even the "pages" that WordPress produces are facets of an application. Granted, it's an application meant for reading the written word (and meant for occasionally writing it), but make no mistake, it's an application first, and a "document" only by happenstance (i.e. the absence of any realistic alternative to HTML & co for application delivery).
via Jim Groom
Instructions for writting a new wildcard adapter for some site.
Play with Docker
to re-phrase a famous line from Zach Davis, “Behind every EDUPUNK is a frazzled web developer.”
The best tool is no tool, the best build step is no build step, the best update is no update. HTML gives us all that, and more.
Truth!
.mainContent {  -webkit-user-select: none; -moz-user-select: none; -ms-user-select: none;  user-select: none; }
Could this maybe be used when publishing content on third party sites to ping your own website?
I LOVE the hover effects for the book covers on this site which is also a great example of someone collecting highlights/annotations of the books they read and hosting them in public on their personal website.
Melanie has written about the CSS part of the hover effect here: https://melanie-richards.com/blog/highlights-minisite/ and like all awesome things, she's got the site open at https://github.com/melanierichards/highlights. I may have to do some serious digging for figuring out how she's creating the .svg images for the covers though.
CSS-generated content is not included in the DOM. Because of this, it will not be represented in the accessibility tree and certain assistive technology/browser combinations will not announce it. If the content conveys information that is critical to understanding the page's purpose, it is better to include it in the main document.
This year’s Slow Art Day — April 10 — comes at a time when museums find themselves in vastly different circumstances.
Idea: Implement a slow web week for the IndieWeb, perhaps to coincide with the summit at the end of the week.
People eschew reading material from social media and only consume from websites and personal blogs for a week. The tough part is how to implement actually doing this. Many people would have a tough time finding interesting reading material in a short time. What are good discovery endpoints for that? WordPress.com's reader? Perhaps support from feed reader community?
Hérigone's only important work is the six volume Cursus mathematicus, nova, brevi, et clara methodo demonstratus Ⓣ<span class="non-italic">(</span>Course on mathematics : new, short, and with clear methods shown<span class="non-italic">)</span> or, to give it its French title, Cours mathematique, demonstre d'une nouvelle, briefve, et claire methode which appeared between 1634 and 1642.
There is a clever little bit of UI on this page in which there appears a red letter T in a circle after the Latin title. If one clicks it ,there's a pop up of the translation of the title into English.
My favorite part of this entire plan has to be the part where I use Github Issues as a blog. Kind of. For every new feature (or set of features) I want to add to the site—no matter how small, like adding a Favicon, for example—I will open a new issue and create a corresponding branch where the work on that feature will happen. I will basically produce a(n) infrequent stream of short “blog posts” in the form of Github issues. The live code for each issue/feature will live in the issue’s corresponding branch. As someone who tends to do multiple things at once, this will take a lot of organization and discipline, and that’s the challenging part for me.
This is a fascinating and very illustrative use of GitHub for web development. I mostly like that she's pointing out her use case.
I am going to rebuild this Web site in public.
The Social Web.
The "Social Web" was a thing by this point
An interesting bit of web history and fascinating list of names here...
There is no shopkeeper for the World Wide Web.
@ajlkn has several related projects including this one:
Might be an interesting experiment to make one or more of them IndieWeb friendly and create a set up to dovetail one or more of them in with the GitHub pages set up.
User stories are a great way of designing features, but when you are designing community features on the web it is also useful to have user stories that start “I am an absolute arsehole and I want to…”
Solid advice.
<small><cite class='h-cite via'>ᔥ <span class='p-author h-card'>James Van Dyne</span> in James Van Dyne on Twitter: "VERY fun hack: using lazy loading turbo-frames as a queue in dom. Each row needs to be imported. Frame source is api (returns html) and loads when visible. Scroll the page and one-by-one it imports your images. ZERO JS. #IndieWeb https://t.co/LOk0tq08tO https://t.co/lJ2hh1tDf3" / Twitter (<time class='dt-published'>03/29/2021 15:45:00</time>)</cite></small>
Silence Here’s another, more subtle, point about the grace of email and newsletters: Creation and consumption don’t happen in the same space. When I go to send a missive in Campaign Monitor the world of my laptop screen is as silent as a midnight Tokyo suburb.9 I think we’ve inured ourselves to the (false) truth that in order to post something, in order to contribute something to the stream, we must look at the stream itself, “Bird Box”-esque, and woe be the person in a productive creative jag, wanting to publish, who can resist those hot political tweets.
This rings very true to me and is a definite benefit of composing things within my own domain rather than too quickly within a social silo's interface.
Who owns and controls it?
This is worth discussion. Specifically the ownership part and it may be surprising to uncover how little control there has been and how that is changing in 2021 as ISPs and hosting companies refuse or welcome radical platforms and groups, https://www.npr.org/2021/02/15/968116346/after-weeks-of-being-off-line-parler-finds-a-new-web-host
And it’s tempting for engineers to think decentralising the Web can be achieved with technology. But really, it’s people who will make it happen. Rather than staying put in our little filter bubbles, we can burst out of them — and be radically sociable, delinquent, and make a scene.
off label uses of technology are important
I'm reminded of how Kicks Condor has appreciated my "people work" in the past.
I really like this and want to figure out way to do it on my own website. It could be fun to tuck it in with the weather and location data I'm already collecting.
Compare ALL markdown implementations for arbitrary syntax!
I was pretty annoyed with myself for having fallen for the trap of not documenting my own systems, but not sure how I could have remembered all of the Hugo-isms
I've explained such a system, and promised Andy Chu an example that I've yet to be able to complete, but it comes down to this:
A website is fundamentally a document repository. One of the first documents that you should store in that repository is one which explains, in detail, the procedures for provisioning the host powering the site and how content gets published. (Even better if it's so detailed that the procedures exhibit a degree of rigor such that a machine can carry them out, rather than requiring manual labor by a human.)
<small><cite class='h-cite via'>ᔥ <span class='p-author h-card'>Kevin Marks</span> in Kevin Marks on Twitter: "@doctorow The podle app by @AdaRoseCannon could be a good starting point https://t.co/q9Y8DEVbfG" / Twitter (<time class='dt-published'>03/15/2021 14:41:41</time>)</cite></small>
Blayac, Thierry, Dimitri Dubois, Sebastien Duchêne, Phu Nguyen-Van, Bruno Ventelou, and Marc Willinger. ‘Population Preferences for Inclusive COVID-19 Policy Responses’. The Lancet Public Health 6, no. 1 (1 January 2021): e9. https://doi.org/10.1016/S2468-2667(20)30285-1.
Deevybee. (2020, December 6). BishopBlog: Faux peer-reviewed journals: a threat to research integrity. BishopBlog. http://deevybee.blogspot.com/2020/12/faux-peer-reviewed-journals-threat-to.html
In terms of defining the “open” in open web annotation, I tend to take a standards approach: the Hypothes.is tool is built upon, and our organization advocates for, open standards in web annotation.
This explanation also highlights an additional idea of open itself. I have heard many in the W3C space criticize the open standard of web annotation arrived at because of the ultimate monoculture of the space. Most of the participants of the process were all related to Hypothes.is in some way and the result was a single product that implemented the standard. To my knowledge no other companies, groups, or individual programmers have separately implemented the standard.
In this sense, while the "standard" is openly defined, it isn't as open as other standards which were mote slowly evolved and implemented gradually and more broadly by various programming languages and disparate groups.
The valueAsNumber IDL attribute represents the value of the element, interpreted as a number. On getting, if the valueAsNumber attribute does not apply, as defined for the input element's type attribute's current state, then return a Not-a-Number (NaN) value.
Screen readers for the blind can help them fill out a form more easily if the logical sections are broken into fieldsets with one legend for each one. A blind user can hear the legend text and decide, "oh, I can skip this section," just as a sighted user might do by reading it.
Fits the ideal behind HTML HTML stands for "HyperText Markup Language"; its purpose is to mark up, or label, your content. The more accurately you mark it up, the better. New elements are being introduced in HTML5 to more accurately label common web page parts, such as headers and footers.
The source for all versions is available on GitHub.
The TreeWalker API gives you only the #text Nodes, and then you do what you want with them.
first sighting: TreeWalker 
You could also use the NodeIterator API, but TreeWalker is faster
Open source code library for building innovative e-learning that is accessible, usable, interoperable, mobile-friendly and multilingual. Based on the Web Experience Toolkit (WET) and bootstrap. This collaborative open source project is led by the Canada School of Public Service, Government of Canada.
20 communication tools (2020)
Accepting PaymentsTracking RevenueCustomer SupportCollaboration and Internal CommunicationMarketing and SalesSEO and Content MarketingAnalyzing Web TrafficServer and HostingBilling and AccountingDesignData VisualizationPassword ManagementDigital Signatures
Nice collection of programs or SaaS for:
Nice collection of communication & producivity programs or SaaS.
Service workers are limited though. A site can opt to perform whatever substitutions it likes, but it can only do that for its own requests.
for requests both to it's origin, and also coming from it's origin. this latter restriction seems unnecessary, but alas, there has been little traction trying to get Foreign Fetch - enabling service workers to be accessible across origins - back into the spec. Foreign Fetch would greatly help the offline web. https://github.com/w3c/ServiceWorker/issues/1188
Simone, Costanza De, Antonella Battisti, and Azzurra Ruggeri. “Differential Impact of Web Habits and Active Navigation on Adolescents’ Online Learning.” PsyArXiv, March 1, 2021. https://doi.org/10.31234/osf.io/hsvc4.
try { const value = await localforage.getItem('somekey'); // This code runs once the value has been loaded // from the offline store. console.log(value); } catch (err) { // This code runs if there were any errors. console.log(err); }
This looks like the best approach for me. async/await
