HN user saulrh mentioned that the list of requirements "does not seem incredibly unusual" for enterprise setups with AMT on.
Pre-Meltdown/Spectre this was 2017's "big deal" re:Intel; nearly all of the varying degrees of paranoia in the previous discusson seem a lot more reasonable with the benefit of hindsight. (If any more AMT info has become available thanks to Meltdown/Spectre-enhanced reverse engineering I would appreciate a heads-up; example vs SGX: https://github.com/lsds/spectre-attack-sgx)
>perlgod: I've spent years tweaking my mail server setup (Postfix, Dovecot, RSPAMD, LDAP...) and did a full writeup a few months ago. I've used other guides online but found most of the rest lacking on details
>opie34: A friend and I put together a free dynamic DNS service [1] offering cool custom domains aimed at the Raspberry Pi community (and similar hardware hackers.)
It's not strictly a hardware project, but it's a crucial building block for any network-enabled Raspberry Pi project, and we'd love your feedback.
I wish there was even the tiniest bit of public accountability! Even user profile totals of upvotes, downvotes, comments, and flags would be a usable signal. Maybe one of the perks of being a YC company is seeing which accounts downvoted yours... ;)
My perspective grows stronger every time someone close to me dies: the true value in photos is the faces.
As a tech person, that is where I try to maximize my pixel budget.
I actually prefer candid home video infinitely more -- most pictures on social networks are as authentic as pornography stills.
Is there any phone app that purposely records video in the background without turning on the screen? I wouldn't care as much if people holding up their phones weren't shining back at me. I assume this is possible with audio, though concert audio is usually way too loud to record on a phone without additional equipment.
I believe this may not even be possible due to privacy issues, hidden cameras / recording without consent is enough of a problem already!
>How did people do that before there were cell phones?
Trust the babysitter to make wise choices. This is actully really tough as cell phones end up lowering the standard expected of babysitters, like the whole GPS/map thing.
>seniorsassycat: I don't understand why AWS released Go support instead of binary support and I don't understand why they chose to rely on go's net/rpc [...] which encodes objects using Go's special [gobs] binary format
I don't really see how replication/HA is an issue in this setup beyond normal file system replication/HA (which seems to be a solved "spend money on NAS" problem in the enterprise world). If your filesystem isn't reliable / delivering what's needed then you're gonna have a bad time no matter the storage approach; I doubt some unusual option is involved though it would be cool to be proven wrong.
The only time the filesystem could even potentially have read/write conflicts (assuming 1-to-1 correlation between devices writing to files) is when querying. I did wind up muddling the terminology in the interest of jumping to the actual problem.
A secure wallet is not super helpful if immediately cashing out (to fiat), right?
A legitimate, soup-to-nuts "turn one email into $___ in cash" walkthrough (perhaps the beginnings of which is below, though I can't personally vouch for it) would do well!
(Search "2. Stellar" [no quotes] twice; does anyone know how to link directly on Medium? This piece focuses more on breadth than depth, covering multiple cryptocurrencies. The only useful Stellar info there seems to be https://launch.stellar.org/#/login)
>swanson: Related to the Coinbase/insider trading noise around BCH a few weeks ago, it seems strange for Stripe to plug other alt-coins (OMG, Stellar, etc) in the post as things they view as "promising" and "imagine enabling support for". I don't think it's illegal nor unethical personally, but it is such a dicey topic that I'm surprised to see someone writing without a mountain of disclaimers on an official Stripe communication channel
>>ChristianBundy: FYI, Stripe has been very transparent in the fact that they believe (and have pumped millions of dollars into) Stellar
>the SQLite packaged with Android is being upgraded to version
3.6.22 in Android 2.2. I think that the SQLite database corruption bug linked in
comment 451 has been fixed in Android 2.2. So _if_ that's what's causing the text
message database corruption and deletion, then this bug will probably be fixed in
Android 2.2
>Statically link your application against SQLite 3.6.23 instead of
using the SQLite 3.5.9 that is found on Android. The bug you are
hitting was fixed in SQLite 3.6.2
https://news.ycombinator.com/item?id=16238937