ADHD af. I regret most of the things I say.
🇪🇺🏳️🌈 #BLM
I'm in denial that @hkt3030.neocities.org is gone.
I'm in denial that @hkt3030.neocities.org is gone.
Then I look up and see this and question my fundamental understanding of the English language.
Then I look up and see this and question my fundamental understanding of the English language.
I tried to install the Yammer app on it circa 2010 (pre-Microsoft ownership) and it became instantly, permanently bricked. 🪦
I tried to install the Yammer app on it circa 2010 (pre-Microsoft ownership) and it became instantly, permanently bricked. 🪦
in retrospect, it's probably a stolen BlackBerry 8820.
Judging by the date, it thinks it's 2007. And I've no idea what the password might be.
in retrospect, it's probably a stolen BlackBerry 8820.
Judging by the date, it thinks it's 2007. And I've no idea what the password might be.
I should probably send them off to be recycled. I enjoyed taking the BlackBerry 8320 apart (not pictured), but there's probably not a lot I can do with the more modern phones.
I should probably send them off to be recycled. I enjoyed taking the BlackBerry 8320 apart (not pictured), but there's probably not a lot I can do with the more modern phones.
None of those using USB micro charging show signs of life. However, these older phones will turn on:
- USB mini-B charging (BlackBerry)
- Proprietary Samsung charger (SGH G600)
I still miss a good integrated hardware keyboard.
None of those using USB micro charging show signs of life. However, these older phones will turn on:
- USB mini-B charging (BlackBerry)
- Proprietary Samsung charger (SGH G600)
I still miss a good integrated hardware keyboard.
text-wrap: nowrap
font-size: 0.8rem;
min-width: fit-content;
}
text-wrap: nowrap
font-size: 0.8rem;
min-width: fit-content;
}
And whilst I enjoy Garage Band on my 12" iPad, I too suffer from fat fingers. Plus, it loses something with the absence of the physical response to touch of the keys!
And whilst I enjoy Garage Band on my 12" iPad, I too suffer from fat fingers. Plus, it loses something with the absence of the physical response to touch of the keys!
Part of my frustration at them is actually a fundamental frustration with the underlying HTML date input.
Behold, values using '/' are not appropriately parsed.
Values using "-" are parsed and displayed with "/".
🤡
Part of my frustration at them is actually a fundamental frustration with the underlying HTML date input.
Behold, values using '/' are not appropriately parsed.
Values using "-" are parsed and displayed with "/".
🤡
Basic interactions like escaping out of the calendar and navigation by keyboard probably come under the "not fully compatible with accessibility" disclaimer.
I see no reason to use this over a standard html input at the moment.
Basic interactions like escaping out of the calendar and navigation by keyboard probably come under the "not fully compatible with accessibility" disclaimer.
I see no reason to use this over a standard html input at the moment.
Temporality as a whole is a nightmare.
FluentUI for Blazor docs go further: when you type a / into the picker, naturally what you want is to enter a search command.
It displays as dd/mm/yyyy but certain cases expect dd-mm-yyyy input. Others expect nothing. Naturally.
Temporality as a whole is a nightmare.
FluentUI for Blazor docs go further: when you type a / into the picker, naturally what you want is to enter a search command.
It displays as dd/mm/yyyy but certain cases expect dd-mm-yyyy input. Others expect nothing. Naturally.