sj4nz

Twitter could possibly fund itself for a long time if they hosted a pay-per-view event of the moment they lock and disable that account for policy violations.

It could be the most profitable 5-minutes of pay-per-view streaming in history and also simultaneously the most amazing test of Internet resiliency, ever.

Did anyone try the setting the terminal to "Developer Tools" permissions and find that things go worse?

Consider that the first-order effects of just _older people dying_ may not be everything entailed with this outbreak:

https://www.cbsnews.com/news/kawasaki-disease-coronavirus-il...

A _novel_ virus means we don't know what it does to everyone yet. At a minimum, closing the schools globally probably has saved millions of children from this "new polio"... for now.

Perhaps also maybe grandparents would like to live long enough to see their _healthy_ grandchildren again.

Thanks for reposting(?) this, I was trying to remember what this project was the last time it was mentioned on HN.

So far my only gripe for picture-in-picture is no closed captioning from sites like YouTube. Otherwise, fantastic as has been usual for Firefox.

The problem with a "normal" app is now you are beholden to the rules/regulations/evaluations of a third party that can easily decide without recourse that your "app" should not be in their store. Even if your app "is fine" every update and upgrade incurs a delay through the third party's reviewing process before your users receive it.

If the web browsers would provide _some API_ for persistent storage without yanking the carpet out from underneath developers this wouldn't be such a huge problem. There _used_ to be a file-access API but it was removed.

Personally, I think web browsers are too large a surface area to secure/keep secure and the world is probably going to swing the opposite direction to native, downloadable applications without the interference of a third-party store.

https://github.com/janestreet/bonsai is making some interesting distinctions between "UI state" and "model state". They're kept separate and they're working on utilities to manage the use of composed components.

Almost, but not quite. Zettlekastenicians (Zettlekasatengineers?) try to only put succinct thoughts into their systems that they can tend and grow into larger productions of thinking or learning--there are some more specialized amounts of explicit metadata (your thoughts, ideas, inspirations, questions) that cannot be crawled and indexed by machine which will only see the implicit metadata.

If you index everything together you get something that it is merely a pile of searchable things. You do not experience the "conversation" with the slip-box as Niklas Luhmann described it. Software like http://zettelkasten.danielluedecke.de/ that implements the "digital version" of the system suffers from what I like to describe as the "Hudsucker Proxy" problem: A young idealist visionary comes out and holds a big plastic loop and mutters "You know... for kids!" and nobody has a clue what that is supposed to mean. It isn't until someone shows how to use the "big plastic loop" before anyone understands what's happening. And that's really hard to do with something as abstract as a Zettlekasten despite it just "being little notes gathered together with lots of numbers and letters pointing at the other notes" or an "unordered database".

While it is painful to move, the frequency for repeat customers will doom most disruptors. An established company with a massive network like U-Haul could do it except for the fact that moving things is a skill that people consider to be "just manual labor" and avoid paying accordingly.

For apartments though, I could see a "house concierge moving" as-a-service being a possible disruption of established moving companies. E.g. they move you for "free" for appropriately long and priced lease. The "hostage holding" of your goods is a non-event here since the goal is to have a happy tenant.

I especially like this idea where you distill data into its most primitive form. It isn't quite as hairy as using n3-notation, but the ability to just collect the data without regard to being CSV or SQL gets you to an interesting space where tracking these changes with GIT works better. I've worked with CSV with 400+ columns (don't ask it was a horror) and SQL is really too verbose for these kinds of collections.

GNU Recutils is a nice metalanguage for data. You can churn out CSV from it which in turn can be \copy loaded into PostgreSQL. Maybe its too many steps, but I found it an important format for creating the logical model of representing data without predisposing it to any other technology or encoding.

Unfortunately its org-mode integration with emacs is broken when using spacemacs-- to far for me to fix as I'm no Elisp wizard.

Definitely looking forward to the Unum Type III alternative to floats. This is a nice visualization and it gives you an idea of how many NaN's waste the bits being used.

My gut feeling is search is bad everywhere because no one provides a pure-text API to the content. Cleaning data is hard and its easier to chuck in all the text blasted off an HTML page than to exclude everything non-signal.

I have no answers for Microsoft File Search, it never returns any results for me, I wonder if they even tested it sometimes.

When I'm ready to flip the table over about search results, I remember that https://millionshort.com/ exists and I give that a whirl. Then when I'm sick of seeing links to sites that are highly-SEOed but low-signal, Tampermonkey is there to give me a nice little [block] button to remove them.

Fantasy-future: Mozilla could "widen out" their library and hire 20,000 librarians to curate the "New Web" in a non-wiki-format. If you paid each librarian about $150K/annum, that's about $0.60/annum from 5B subscribers, just for their salaries for the advertising-free library.

Movie reference from Jurasic Park (1993). https://www.youtube.com/watch?v=T4kBRC2co7Y [perhaps a spoiler...]

Twitter in ~2007-2008 was an amazing place when you interacted with actual people.

But now the "frog has boiled" and the humanity has long left Twitter. Practically every interaction between entities on Twitter now is generated by some kind of bot or script that you're essentially trying to communicate with nothing. If there weren't Twitter API limits it would consume more energy and data storage than all the crypto coins combined (slightly hyperbolic). I've left Twitter and I have no desire to return.

However, if Twitter decided to "embrace humanity" and use the API limit system (which already exists) for accounts to increase the value of an interaction they might have a chance to bring back that earlier magic. Scarcity would increase the value, and if you could only post 5-10 new tweets per day you would certainly spend more time considering what you do on Twitter and make it easier for Twitter to identify the sources of noise in the signal.

I got curious and found https://asciidoctor.org/docs/asciidoctor-diagram/ is available. Important if you're not wanted to "delegate" this to a web-service.

I've installed fathom and self-hosted it. Seems to work pretty well.

This so much. Handwriting quality helps me decide which paper should be tossed. If its agitated like you describe, the value of the information on it is probably trash and therefore it goes into the trash.

Let's write this out in TeX:

$hell^{no}$

I'm already there wanting to stop using phone numbers. So. Much. There.

I haven't had a "land line" in multiple-decades. My short list of "the next thing" requires:

- Ability to install on a mobile device without any connection to a "phone number." Phone numbers in my mind are dead. - Skip the synchronous social convention of calling. Everything should be async by default. You don't ever cause someone's device to interrupt them. This is already culturally "accepted" with SMS. Unopened messages are deleted after some number of days. - With permission, these asynchronous messages should be forwardable. You give permission in advance of course, and then you can avoid having to repeat yourself again and again. - TMDA style whitelisting for unknown public keys wishing for contact. Addresses need some kind of seniority (older than 30-days) and some reasonable integration into the network at large (vouching connections between other people with "skin in the game", akin to a shared reputation--If I could remember the name of that early social network that tried to do this, avogato.org? Something like that.) - Mesh networking forever. Decentralize it all.

This is not something that I think can be a "startup," because this needs to be a protocol, not tied to any firm. If anyone's software works with the protocol, then let the "best installable" win. The closest thing to this right now is Scuttlebutt protocol and if someone could re-introduce contact sharing via "bumping" (using the accelerometer and GPS location and time together) devices together to exchange public keys, that particular bit of UX could go a long way to making it easier to adopt. However, the worst part of Scuttlebutt's capabilities has been the storage consumption for very popular identities that often consumes all the available memory on smaller devices. It needs data-storage hygenics--some way for the end-user to state what kind of data they want to keep and what they wish to ignore.

Giving this a try. Its really ugly but the concept works.

Someday I might buy an ortholinear keyboard for the desktop, it depends really on when the DasKeyboard deck breaks.

Hijacked scrolling site is my second-ranked peeve below the website that pops an overlay to "subscribe". Closed the tab before I could enjoy the design.

I gave up on Skype a long long time ago. Aside from the dumpster fires of their clients, their attempts to manage the spam/bot problem make legitimate use nearly impossible because they keep disabling "new, lightly used" accounts.

Unrelated: Your speech-to-text result threw me for a loop, "moose Leon" (mostly)

Related: A hardware "Dash" button made more sense in a time when mobile smart devices were not ubiquitous. The recommended items I see are really strange, often items that are "one-offs" which I might only buy once every ten years are recommended. This to me is a serious problem with their algorithm.

This is pretty good perhaps even for auto-generated absurdities:

Seed with: "Why does my dog speak poor English?"

> It's possible your dog has a rare genetic condition called dyslexia, which puts him or her at risk for learning difficulties. If the problem has progressed beyond a certain point—say, if your dog has been in the hospital for over a year—and when you go to bring him out of the hospital—not for exercise or exercise training—he may not speak English in the proper way. Your veterinarian will work on the problem while you are in the hospital.

What should I do with a dog with dyslexia?

It's important to be vigilant and familiar with what is going on with your dog in hospital. If you find that your dog may be learning, take him home and have him trained as soon as possible. It may take a while for your dog to learn to associate the letters of English with words.

I've seen this when the company switched the "exercise" as a no-wait-solve-this-one-instead which was fairly obvious it was a work-related task that was being farmed out to candidates.

Sounds very zettelkasten-esque.

I'm working on something just for this, no A.I required. Most of the problems with eating healthy in my opinion is just being prepared with the stuff to make and deciding what to make in advance. Most of the problems I've found with existing "food/recipe sites" is they quickly devolve into "branded advertising", "data collection", and/or "choice overload." Does any site really need over 10,000 choices of "chicken soup" recipes? The other problem with the Internet (there are always more problems with the Internet) is when you search for recipes in the uncurated web, every recipe is prefixed by an intensely personal story about the family you don't even know. Once you find that recipe, it's in a tiny hard to read box (I don't know who made this template) that naturally has been made very hard to copy and paste elsewhere.

Its a terrible user experience.

My idea isn't ready yet, but I'm furiously working on the MVP.

Absolutely excruciating.

I'm _this_ close to cancelling Netflix because of this behavior on Roku. Also the utter lack of closed captions configurability is wearing on my nerves.