https://whalebird.social/en/desktop/contents

Whalebird is a Mastodon, Pleroma, and Misskey client for desktop application

It's clear that gklitt is referring to the ability of extensions to augment the browser, but: * it's not clear that he has applied the same thought process to the extension itself (which is also software, after all) * the conception of in-browser content as software tooling is likely a large reason why the perspective he endorses here is not more widespread—that content is fundamentally a copy of a particular work, in the parlance of US copyright law (which isn't terribly domain-appropriate here so much as its terminology is useful)

در زمان کم بودن باطری خودمان متوقف کنیم خیلی چیزها رو ولی قبلش اطلاع بدیم به فرد ذی نفع

Can see can choose can set can enable/disable

notification push notification

Create User Stories Collaboratively With the collaboration of all the development team, the epics are broken into several smaller user stories that will be used in the sprint.

https://500ish.com/mastodon-brought-a-protocol-to-a-product-fight-ba9fda767c6a

https://www.eff.org/deeplinks/2022/12/user-generated-content-and-fediverse-legal-primer

Architecture can make UX suck.

https://borretti.me/article/unbundling-tools-for-thought

He covers much of what I observe in the zettelkasten overreach article.

Missing is any discussion of exactly what problem he's trying to solve other than perhaps, I want to solve them all and have a personal log of everything I've ever done.

Perhaps worth reviewing again to pull out specifics, but I just don't have the bandwidth today.

This is a terrible idea. At least if there's no way to opt out of it! And esp. if it doesn't auto log out the original user after some timeout.

Why? Because I may no longer remember which device/connection I used originally or may no longer have access to that device or connection.

What if that computer dies? I can't use my new computer to connect to admin UI without doing a factory reset of router?? Or I have to clone MAC address?

In my case, I originally set up via ethernet cable, but after I disconnected and connected to wifi, the same device could not log in, getting this error instead! (because different interface has different mac address)

🤗

We shape our tools and thereafter they shape us....

I came here after reading a couple articles (one on Super User & one on MS's help forums) recommending X-Mouse Button Control as a general way to disable back buttons on mice.

Note: this doesn't seem to work on Windows 11 for Microsoft USB IntelliMouse Optical.

https://fasiha.github.io/yoyogi/

Yoyogi is an alternate Mastodon reading interface that shows messages by author / thread and not as the traditional timeline.

Similar to Pinafore

why not allow user to do it directly instead of force to contact support? If they'll remove it for you because you said the user asked you to... why not just let you remove the suppression yourself? Mailgun lets you directly delete suppressions via their API.

From a gradual enrichment standpoint I understand but from a data entry standpoint this seems like more work.

Meta Pixel default behavior is to parse and send sensitive data

Wait, wait, wait... the software has a feature that scans for privately identifiable information and sends that detected info to Meta? And in other cases, the users of the Meta Pixel decided to send private information ot Meta?

I've only just noticed it now, but there is a "Verified" tab in my Twitter Notifications page to filter out notifications from verified users.

And this, in part, is just what makes social readers so valuable: a tight(er) integration of a reading and conversational interface.

https://simonwillison.net/2022/Nov/8/mastodon-is-just-blogs/

https://twitter.com/codexeditor/status/1590314248370286593

Index card and file folder influenced computer user interfaces.

https://app.sane.fyi/space/kevinmarks-gmail-com-tools-for-thought-87615

An example of the Sane user interface.

https://pinafore.social/

Pinafore is a web client for Mastodon, designed for speed and simplicity.

<small><cite class='h-cite via'>ᔥ <span class='p-author h-card'>Jessica Smith</span> in Small Web - Jayeless.net (<time class='dt-published'>07/03/2021 23:34:42</time>)</cite></small>

This is talked about in the user story book

https://readwise.io/reader/shared/01ge4efpkxh985s8eszbb9dr2e/

Simple user interface example of highlighting and annotations on an article in Readwise Reader.

https://www.denizcemonduygu.com/philo/browse/

History of Philosophy: Summarized & Visualized

This could be thought of as a form of digital, single-project zettelkasten dedicated to philosophy. It's got people, sources, and ideas which are cross linked in a Luhmann-sense (without numbering) though not in a topical index-sense. Interestingly it has not only a spatial interface and shows spatial relationships between people and ideas over time using a timeline, but it also indicates—using colored links—the ideas of disagreement/contrast/refutation and agreement/similarity/expansion.

What other (digital) tools of thought provide these sorts of visualization affordances?

Natto https://natto.dev<br /> built by Paul Shen https://twitter.com/_paulshen

https://www.loom.com/share/a05f636661cb41628b9cb7061bd749ae

Synopsis: Maggie Delano looks at some of the affordances supplied by Tana (compared to Roam Research) in terms of providing better block-based user interface for note type creation, search, and filtering.

These sorts of tools and programmable note implementations remind me of Beatrice Webb's idea of scientific note taking or using her note cards like a database to sort and search for data to analyze it and create new results and insight.

It would seem that many of these note taking tools like Roam and Tana are using blocks and sub blocks as a means of defining atomic notes or database-like data in a way in which sub-blocks are linked to or "filed underneath" their parent blocks. In reality it would seem that they're still using a broadly defined index card type system as used in the late 1800s/early 1900s to implement a set up that otherwise would be a traditional database in the Microsoft Excel or MySQL sort of fashion, the major difference being that the user interface is cognitively easier to understand for most people.

These allow people to take a form of structured textual notes to which might be attached other smaller data or meta data chunks that can be easily searched, sorted, and filtered to allow for quicker or easier use.

Ostensibly from a mathematical (or set theoretic and even topological) point of view there should be a variety of one-to-one and onto relationships (some might even extend these to "links") between these sorts of notes and database representations such that one should be able to implement their note taking system in Excel or MySQL and do all of these sorts of things.

Cascading Idea Sheets or Cascading Idea Relationships

One might analogize these sorts of note taking interfaces to Cascading Style Sheets (CSS). While there is the perennial question about whether or not CSS is a programming language, if we presume that it is (and it is), then we can apply the same sorts of class, id, and inheritance structures to our notes and their meta data. Thus one could have an incredibly atomic word, phrase, or even number(s) which inherits a set of semantic relationships to those ideas which it sits below. These links and relationships then more clearly define and contextualize them with respect to other similar ideas that may be situated outside of or adjacent to them. Once one has done this then there is a variety of Boolean operations which might be applied to various similar sets and classes of ideas.

If one wanted to go an additional level of abstraction further, then one could apply the ideas of category theory to one's notes to generate new ideas and structures. This may allow using abstractions in one field of academic research to others much further afield.

The user interface then becomes the key differentiator when bringing these ideas to the masses. Developers and designers should be endeavoring to allow the power of complex searches, sorts, and filtering while minimizing the sorts of advanced search queries that an average person would be expected to execute for themselves while also allowing some reasonable flexibility in the sorts of ways that users might (most easily for them) add data and meta data to their ideas.

Jupyter programmable notebooks are of this sort, but do they have the same sort of hierarchical "card" type (or atomic note type) implementation?

One might suggest that the freedom, flexibility, and customization of these systems is actually an unuseful time suck for many users which only encourages shiny object syndrome. From a design perspective, try starting out building a system that works for you before beginning on design for others. Research and looking at the user interfaces offered by the competition will helpful as well. Which are the most popular? fun to use? Why? What actual affordances do those interfaces and functionalities allow? are they truly productive?

Possibly more productive, what sorts of standards can you leverage to make people's pre-existing notes more useful? Can you take pre-existing stores of .txt or .md files and provide different views or perspectives on them? This will allow people to pick and choose which applications might work with their stores of data to provide different views or perspectives on them. Why reinvent a text editor or tools like Logseq or Obsidian when you can leverage the local stores of data to provide the sorts of services you're not seeing in the broader space? For example, on the "social media" side, there are existing solutions for taking your locally stored notes, putting them into the cloud and displaying them on the web, but the various steps are highly technical and require a relatively large amount of work and admin tax to maintain. A service that allows one to point at their local store of data and automatically host it on a website and keep it synced would be a major boon for the non-technical user.

Separately, Matuschak did not invent evergreen notes. The first clear cut instantiation I've seen in the literature is from Konrad Gessner in 1548, and honestly even his idea really stems from a longstanding tradition of working with commonplace sententiae preceding his work. (see https://hypothes.is/a/uEboYlOwEeykkotYs594LA) Matuschak simply applied the definition/idea of "evergreen" (meaning easily reusable) articles or content from journalism to describe his notes which could be reused in various contexts. (Example: Why rewrite an article on how to decorate and entertain for the holidays, when you can reuse the same article you've been publishing for years, perhaps along with some updated photos?) "Atomic" notes is another variation on this same theme, but is one which underlies the ability to re-use notes in combination with one or more other notes to generate new ideas.

I love that he closes the pamphlet again with a nod to comfort and ease of use.

...what this pamphlet has sought to do is to make it possible for the researcher to develop a way of doing things which will be as productive and as comfortable as possible.

...the usefulness of a note-taking system has an ultimate limit beyond which it becomes self-defeating. [...] After all, the ultimate purpose of the exercise is not to produce beautiful notes displaying the researcher's technical prowess, but rather usable notes to build the mosaic.<br /> —Jacques Goutor (p33)

Unlike many note taking manuals, Goutor advises that within the small list of rules and standards which he's laid out, one should otherwise default to maximizing the comfort of their note taking system. This may be as small as using one's favorite writing instruments or inks. (p28)

It's nice to see him centering self-care and small things which contribute to the researchers' mental health within note taking design and user interface.

Unnoticed design

The intention of design can go unnoticed, and people may not think of the factors and the expertise that went into making that conscious design choice.

Finding order and relations (and their particular types), is a form of linking ideas found in some of the more complex zettelkasten and knowledge management spaces. It's not as explicit here and he doesn't seem to be focusing on stating or writing explicit links within his notes. He does, however, place some focus on the quality and types of links he's making (or at least thinking about), something which isn't frequently seen in the current PKM space. For example, no one is creating user interfaces that show links between ideas which are opposite (or in opposition or antonym relation) to each other.

Applying the Google search experience to other services

Google's Page Rank algorithm might be good for searching information, but Amazon's search service has different priorities: selling you something that it wants to sell you. This is just one example of how translating the Google search experience to other domains is problematic. Another example is when there is lack of relevance context, like searching email; emails are not inter-linked with each other.

https://ncase.me/nutshell/

For those interested in the ideas of annotations, inline footnotes, expandable text, additional context, stretch text, hovercards, etc., Nicky Case has recently released a new project called Nutshell (https://ncase.me/nutshell/) which has some fun user interface as well as code with which to play.

https://render.plexus.earth/

One of my favorite things about Hypothes.is is that with a quick click, I've got a space to write and type and my thinking is off to the races.

Sometimes it's tacitly (linked) attached to another idea I've just read (as it is in this case), while other times it's not. Either way, it's coming out and has at least a temporary place to live.

Later on, my note is transported (via API) from Hypothes.is to my system where I can figure out how to modify it or attach it to something else.

This one click facility is dramatically important in reducing the friction of the work for me. I hate systems which require me to leave what I'm doing and opening up another app, tool, or interface to begin.

https://www.kevinmarks.com/memex.html

I got stuck over the weekend, so I totally missed Kevin Marks' memex demo at IndieWebCamp's Create Day, but it is an interesting little UI experiment.

I'll always maintain that Vannevar Bush really harmed the first few generations of web development by not mentioning the word commonplace book in his conceptualization. Marks heals some of this wound by explicitly tying the idea of memex to that of the zettelkasten however. John Borthwick even mentions the idea of "networked commonplace books". [I suspect a little birdie may have nudged this perspective as catnip to grab my attention—a ruse which is highly effective.]

Some of Kevin's conceptualization reminds me a bit of Jerry Michalski's use of The Brain which provides a specific visual branching of ideas based on the links and their positions on the page: the main idea in the center, parent ideas above it, sibling ideas to the right/left and child ideas below it. I don't think it's got the idea of incoming or outgoing links, but having a visual location on the page for incoming links (my own site has incoming ones at the bottom as comments or responses) can be valuable.

I'm also reminded a bit of Kartik Prabhu's experiments with marginalia and webmention on his website which plays around with these ideas as well as their visual placement on the page in different methods.

MIT MediaLab's Fold site (details) was also an interesting sort of UI experiment in this space.

It also seems a bit reminiscent of Kevin Mark's experiments with hovercards in the past as well, which might be an interesting way to do the outgoing links part.

Next up, I'd love to see larger branching visualizations of these sorts of things across multiple sites... Who will show us those "associative trails"?

Another potential framing for what we're all really doing is building digital versions of Indigenous Australian's songlines across the web. Perhaps this may help realize Margo Neale and Lynne Kelly's dream for a "third archive"?

This should probably say "later point" or "later date", correct?

Examples of existing types of mobilization systems: 1. Persuasive technology 2. collaborative technology 3. user experience 4. gamification

Previously: Open Source Is Not Enough and Free software is not enough: on practical user freedom.

See also: "Even GNU's philosophy has a few puzzle pieces missing from the box."

https://www.houstonchronicle.com/projects/2022/roe-opinion-annotated/

An interesting example of visual user interface of highlights and marginalia on a news site to help tell and report on a story.

https://docs.google.com/document/d/1N4LYLwa2lSq9BizDaJDimOsWY83UMFqqQc1iL2KEpfY/edit

P.R.O.B.E. rubric participation (exceeds, meets fails), respectful, open, brave, educational

Mentioned in the chat at Hypothes.is' SOCIAL LEARNING SUMMIT: Spotlight on Social Reading & Social Annotation

in the session on Bringing the Margins to Center: Introduction to Social Annotation

Looking at the idea of rubrication, I feel like I ought to build a Tampermonkey or Greasemonkey script that takes initial capitals on paragraphs and makes them large, red, or even illuminated. Or perhaps something that converts the CSS of Hypothes.is and makes it red instead of yellow?

What if we had a collection of illuminated initials and some code that would allow for replacing capitals at the start of paragraphs? Maybe a repository like giphy or some of the meme and photo collections for reuse?

How might we design better digital reading interfaces that take advantage of a wider range of modes of thinking and reading?

Certainly adding audio to the text helps to bring in benefits of orality, but what other axes are there besides the obvious spatial benefits?

If digital user interfaces and navigational difficulties inhibited reading comprehension in the modern age, what did similar interfaces do to early reading practices?

What methods do we have to tease out data of these sorts of early practices?

What about changes in modes of reading (reading out loud vs. reading quietly)?

I'm reminded of this as a hyperbolic answer, but still the root question may be an apt one:

https://www.youtube.com/watch?v=pQHX-SjgQvQ

https://blog.mojeek.com/2022/02/search-choices-enable-freedom-to-seek.html

User interface options in multiple search provider selection

Spencer's example of user interface below his posts to indicate how readers might comment on his website.

See also: The Pinocchio Problem

See also; plugging these: * A new publishing discipline * plain.txt.htm (An assembler)

This is an excellent piece, even though the writing is (probably intentionally) in places too obscure.

This wording seems quite profound.

It means that by creating a personification of our tools, we can more easily communicate with them.

Do people personify their computers? I remember in the late 80s and early 90s computer workstations, especially in university settings, having personified names.

Link this to the personification of rocks w.r.t. talking rocks and oral traditions.

link to: https://hypothes.is/a/KosdVt1qEeykU2dTuVZT3Q

See also An app can be a home-cooked meal along with this comment containing RMS's remarks with his code-as-recipe metaphor in the HN thread about Sloan's post:

some of you may not ever write computer programs, but perhaps you cook. And if you cook, unless you're really great, you probably use recipes. And, if you use recipes, you've probably had the experience of getting a copy of a recipe from a friend who's sharing it. And you've probably also had the experience — unless you're a total neophyte — of changing a recipe. You know, it says certain things, but you don't have to do exactly that. You can leave out some ingredients. Add some mushrooms, 'cause you like mushrooms. Put in less salt because your doctor said you should cut down on salt — whatever. You can even make bigger changes according to your skill. And if you've made changes in a recipe, and you cook it for your friends, and they like it, one of your friends might say, “Hey, could I have the recipe?” And then, what do you do? You could write down your modified version of the recipe and make a copy for your friend. These are the natural things to do with functionally useful recipes of any kind.

Now a recipe is a lot like a computer program. A computer program's a lot like a recipe: a series of steps to be carried out to get some result that you want. So it's just as natural to do those same things with computer programs — hand a copy to your friend. Make changes in it because the job it was written to do isn't exactly what you want. It did a great job for somebody else, but your job is a different job. And after you've changed it, that's likely to be useful for other people. Maybe they have a job to do that's like the job you do. So they ask, “Hey, can I have a copy?” Of course, if you're a nice person, you're going to give a copy. That's the way to be a decent person.

Interesting that this is written by a BSD guy.

similar to my strawman for language skins

هدف باید مشخص باشه و ریز (برای یک قسمت کار) مثل : ساخت حساب کاربری رابطه باید یک طرفه باشه باید هر مرحله رو زیرش توضیح بدیم تیک ضربدر میشه به فلوهای مجزا تقسیم کرد

Flow شبیه به الگوریتم و فلوچارت هست

فلوی کاربری

مراحل نوشتن یوزر فلو: شناسایی هدف کاربر (ریز اهداف ) نوشتن قدم های لازم برای رسیدن به هدف کشیدن فلوی کاربر

مراحی که کاربر برای رسیدن به هدفش انجام میدهد باید طوری طراحی شود که کاربرد به بنبست نرسد و به مشکل نخورد.

overflow.io flowmapp. analytics google

user story mapping شخص مشخص قدم ها در طول زمان هم مشخص

Release slice

از بالا به پایین ، کلیات به جزیییات تقسیم میشه

نقطه چین ها :تتوی کدوم ورژن میخوام باشه

user activities (backbone) user tasks (walking skeleton) user stories

WIP (work in progress)

user story writing workshop

OUTPU کمکه

OUCOME که چی؟ IMPACT تاثیر نهایی رو که میخواد

روایت عالی باید همه این سه تا رو داشته باشه

INVEST Independent negotiable valuable estimable small testable

Kids are the biggest and most expansive demographic to acquire users from.

let timer; // timer identifier const waitTime = 500; // Wait time in milliseconds

// search function const search = (text) => { // to do: make http request here }

// Listen for keyup event const input = document.querySelector('#input-text'); input.addEventListener('keyup', (e) => { const text = e.currentTarget.value; // clear timer clearTimeout(timer);

// Wait for X ms and then process the request timer = setTimeout(() => { search(text); }, waitTime); });

Step 1. Listen for User Input

<input type="text" id="my-input" />

let input = document.querySelector('#my-input'); input.addEventListener('keyup', function (e) { console.log('Value:', input.value); })

Step2: Debounce Event Handler Function

let input = document.getElementById('my-input'); let timeout = null;

input.addEventListener('keyup', function(e) { clearTimeout(timeout);

timeout = setTimeout(function() { console.llog('Input Value:', textInput.value); }, 1000); })

I'm sure I read this ages ago, but it's not in my notebook yet. Perhaps worth another pass for notes.

https://winnielim.org/library/collections/personal-websites-with-a-notes-section/

Winnie has some excellent examples of people's websites with notes, similar to that of https://indieweb.org/note. But it feels a bit like she's approaching it from the perspective of deeper ideas and thoughts than one might post to Twitter or other social media. It would be worthwhile looking at examples of people's practices in this space that are more akin to note taking and idea building, perhaps in the vein of creating digital gardens or the use of annotation tools like Hypothes.is?

What other forms/shapes might it take?

The randomness of interesting tidbits in a social media scroll help to put us in a state of flow. We get small hits of dopamine from finding interesting posts to fill in the gaps of the boring bits in between and suddenly find we've lost the day. As a result an endless scroll of varying quality might have the effect of making one feel productive when in fact a reasonably large proportion of your time is spent on useless and uninteresting content.

This effect may be put even further out when it's done algorithmically and the dopamine hits become more frequent. Potentially worse than this, the depth of the insight found in most social feeds is very shallow and rarely ever deep. One is almost never invited to delve further to find new insights.

How might a social media stream of content be leveraged to help people read more interesting and complex content? Could putting Jacques Derrida's texts into a social media-like framing create this? Then one could reply to the text by sentence or paragraph with their own notes. This is similar to the user interface of Hypothes.is, but Hypothes.is has a more traditional reading interface compared to the social media space. What if one interspersed multiple authors in short threads? What other methods might work to "trick" the human mind into having more fun and finding flow in their deeper and more engaged reading states?

Link this to the idea of fun in Sönke Ahrens' How to Take Smart Notes.

Standard Ebooks's search needs to incorporate alternate titles. I tried searching first for "the underground man" (my fault) but then I tried "notes from the underground", which turned up nothing. i then began to try searching for Dostoyevsky, but stopped myself when I realized the fruitlessness, because even being unsure if search worked across author names, I knew that I had no idea which transliteration Standard Ebooks was using.

Why is Standard Ebooks sending content-security-policy: default-src 'self';? This is not an appropriate use. (And it keeps things like the Hypothesis sidebar from loading.)

In an ever-increasing sphere of digital print, why can't publishers provide readers a digitally programmed selection of footnote references in texts?

This digital version of Annie Murphy Paul's book has endnotes with links from the endnotes back to the original pages, but the opposite links from the reading don't go to the endnotes in an obvious way.

I'd love to be able to turn on/off a variety of footnote options so that I can see them on the pages they appear, as pop up modals, or browse through them in the end notes after-the-fact as I choose. This would allow me to have more choice and selection from a text based on what I want to get out of it rather than relying on a publisher to make that choice for me.

Often in publishing a text written for the broad public will "hide" the footnotes at the end of the text in unintuitive ways where as more scholarly presses will place them closer to their appearance within the text. Given the digital nature of texts, it should be possible to allow the reader to choose where these items appear to suit their reading styles.

Types of requirements in a SaaS selection

There are different types of requirements. In this article we divide the requirements into a number of categories that help us with the software selection.

Kartik made a similar remark in an older version of his mission page:

Open source would more fully deliver on its promise; are the sources truly open if they take too long to grok, so nobody makes the effort?

https://web.archive.org/web/20140903010656/http://akkartik.name/about

I don't think so. I think it's rather the opposite. Churn is one of the biggest causes for what makes modifying software difficult. I agree, however, with the later remarks about making it easy to delete code where it's no longer useful.

I have learnt to abandon such attempts of adaptation fairly quickly, and to start the design of a new program according to my own ideas and standards

Feature request (implement something that allows the following): 1. From any page containing a bookmarklet, invoke the user-stored bookmarklet בB 2. Click the bookmarklet on the page that you wish to be able to edit in the Bookmarklet Creator 3. From the window that opens up, navigate to a stored version of the Bookmarklet Creator 4. Invoke bookmarklet בB a second time from within the Bookmarklet Creator

Expected results:

The bookmarklet from step #2 is decoded and populates the Bookmarklet Creator's input.

To discriminate between invocation type II (from step #2) and invocation type IV (from step #4), the Bookmarklet Creator can use an appropriate class (e.g. https://w3id.example.org/bookmarklets/protocol/#code-input) or a meta-based pragma or link relation.

Bookmarklets and the JS console seem to be the workaround.

For very large customizations, you may run into browser limits on the effective length of the bookmarklet URI. For a subset of well-formed programs, there is a way to store program parts in multiple bookmarklets, possibly loaded with the assistance of a separate bookmarklet "bootloader", although this would be tedious. The alternative is to use the JS console.

In FIrefox, you can open a given script that you've stored on your computer by pressing Ctrl+O/Cmd+O, selecting the file as you would in any other program, and then pressing Enter. (Note that this means you might need to press Enter twice, since opening the file in question merely puts its contents into the console input and does not automatically execute it—sort of a hybrid clipboard thing.) I have not tested the limits of the console input for e.g. input size.

As far as I know, you can also use the JS console to get around the design of the dubious WebExtensions APIs—by ignoring them completely and going back to the old days and using XPCOM/Gecko "private" APIs. The way you do is is to open about:addons by pressing Ctrl+Shift+A (or whatever), opening or pasting the code you want to run, and then pressing Enter. This should I think give you access to all the old familiar Mozilla internals. Note, though, that all bookmarklet functionality is disabled on about:addons (not just affecting bookmarklets that would otherwise violate CSP by loading e.g. an external script or dumping an inline one on the page`).

There're lots.

The ability to resize the Hypothes.is drawer is already built into the Hypothes.is interface natively. In the top left of the drawer there is a ">" tab that you can drag to resize the annotations window to suit your needs. Clicking on it will allow you to open and close the pane as needed. If it's closed (the icon appears as "<"), you can highlight and choose "annotate" or "highlight" and it will automatically re-open the Hypothes.is interface.

While being able to view the history of a problem space from the perspective of a creation process is interesting, in reverse, it is also an interesting way to view a potential learning experience.

I can't help but think about the branching tree networks of knowledge in some math texts providing potential alternate paths through the text to allow learners to go from novice to expert in areas in which they're interested. We need more user interfaces like this.

Given the propensity for technologists in the late 90s and early 00s to have rose colored glasses with respect to their technologies, it's nice to see at least some nod to potential misuses and bad actors within the design of future tools.

This sounds a lot like the management philosophy of W. Edwards Deming who encouraged managers to empower workers to take ownership of their craft and work.

@pratik Mastodon caps at 500 as a default. The information density of the particular language/character set is certainly part of the calculus.

Here's a few to start (and see their related references): - https://www.semanticscholar.org/paper/How-Constraints-Affect-Content%3A-The-Case-of-Switch-Gligoric-Anderson/de77e2b6abae20a728d472744557d722499efef5 - https://www.nature.com/articles/s41599-019-0280-3

Ideas fill their spaces.

When writing it can be daunting to see a long blank screen and feel like you've got to fill it up with ideas de novo.

From the other perspective if you're starting with a smaller space like a Twitter input box or index card you may find that you write too much and require the ability to edit things down to fit the sparse space.

I do quite like the small space provided by Hypothes.is which has the ability to expand and scroll as you write so that it has the Goldilocks feel of not too small, not too big, but "just right".

Micro.blog has a feature that starts with a box that can grow with the content. Once going past 280 characters it also adds an optional input box to give the post a title if one wants it to be an article rather than a simple note.

Link to idea of Occamy from the movie Fantastic Beasts and Where to Find Them that can grow or shrink to fit the available space: https://harrypotter.fandom.com/wiki/Occamy