Hacker Newsnew | past | comments | ask | show | jobs | submit | charlieboardman's commentslogin

From what I can ascertain, the new bigger battery is incompatible with the old chassis: https://frame.work/products/pro-battery-74wh

"This product can only be used with both the Framework Laptop 13 Pro Bottom Cover and Framework Laptop 13 Pro Input Cover."

I applaud that the mainboard and keyboard are backwards compatible, but I don't think the pro is quite as backwards compatible as some are thinking


They actually call out this specific incompatibility in the video here (at 2m44s): https://www.youtube.com/watch?v=JSxgCEpkiKM&t=2m44s

Mainly just a trade-off because of because of the bigger battery (but it sounds like they'll sell you the bottom chassis pieces as well).


Yup. Sounds right. Interestingly though, you can use the new input cover with the older frames.


Receive email, render page with the email and a reply section and a unique ID, print it out physically

Human picks up all the sheets out of the printer, writes out replies with pen

Human puts the stack of answered email sheets in a multi-page scanner

Scanner physically scans them, agent transcribes them and matches them back to the incoming emails via the unique ID on each sheet, sends replies

You could adjust this flow for anything where human input is just one part of a larger sequence: just add print -> write -> scan into your flow where you'd normally have a human type. It's kind of a rebirth of faxing


On one of my first qualified jobs, my manager (a lovely older lady) did exactly this. All incoming emails were printed and put into a binder. Then she would go home, write an answer with a pen on the back side of every single one, and on the next day write a new email to the recipient. 10-15 % of all emails she sent this way would bounce because she had written the address incorrectly.

When I showed her the reply button in Eudora (this was in 2001), she was so happy that she bought me a cake.

She struggled with IT but was tack sharp otherwise. So far she's the only boss I've ever really liked.


Eudora! My mom used Eudora when I was a kid


I will say scanners are somewhat unergonomic, but if you had a high enough definition camera, you could photograph the document in its "natural environment". Granted, it's harder to get an evenly lit picture that way, but I think it's a nicer interface.


Scanners with automatic feeders are ergonomic when you have to scan more than a page or two. Just place your stack of paper in the feeder and press start. I had a job where I used to do that routinely, and no way a camera would have been more convenient.


All of my document "scanning" for the last—god, maybe 15 years?—has been with a phone camera.

Before everyone just started using Docusign anyway, I'd bought houses with a phone "scanner". LOL.

I don't think I started with it, but for a very long time I've had an app called TinyScanner that's good-enough at edge detection, can de-noise or make a document entirely black & white, and can glue multiple pages together into a PDF. The results look better than plenty of flatbed scanner results I've seen, if not as good as the best of those.


I've been using Genius Scan for ~15 years and it also lets you send faxes (via credits you buy). My phone works for 99% of my use cases.


Fair enough, I actually have been thinking about this topic lately since I have to generate and print and fill out and sign a lot of paper vouchers in my job. I would prefer having a dedicated scanner to just throw them into in a stack with a server/cron job/bash script always watching for new incoming documents rather than a more complex camera setup but yeah something like a camera over your shoulder on your desk could pick up documents too


This is fixed by using anoto paper and a supporting pen!


I always wished I could throw my Pocketmod[0] in the scanner at the end of the day and have a nice new one with any notes I wanted to carry over to the next day freshly printed and waiting in the morning.

[0] https://pocketmod.com/


If they have stock outlook they are doing normal networking and are connected to the normal internet over some deep-space antenna setup. So why not just use Debian and gmail in the browser if you want easy? The ISS uses Debian. I can't believe it's too hard to get astronauts to open Firefox


The browser would be far too slow for practical use. Local fist software, which ironically outlook is, would be the way to go.


Does the modern PWA-based outlook even support offline access? I know the old outlook that is no longer being updated does.


Old Outlook still works and is supported until ~2029. We still use it here.


what is old Outlook? for me that's Outlook Express 6 :D


Gmail is not an Outlook replacement. Gsuite as a whole has more or less the required pieces, but there is no single google product that covers the feature set of Outlook + Exchange.


My Steam password is one short weird phrase that I can remember. I haven't changed it since high school, ~15 years ago. Never had any security issues.

The modern landscape is frustrating because that setup actually works. Passwords, from a technical perspective, are actually great and are are bulletproof as long as they don't leak. No 2FA required. The entire issue is data leaks and phishing.


They are not, 100% strictly speaking, “ensured”. But they are 128bit numbers, so you have realistically no chance of generating a uuid that someone else has already. Age-of-the-universe type chances of duplicating one.


They are; the blog post explains why.


I have been hoping for compatibility layer + application flatpaks for a while so it’s nice to see someone doing it. My dream is to have a bunch of flatpaks for the Microsoft office suite


I actually have a lot of firsthand experience with limewash on stucco. I don’t know if our lime guy is just screwing it up, but I have been very unimpressed. The claims of vibrancy and longevity just don’t pan out in my experience. A house project I worked on last year used limewash and it’s already falling off and fading. It may have been the contractors not applying it properly, but our lime guy himself said the issue was applying to a wall that the sun was hitting, so it dried too fast. It seems like a very fragile process to get everything right, which makes it a huge pain to use.


One of the first things that this PDF talks about is the application of limewash to different substrates, and how different substrates must be prepared differently.

It sounds like the kind of thing a lot of tradespeople would screw up- like it requires study to do properly. They specifically call out how mortars and renders (which includes stucco) should be composed with the 'mechanical keying' of limewash in mind.


Most important preparation in my experience is to mist the substrate before application to prevent rapid drying.


The last paragraph on page 10 has some interesting information on applying in very dry and hot conditions. Repeated wet/dry cycles each day during application are important for promoting the carbonation to make the final surface durable.


It has to dry slowly to crystalise properly. Hanging damp hessian over the freshly painted wall is a common practice.

It's the same when using lime mortors, you are generally looking for a three day cure for mortor. Lime does not like the sun, wind, or rain (basically any weather!) during this time.


To expand on the angles of a polygon idea. It looks like each of these tracks has about a 30 degree bend. So you should have 360/30 = 12 more right-handed than left-handed tracks, or vice versa. It takes some counting, but you could probably get pretty quick at going around the track and adding or subtracting 1. If you end at 12, perfect. Your distance from 12 is an estimator for tension.


This is necessary but not sufficient for there to be no tension. For example, if you have 12 curved pieces, all curving in the same direction, and one straight piece, there will be tension.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: