Hypertext systems should take about 1/4 second to move from one place to another. If the delay is longer, people may be distracted; if the delay is much longer, people will stop using the system. If the delay is much shorter, people may not realize that the display has changed.
It is funny how thoughts about speed and user experience were already there before the 2000's.
Issue: Links on the web are often quite slow
One solution is to abandon hypertext links. [...] Have a one-page view.
Another strategy is to exchange one large delay for many small ones. We can sometimes arrange a Web site to to bundle large parts of the data in a package that is pre-loaded at the entrance. Within the site, link response is quick because time-consuming sound, graphic, video, and applets have been pre-loaded onto the user's computer.
A better solution, for sophisticated hypertexts that must provide crisp performance, may be to use the Web as a way to provide access to, and information about, hypertexts that can be downloaded (or purchased) as a unit and then performed on the user's machine.
Thoughts of the web and hyperlinks
eine neue Literaturgattung, bei der sich die tradierten Strukturen von Erzählungen in offene, für den Leser unerwartete Strukturen auflösen. Vielfältige Rezeptionswege werden durch die Möglichkeit, im Text zu springen, möglich. Der Leser wird dabei durch seine Auswahlentscheidungen zum Mitproduzenten des Textes.
(In context of web gardening)
- Many hypertexts do not require elaborate navigational apparatus.
- Rigid hypertext structure is costly.
- The shortest path is not always the best.
- Large hypertexts and Web sites must often contain both parks and gardens.
- Use punctuation sparingly; unwanted interruptions are tiresome and intrusive.
- The boundaries of parks should be especially clear, lest readers see them as mere wilderness.
- Rigid structure makes a large hypertext seem smaller. Complex and intricate structure makes a small hypertext seem larger, inviting deeper and more thoughtful exploration.
Highways are judged by efficiency: distance, cost, safety, and time. Garden paths play a different role; they lead us through the best routes, not the shortest. They may bend to pace our journey, curving here to reveal a view, twisting there to lead us through a shady grove or a sunny clearing.
Rigid hypertext is streetscape and corporate office: simple, orderly, unsurprising. We may find the scale impressive, we admire the richness of materials, but we soon tire of the repetitive view. We enter to get something we need: once our task is done we are unlikely to linger. We know what to expect, and we rarely receive anything more.
Make an OSS version of it for the web: why not building on the web for the web?
At times, wilderness is exactly what readers want: a rich collection of resources and links. At times, rigid formality suits readers perfectly, providing precisely the information they want, no more and no less. Indeed, individual hypertexts and Web sites may contain sections that tend toward each extreme.
Often, however, designers should strive for the comfort, interest, and habitability of parks and gardens: places that invite visitors to remain, and that are designed to engage and delight them, to invite them to linger, to explore, and to reflect.
A website about web, links and hypertext... well it is a garden when someone can lost itself a bit.
Baseline is a new term that defines a feature broad adoption. There are two stages:
- The new feature is available in all last versions of the browsers
- The new feature is widely available after 30 months after the first stage
We can then speak of baseline 2023 that groups all features usable in the considered browsers.
Limitations:
- the browsers considered are Safari, Firefox, Chrome and Edge. The rest is unknown even if they are listed on caniuse.com
- it does not take screen readers and accessibility tools in consideration as part of "availability"
I like the model: Subject - Predicate - Object
Such as: Xerxes - Parent - Brook.
It can be modeled as such:
parent(xerces, brooke).
parent(brooke, damocles).
Note of Tim Berbers-Lee.
Put a frame around "engineering" and " ownership"
The overwhelming motivation behind it seemed to be “I made something, here it is”. Sharing things for the sake of showing them to the world. Somebody had created something, then put it online so you could see it. Visit their website (wait for the dial-up to finish), and it’s yours.
Large companies find HTML & CSS frustrating “at scale” because the web is a fundamentally anti-capitalist mashup art experiment, designed to give consumers all the power. — Mia, with valuable secrets 🤫 (@TerribleMia) November 24, 2019
You can stand out of the crowd by simply treating the web platform as what it is: a way to deliver content to people.
The best growth hack is still to build something people enjoy, and then attach no strings to it. You’d be surprised how far that can get you.
Metaphosr of the web as Dark Forest, cozy web, dark web, corporate web, etc...
And there are The Towns, the IndiWeb or the small web. There is the fun !
Let's create a holiday card generator by learning how to get access to a user's webcam and compose a screenshot.
Because the federation is disturbing for casual users, it seems normal to
remind ourselves of what social media used to be: a way to connect around shared interests, talk to friends, and discover new content. No grifts, no viral fame, no drama.
The barrier to be free on the web is highly correlated to the level of expertise.
You could loosely map some of them by how easy it is to get started if you have no technical knowledge. [...] The more independence a technology gives you, the higher its barrier for adoption.
Owning, control and independance on the web should be just as easy as signing up for a cellphone plan.
An acronym standing for "Publish (on your) Own Site, Syndicate Elsewhere".
It seems great :D
Great explanation of the rel attributes that provide:
- information to the resource linked
- behaviors while navigating