35 karma · joined February 12, 2014
> Last month [...]
> At the same time [...]
> That was over 6 months ago [...]
From when?!? What good is a relative timeline of events and your "current" thinking without a timestamp?
Digging though the source, it looks like this is from a few days ago.. "created_at":"2024-02-14T01:45:45.254Z"
/rant
Still, it's a useful device while traveling – nice to be able to plop a decent multi-monitor setup out of a backpack. My model also has a micro HDMI port (and an internal battery) which can be handy if you need a temporary screen for a Raspberry Pi or a machine that usually runs headless.
> The model is able to reference up to approximately 3000 words (or 4000 tokens) from the current conversation - any information beyond that is not stored. (https://help.openai.com/en/articles/6787051-does-chatgpt-rem...)
So if you overflow that it'll loose context.
The files don't need to be valid, just have the extension you want to associate, so you can do something like `touch _.mp3 _.mp4 _.m4a _.mkv` then select those files and set them all at once.
It has a lot of personal preferences baked in but you get the idea.
Last December I got serious about the problem and went looking for solutions. Specifically, I wanted to be able to route email to my existing mailbox, have unlimited aliases, operate the whole thing via and API and not pay much – this is for personal use after all.
There are stacks of businesses that will give you email forwarding on a domain but I found most of them either only relay messages using a webhook, rather than forwarding the actual email (SparkPost, SendGrid, Postmark, Mailchimp) or are expensive, often with the email forwarding service being a feature point of some premium plan or having arbitrary limits (Mailgun $35/mth, MailSlurp $21/mth, ImprovMX $9/mth for 100 domains x 100 aliases, MailerSend $25/mth).
The standout at the time was Forward Email (https://forwardemail.net) who offer unlimited domains/aliases/messages for $3/mth. They're privacy focused, open source and have some nice features like regex aliases with substitution in the forward address which is cool. (So you can have rules like `/^(domains|webmaster|admin|root)$/@example.com` forwarding to `$1@example.net` and `me+$1@example.com.au`)
I now have a bash script that wraps the Forward Email API. It takes the url of the page that's asking for an email (to be logged against the new alias) and an abbreviation for the service, and it spits out a new alias, with the abbreviation and a random component, that looks nothing like my real address. I registered a domain specifically for email which is short, easy to type, and a .com (so even the harshest/most broken form validation will accept my aliases). New aliases are immediately forward to my Google mailbox and still include the service abbreviation as a "+" alias, so I can still see at a glance who sent the message. (For example an alias for Hacker News might be `hn.u2la1@example.com` which would forward to my mailbox as `me+hn@example.net`). Any mail sent to a non-alias is silently black-holed.
I've been using this for all new accounts for a few months and it's working well for me. Forward Email isn't perfect but they're cheap and seem trustworthy. Support (which I used once) was great though I'm pretty sure the entire service is a one man band so arguably the bus factor is high. The docs aren't fantastic but has been working flawlessly since I got it running.
After I had this all setup I stumbled on another service, Hanami (https://hanami.run), which would also probably work for me ($2/month for 4 domains, unlimited aliases, regex routing). And now of course Cloudflare's solution is publicly available (https://developers.cloudflare.com/email-routing). If I was starting from scratch I'd definitely consider those options.
Apparently Google had delisted the authors site as duplicate content because the content was originally posted elsewhere, blocking me from finding the story when I'd searched previously.
https://scifi.stackexchange.com/questions/tagged/story-ident...
Personally, I'm hanging out for a 5120x2880 display larger than 27". We've had 27" 5120x2880 displays for 6 or 7 years now, you'd think someone would have taken that res to a larger panel by now. But nope, still waiting.
What confuses me is that, surely you could achieve the same outcome using software with very little overhead. Doing so saves all the manufacturing and distribution costs so you'd expect it would be a more profitable approach. So why the stick? Is the filtering overhead large enough to justify a dedicated co-processor or is the form factor used here really a placebo? In the way that a heavier wrist watch feels more valuable, does plugging a physical device into your computer to protect it/make it faster, _feel_ more effective than installing software that does the same job?
Pre-Touch Bar, of course...
If you're building a botnet you don't need to crack any specific machine so you can distribute your attempts across more hosts. Eg. rather than hitting one machines with 1,000 pwords/sec you target 1,000 machines at 1 pword/sec each (or whatever rate you're limited too). There's no shortage of badly configured routers.