slow
72 posts

slow
@slowfft
engineering and design at Jot ~ opinions not my own





there should be 2 parallel internets: a human-only internet and an AI-only internet. anything else would be very painful.









have any of you ever met up with someone you got to know on the internet



Collecting metrics from a large IRC network, researchers found in 2008 that posting activity eventually tops out regardless of community size. "discourse … appears to be limited to 40 posters in any 20 minute interval" There are interesting implications, so let's take a look. Message density (messages sent per user within a given time interval) was seen to drop sharply until a channel had around 40 active posters implying that the number of lurkers or inactive users in an instant messaging chat grows asymptotically with channel size. This decay is in part due to (1) human information-processing constraints; to cope with a large stream of messages a user will either start lurking or selectively respond to certain users which means taking activity elsewhere, and (2) user interface boundaries (lack of space). Some thoughts: Obvious as it might seem, hard limits to meaningful activity are inherent to any social space. Effective design of communication tools must treat these concerns with care and attention. Different tools possess different qualities which nudges users toward different behaviours. For any given tool one might consider: • Does interaction require presence? • Is content ephemeral or persistent? • How structured is the communication? Hierarchy, threading, searchability, linearity? • How much context does parsing a piece of information require? Let's look at two very different modes of communication: 1. A blog is asynchronous, persistent, structured and usually does not require context to parse (but may assume some topic knowledge). 2. A video meeting requires all participants to be present, may or may not be recorded, is semi-unstructured and most things being said are highly contextual. The video meeting demands more of each participant since even just a momentary lapse of attention might make them lose the context with no way to backtrack. This is naturally compensated for through repetition and less dense communication. The tradeoff is that interaction is fast, bidirectional and personal. Instant messaging tools are by far the most varied in terms of implementation and design, making them extremely versatile and therefore ubiquitous. However, users will always be subject to information-processing constraints. Anyone building a social space should probably take the qualities discussed above into consideration and keep in mind that there are advantages to each. I'd like to write more on this eventually, especially regarding how to design the interface and experience around the hyper-synchronous real-time text mode (messages shown as they are typed) in a way that manages information overload. … but I'll stop here. Thanks for reading!

Crypto has broken my concept of money In college I used to work 8h shifts for $100 Now I lose $3k on a stop and it barely registers "Damn I only made +$900 today" Follis you dumb mfer that is a doctor's salary

does the internet ever bore you? then let me introduce you to real-time text... we've created @jot_chat, a place where you can host communities and chat with people in a truly novel way, leveraging technology that makes chatting feel just like speaking and listening. read on...

My dear front-end developers (and anyone who’s interested in the future of interfaces): I have crawled through depths of hell to bring you, for the foreseeable years, one of the more important foundational pieces of UI engineering (if not in implementation then certainly at least in concept): Fast, accurate and comprehensive userland text measurement algorithm in pure TypeScript, usable for laying out entire web pages without CSS, bypassing DOM measurements and reflow

My dear front-end developers (and anyone who’s interested in the future of interfaces): I have crawled through depths of hell to bring you, for the foreseeable years, one of the more important foundational pieces of UI engineering (if not in implementation then certainly at least in concept): Fast, accurate and comprehensive userland text measurement algorithm in pure TypeScript, usable for laying out entire web pages without CSS, bypassing DOM measurements and reflow

@onehappyfellow bidirectional scroll with content load+unload that works across all browsers and mobile



With all due respect to Andrew, in his motivational post, he didn't explain why anyone would write code by hand. I can code, but I consider coding by hand a waste of time. So, if I, the one who already knows how to code, consider this a waste of time, why would anyone learn something which is very hard to learn only to then consider it a waste of time, like I do?




