Ensure a seamless, intuitive, and controlled experience when applying coupon codes in the cart drawer by:Clearly displaying applied coupons.Preventing multiple or duplicate coupon entries.Providing users with the option to remove applied coupons.Maintaining synchronization with backend/cart state.
Learn effective ways to optimize your Shopify cart drawer for faster checkout, better user experience, and increased conversion rates. Discover practical UI/UX tips.
This doesn't allow easy creation of bookmarklets like:
javascript:(`foo <b>bar</b>`)
We need explicit detection/support for these.
So if the network roundtrip time to your server is even 100ms, and Sliding Sync is operating infinitely quickly, you’re still going to end up showing a placeholders for a few frames
What stops loading context around the window?
Better off, start from windows position and sync everytihng from that priority.
I.e., prioritize what gets replicated by how user's acting.
Usage of an IS is not required in order for a client application to be part of the Matrix ecosystem. However, without one clients will not be able to look up user IDs using 3PIDs
Better: linke from 3rd party to Matrix.
E.g., by adding on Twitter link to Matrix ID.
type values MUST be uniquely globally namespaced following Java’s package naming conventions, e.g. com.example.myapp.event
We're in the Web. Better: URIs.
signing the message in the context of the graph for integrity
That's weird. User's not in chare of creating an event (as user-generated event is not a complete event in Matrix model, it lacks causal history).
Relying for creation of an event on a server means you need to be online in order to use apps.
Better: let user's device be enough, so user can create events offline, sync it later. Server is dumb - just relaying it to user's friends.
and shares data with the wider Matrix ecosystem by synchronising communication history with other homeservers and their clients
That's a con. There's no need to sync globe-wide, creating a giant ledger. You have a set of peers that you want to share your stuff with (friends), leave it at that.
Managing user accounts (registration, login, logout)
Better: always log in with a server, unless you choose to migrate.
Extensible user profile management (avatars, display names, etc)
Better: let peers have personal profiles of their friends.
Like you do with your contacts on phone. You know their id (phon number), you give it a name, assign a pic. It's up to you.
Extensible user management (inviting, joining, leaving, kicking, banning) mediated by a power-level based user privilege system
Additionally: community-based management, ban polls.
Alternative: per-user configuration of access. Let rooms be topics on which peers discuss. A friend can see what he's friends and foafs are saying.
The user should know precisely where their data is stored
And be able to store it locally, on trusted devices, replicated.
no single points of control over conversations or the network as a whole
Ideally support p2p. Servers/brokers are optional.
Sending and receiving extensible messages
Better: text messages & structured stuff (data).
across a global open network of federated servers and services
Better: across devices (p2p) and (optionally) their servers.
The same applies to reorganisation, whoseobject is merely to substitute superior for inferior control oradequate for inadequate control.
Substituting what Kaiser calls "superior for inferior control" which he defines as "reorganization" is a path which allows for the ideas behind the progressive enhancement of raw (fleeting) notes to commonplacing, to indexing, to a Luhmann-artig zettelkasten to work for a broad variety of people. Not everyone will require the same level of organization.
@chrisaldrich thank you for this detailed response about your use of Obsidian and organization for digital Zettelkasten. I am not sure if this is the current forum or discussion to ask this but I would be curious to see how you have integrated or coordinated your analog Zettelkasten and notetaking with what you describe here. I've followed your posts about the use of index cards for a long time. I'd love to see how you use the very different affordances of these environments together.
reply to u/wtagg at https://www.reddit.com/r/Zettelkasten/comments/16wgq4l/comment/k356507/?utm_source=reddit&utm_medium=web2x&context=3
Perhaps the easiest way to frame things is that I use my digital note taking as scaffolding in the learning and research process and the zettels in the digital space are the best filtered outcomes from some of that. If you compare my practice to that of Luhmann's one might consider most of my digital practice to be equivalent to his ZKI. Most of my analog practice is more highly focused and deliberate and is more closely limited to a small handful of topics related to my specific areas of research on memory, orality, intellectual history, Indigenous studies, education, anthropology, and mathematics (and is potentially more like Luhmann's ZK II). As a result, in hindsight—thanks for asking—, I'm simultaneously building my ZK I and ZK II instead of switching mid-career the way Luhmann did. But to be clear, a lot of my ZKII material filters (or digests, if you prefer that analogy) its way through the ZKI process along the way.
Title
In order to make it way easier to keep track of things in bookmarklet workspaces, there needs to be an option that adds an incrementing counter (timestamp?) to the bookmarklet title, so when dragging and dropping into your bookmarks library, you don't lose track of what's going on with a sea of bookmarklets all named the same thing.
Meta-level referencing (addresses on linksthemselves) enables knowledge workers to commentupon links and otherwise reference them.
By dropping or reducing or postponing the least importantparts, we can unblock ourselves and move forward even when timeis scarce.
When working on a project, to stave off potential procrastination on finishing, one should focus on the minimum viable version and finish that. They can then progressively enhance portions and add on addition pieces which may be beneficial or even nice to have.
Spending too much time on the things that sound nice or that one "might want to have" in the future will be the death of the thing.
link to: - you ain't gonna need it - bikeshedding for procrastination
questions: - Does the misinterpreted-effort hypothesis play a role in creating our procrastination and/or lead to decision fatigue?
output.addEventListener("click", ((event) => { if (event.target == output.querySelector("a.bookmarklet")) { alert("It's not an ordinary link; you need to bookmark it");
This should use the registered control service pattern (or something). It's too hard to override this behavior. For example, I could remix the page and remove it, but I should also be able to write a bookmarklet that achieves the same effect.
Prof. Akiko Iwasaki. (2021, September 23). Thankfully, we have not seen any evidence of antibody-dependent enhancement of infection or disease by any COVID vaccines to date. Vaccine are not making infections worse, and are very effective in preventing disease. [Tweet]. @VirusesImmunity. https://twitter.com/VirusesImmunity/status/1441074260534075392
makes your app inaccessible to users if JavaScript fails or is disabled (which happens more often than you probably think).
Build a baseline email experience for subscribers using email apps with limited support for HTML and CSS—such as Outlook and Gmail—before enhancing your email for other clients. Progressive enhancement should not create suboptimal experiences for other users.
An escalator is a great example of progressive enhancement and graceful degradation in real life. The late comedian Mitch Hedberg joked, “An escalator can never break: it can only become stairs. You should never see an Escalator Temporarily Out Of Order sign, just Escalator Temporarily Stairs. Sorry for the convenience.” Regardless of its environment, an escalator maintains its functionality.
The main focus of his talk was on progressive enhancement, which involves providing advanced functionality in environments where its supported. He also emphasized the importance of graceful degradation. Graceful degradation means that if your subscriber’s email client doesn’t support a certain functionality, you’ll still provide them with a pleasant experience.
there are bugs aplenty with ie's, the way to address them is by complimenting your otherwise sound html/css with fail safe code, rather than degenerating your sound html into hacky html for ie's sake.
And that just leaves the Word Outlooks (and their ever-aligning web based equivalents), and a few lesser used (for us) regional clients. Here, our div based layout reverts back to every story being on a new line. For #EmailWeekly, we’re ok with that.
Take inspiration from the mailto URI scheme here; ideally, we should be able to re-use almost exactly the same style of URL construction.
Since a lot of this is guaranteed to be seen as arcane magic, maybe this is an opportune place for the UI hooks for a conversational/palette-based UI? Maybe >> to set it off?
Yet sales figures for certain neuro-psychotropic drugs are considerably higher than the incidence of the illnesses for which they are indicated would lead one to expect. This apparent paradox applies above all to neuropsychotropic drugs that have neuro-enhancement properties. The most likely explanation is that neuro-enhancers are currently undergoing millions of self-trials, including in universities – albeit probably not in their laboratories. The ten top-selling psychotropic substances in the USA include anti-depressants, neuroleptics (antipsychotics), stimulants and drugs for treating dementia.
Therefore client side validation should always be treated as a progressive enhancement to the user experience; all forms should be usable even if client side validation is not present.
Überblick tut Geschichte und den wichtigsten Texten zu Progressive. Enhancement. Tolle Links!
There’s an important wrinkle when it comes to animating the menu away. When the user closes the menu, it will always disappear instantly, because the open attribute is, by default, removed immediately when the user clicks that summary element. In order to gracefully animate your menu out when it closes, we need some JavaScript. Here we can listen for clicks on the details element, and call preventDefault() on the click event, then use setTimeout() to determine exactly when that open attribute should be removed. This gives us time to trigger the closing animation with CSS. This click event listener will also fire when a keyboard user hits space or enter while the element is focused, which means no further listeners are needed for keyboard actions!
If you're creating an actual, informational web page, stick to frameless HTML, CSS and unobstrusive JavaScripts and keep in mind that the page should still be usable with scripting disabled.
JavaScript is more brittle than we care to admit. <a> elements function even if JavaScript breaks. Using anchors for your download means that a person can access what they need, even in suboptimal situations.
It is important to notice that if you are planning on making your application a PWA, you don’t have to rewrite all the logic.
The great thing about having our function in Promise form is that we don't actually need to "make it an async/await version" if we don't want to. When we call/execute the function, we can simply use the async/await keyword
Warning witnesses of the possibility of misinformation helps protect their memory accuracy. (2020, August 30). Tufts Now. https://now.tufts.edu/news-releases/warning-witnesses-possibility-misinformation-helps-protect-their-memory-accuracy
McKinley, L., McAnally, K., Moyers, S. A., & Hagger, M. S. (2020). Behavioral Health Theories, Equity, and Disparities in Global Health: A Basic Process Model. https://doi.org/10.31234/osf.io/nybv8
We do know that, just like iMessage, this new approach will failover to SMS/MMS if a user cannot receive the encrypted variant or if bandwidth is insufficient on either end.
A couple of years after WhatsApp, Apple jumped into the game with iMessage—its obvious drawback, that senders and recipients had to be using iPhones, was overcome by integration with the standard SMS platform on those phones. If a recipient was not on iMessage or was offline, the message would revert to SMS.
Adopting TypeScript is not a binary choice, you can start by annotating existing JavaScript with JSDoc, then switch a few files to be checked by TypeScript and over time prepare your codebase to convert completely.
First proposed as a somewhat less unwieldy catchall phrase to describe the delicate art of "separating document structure and contents from semantics, presentation, and behavior"
In progressive enhancement (PE) the strategy is deliberately reversed: a basic markup document is created, geared towards the lowest common denominator of browser software functionality, and then the designer adds in functionality or enhancements to the presentation and behavior of the page, using modern technologies such as Cascading Style Sheets, Scalable Vector Graphics (SVG), or JavaScript.
graceful degradation
Ritanserin, 5 mg, produced a substantially larger increase in SWS (51.4%) than either ketanserin, 20 mg (17.2%) or ketanserin, 40 mg (24.4%). Ritanserin has a significantly higher affinity than ketanserin for 5-HT2C receptor binding sites in the human brain and, based on estimates of per cent occupancy by the two compounds at brain 5-HT2A and 5-HT2C receptors, we conclude that SWS in humans is primarily regulated by 5-HT2C receptors.
This doesn't quite clarify the effect of 5HT2C antagonism in the absence of 5HT2A antagonism.
John Hockenberry
In the film John Hockenberry talks about how human enhancement changed through science and technology. Scientist invented robotic human parts connecting to a human’s nervous system that allows a person to move their body parts. Scientist have been concerning cosmetic surgery because the rate in males and females getting cosmetic surgery is increasing as technology is scientifically improving. I think this all relates to transhumanism because it is showing how science and technology is evolving overtime and the physical and mental limitations among humans. Disabled people are starting to live normal lives through scientifically advanced technology that will allow human hand to fix the nervous system.
Library (originally from Mozilla) for building components based on the W3C Web Components specs
A Web Component that can be used to pull fragments of HTML from the server and replace some placeholder content in the page once the fragment loads.
Framework for fast PE-navigation by updating just sections of a page that change during navigation, rather than reloading the whole page.
An experimental performance comparison of client and server-side templating on desktop and mobile, focusing on time to first paint and time to last paint metrics.
The server is written in Go. The client is the simplest possible client-side templating you can do (using a <template> element and a few DOM API calls), so no frameworks involved.
Some takeaways:
Server-rendered markup can be progressively enhanced as element definitions are registered and upgraded by the browser.
Question - How is the server-rendering done and in what language?
I came across this from a post reflecting on the last Chrome summit.
The splash pages which appear to be basic static content with little interactivity load a 1.5MB JS bundle (500KB gzipped). Flipping back and forwards between pages feels sluggish in Firefox. My initial hypothesis is that letting the client's side router tear down the DOM for the current route and build up the DOM for the new route might be slower than just relying on the browser's back/forwards cache as a set of boring static pages would do.
Hardly a scientific survey, but the answers on Twitter and offline have been surprisingly consistent: server-side React for graceful degradation, jQuery and possibly shared templates (e.g. Mustache) for progressive enhancement
Good article on progressive enhancement. Jake Archibald now works for Google, I'm not sure if that was the case at the time.
Transhumanists are at war with the bioconservatives. This just sounds like a William Gibson sci-fi novel. We live in amazing times. That said, global bans on technology and science never work; they just really mess things up. Regardless of what the bioconservatives think, there are cultures that will embrace these technologies (and already do). Historically, and possibly without exception, countries that ban or hobble new technologies eventually regret it because at least some of their neighbors will not follow suit. Further, by outright turning their back on the technology, they lose any voice they might have had in determining how it will be employed.
This picture
... could also mention the Ether way. Or offline. Or graceful degradation / progressive enhancement depending on connectivity.