mtwittman

The single most problem-reducing maneuver I've tried with home network printers is getting the printer off plain DHCP and make it consistent (set a static IP manually [outside your DHCP range] or by DHCP reservation).

After sorting this out in the router, then add the printer to the various desktops/laptops/tablets/phones.

Maybe I'm imagining the improvement, but I don't think so (and it can't hurt).

First, congratulations, hamaluik. This especially made me smile because I went through a similar experience - in the early 2000s, inspired by kids’ births I had the itch to evolve the manual process of a 'game' with our extended family—gathering/compiling their guesses at a name and other birth stats.

So I designed a free (and no ads) web app[0] for me and so others could automat their own pools.

It also has “bebe” in the app name :)

Just as an historical point: There were just two other 'baby pool' type web apps on The Internet at the time (2003~2005). One of those two disappeared a few years ago. This was before conventional wisdom would be that facebook integration was a prerequisite for mass audience success for this kind of app. I was never interested in hitching my wagon to FB or any other third party. I’m happy it’s an independent piece of old school web 1.5 / 2.0 that still kicking a decade and a half later. I hope your app has a long life as well.

Anyway, cheers!

[0] https://bebepool.com

This is important to be aware of, but there is some nuance.

According to this BB blog post[0] certain functions are unavailable ("making a new purchase, installing new trials, signing in to your account, creating new accounts, enabling B2, and creating a master Key"), and two B2 API calls (b2_create_bucket, b2_delete_bucket).

If these are the only disrupted features, then impact depends on the details of the use case (perhaps get object and friends have to be on demand but other changes can be async).

Now, why these specifics are in their blog post and not in the Scheduled Maintenance page itself, that is a fair question, because it leaves room for doubt that only this exact set of functions are affected each and every window.

[0] https://help.backblaze.com/hc/en-us/articles/227807447-Backb...

This article is not an exclusive (but some on medium are), so here's the canonical non-paywalled version:

https://pluralistic.net/2021/10/08/unfollow-everything/#shut...

Cory seems to be up front about the conditions of his various forms of publishing:

How to get Pluralistic:[0]

Blog (no ads, tracking, or data-collection):

Pluralistic.net

Newsletter (no ads, tracking, or data-collection):

https://pluralistic.net/plura-list

Mastodon (no ads, tracking, or data-collection):

https://mamot.fr/web/accounts/303320

Medium (no ads, paywalled):

https://doctorow.medium.com/

Twitter (mass-scale, unrestricted, third-party surveillance and advertising):

https://twitter.com/doctorow

Tumblr (mass-scale, unrestricted, third-party surveillance and advertising):

[0] https://pluralistic.net/2021/05/05/clarkes-third-law/

Consider a different approach to mitigate automated URL fetching interference (this can apply to both email ownership verifications and password resets).

Make the emailed verification/reset link (GET request) idempotent (1 and >1 request has the same effect).

Have the link just present an interface for the user to take the next step. In the next step make a POST request that actually commences your verification/reset process.

In all likelihood you'll want expiry logic (let's say it's 30 minutes) - if you store the token with a created_at timestamp on the server you can have your verification/reset process check that now < (created_at + 30 minutes)

If expired, provide a UI for the user to request a fresh verification/reset email.

At the moment anyway, that XML link won't render per an XML parsing error. For anyone who wants a quick look at what these XML docs look like here's one for UUID6 [0].

[0] https://github.com/uuid6/uuid6-ietf-draft/blob/master/draft-...

I use the expiration date in KeepassXC and here's my thought on it in particular: I want the KP date-time field to err on the side of simplicity (implementation and interface).

Seems to me best practice of renewing accounts is to always apply padding (TODO: renew Foo today because it expires in roughly n days); if you make as a minimum n >= 2 (or how about >=3 as a safety factor) then you don't have to consider how the account provider administers their cut-off (expires at 00:00 vs 23:59, is timezone a factor?, etc).

With this approach the difference between 'instantaneous time' and 'calendar time' are, for practical purposes, a moot point.

So the date I enter into the KeepassXC field has the padding included. The expiry date as described by the provider I can put in the note field for additional reference.

The research and engineering of new mobility aids is fine, but the inventor/CEO's quote, "Ten years from now, there will be no, or far fewer, wheelchairs" belies an attitude strongly criticized by many in the disability community. And in the video footage he says, "wheelchairs are an anomaly, men and women, human beings are meant to be upright". Imagine saying "Bicycles an anomaly—humans are meant to be upright, not in some aero-dynamic tucked position." Deriding one form mobility tech (an asset to more than 10,000,000 people) to promote another potential one is disappointing.

The Exoskeleton's Hidden Burden [0] is a good article that includes the history of exoskeleton development (goes back to 19th c. Russia):

[0] https://www.theatlantic.com/technology/archive/2015/08/exosk...

The handle/touchpoint is not full user journey, let's pull back and explore the approach, the threshold navigation, the bio-mechanical motion & timing — the bigger picture: "How to open a door - Finnish instructional video from 1979"[0]

[0] https://www.youtube.com/watch?v=Wof0xPUmW38

Also good[0].

0:https://99percentinvisible.org/episode/interrobang/

Earlier this month I got tired fumbling through all the little steps to use notes app for scanning and then separating out the PDF so I blogged[0] up the steps (including screencaps).

[0] https://wittman.org/blog/scan-paper-document-to-pdf-with-iph...