aard

Homepage?

Long range stuff typically is UHF RFID in the 860-960MHz band.

HF NFC at 13.56 MHz can be done up to roughly 20cm, though with passive sniffing you might pick up parts at longer range.

LF NFC is just a mess. I think there were some pretty long range readers available, but nobody should be using that stuff anymore, it's just horrible. Unfortunately there still are companies using that for access control, so I'm now and then handing out copies of their keys to friends. The main security on those things is that sometimes it takes a few tries to get the your reader detect the tag.

it's an 8 character code of mostly digits and two upper score letters.

That's the UUID of the VFAT filesystem on the card, so if you clone the card and then resize the partition you'll keep the same filesystem UUID on the new card.

Summary judgment seems unlikely given the vagueness of the email.

In other circumstances that kind of phrasing would be interpreted of intent to commit illegal activity - so I'd hope large companies can't just get away with openly planning shit by just ensuring vague phrasing.

That attack is via bluetooth, not NFC. And the article states exactly that (just checked).

I'm not aware of any correct email validations. I'm still looking for something accepting a space in the localpart.

Also a surprising number of sites mess with the casing of the localpart. Don't do that - many mailservers do accept arbitrary case, but not all. MyName@example.com and myname@example.com are two different mail addresses, which may point to the same mailbox if you are lucky.

Are you trying to press the keys as lightly as possible or something?

Pretty much the opposite, I'm usually either typing on a buckling spring keyboard, or on one with Kailh Box Navy switches - which requires quite a bit of force, and both have quite a bit of travel.

low profile

that is a problem

easy to type on quickly

not really, doesn't have a clear pressure point, so leads to keys not registering surprisingly often. I also get pain in my hands if I'm working on it for several hours.

I only can do something like 70-80 WPM on that, on a proper keyboard I'm doing slightly above 100.

lights up

Don't care about that.

Additionally half the useful keys (pgup/pgdown/end/home/insert/delete/...) are hidden behind FN combinations.

I recently had the need for some apple hardware due to customer projects - and ended up buying an air with 16GB of RAM when it was available relatively cheaply.

The keyboard is shit - but keyboards are shit on pretty much any notebook nowadays unfortunately.

Both memory and storage are a problem - the rest is surprisingly nice. I also have a Windows arm notebook from HP, same 16 GB storage issue, but at least the SSD is user replacable.

We should get rid of 8GB base models in general - that's pretty much what you'd expect in a phone nowadays, but not in a computer.

This is an Xorg thing - for wayland you'd have to implement that kind of functionality yourself.

Just checked, it seems to be still there, and exposed via xrandr, see the --panning option in xrandr manpage. So you should be able to somewhat dynamically resize the virtual desktop used via xrandr nowadays. The maximum virtual desktop size supported is determined by your graphics card - so if you'd want that some infinity thing you'd have to do that yourself and just throw a small part of the screen in the graphics buffer for rendering.

The bit where you have a small view on a large virtual display exists in xorg (I assume it is still there - when I used that it was XFree86).

You'd configure a virtual screen with whatever resolution you want, and your physical resolution generates a view on that which is moving with the mouse focus. I used to run a 1200x1600 desktop on a 640x480 screen until my girlfriend said she got sick watching me and bought me a large screen.

Might be useful if you quickly want to prototype the general idea.

Hinter dem Kreis wird ein Sechskant sein.