131–140 of 226 posts
Earlier quoted context omitted.
If people are lumping in all tech companies in with big tech, we should all be concerned about that.
People who are consciously trying to de-couple from big tech are the same people who are conscious about lock-in effects.
A lot of people want to own their house while too many service/hardware providers are trying to be your landlords.
This is a cool idea but I think having a mandatory subscription killed it for me. It does not even provide an illusion that I can still have my own services intact and running indefinitely no matter what happens to or at the service provider. This is especially crucial when you consider how much of a pain switching email is.
Do I move out of Google just to be dependent on another company that requires a subscription for the illusion of owning my data? On top of that I have to deal with all the hassle that comes with it? I don't think so.
Many people here, including myself, are heavily turned off by the mandatory subscription that costs as much for 2 years as an entire device. However, the service provided as part of the subscription, a static IP address forwarding to your device without terminating the TLS connection is actually cool. For about 30$/year (24$ sounds good), I'd absolutely buy that alone, since that's the key to the tag line - truly pri…
Clean IPv4 + IPv6 address, Reverse DNS, unblocked ports, unfiltered ICMP
It's priced reasonably to keep bad actors out:
We have a $60/year plan in the works, which will be available before the end of this year.
Earlier quoted context omitted.
If the TLS is terminated on the device and all it's using AWS for is a static ip and inbound port for email, that seems pretty harmless.
Seems like a stupid design decision at that point to have a dedicated instance per user. For a pass-through they could multiplex tens of thousands of customers easily onto a single instance.
It's not stupid.
Earlier quoted context omitted.
For IP, you can get a domain adress from namecheap then set up dynamic DNS ( https://www.namecheap.com/support/knowledgebase/article.aspx... ). Maintenance/security.. log in from time to time and run 'apt update && apt upgrade' ?
residential IP addresses are generally blacklisted by email services
Earlier quoted context omitted.
1. Secure boot is supported on Raspberry Pi, just not out-of-the-box. There's plenty of solutions in this field for your respective needs. 2. Raspberry Pi supports LUKS perfectly fine, making disk encryption a snap.
Would love to see what documentation you have around both of these points. I have not seen anything that indicates the SoC for the Pi supports eFuse or any other OTP storage.
I more personally lament the creeping buzzword-ification of "personal server" messaging. There's a burgeoning array of different underlying meanings for the terms "personal", "server", "own your own data", "full privacy", etc. It seems likely that terms like these will continue grow in popularity with adwords searches, so you can expect more companies and products to use this claim to sell a particular architecture with a potentially large set of technical trade-offs between various ideas of "server ownership".
Ultimately where I think the general trend towards "server ownership" will land, like all new important technologies as they get integrated into the rest of society, is with a company/product that best navigates a rather tricky balance between the affirmed value of "ownership" (et cetera) vs the individual's willingness to get their hands dirty with a slightly more sophisticated, but more robust understanding of the underlying architecture.
Put simply; the less the "end-user" knows about the fundamentals of their personal computing stack, the less capable they'll be when it comes time to reason about the right decisions for them regarding privacy, security, modularity, longevity, and the other various desirable properties of a personal computing stack that truly meets their needs (as parents, citizens, businesspeople, etc). The victor of this trend will be the one that best facilitates true "end-user" empowerment, with minimal gotchas.
Earlier quoted context omitted.
I'm not sure where you got that the device would be bricked. Can you point me to where you saw this? All data is accessible on local ports on the LAN, with or without the subscription service.
The subscription not being optional ("We don't make the subscription optional at this time", https://news.ycombinator.com/item?id=28351035 ), with unspecified consequences of not having one. One thing I definitely gather from that comment is that E-Mails wouldn't work, which appears to be the main selling point of the device.
If a customer doesn't want a subscription, they can still use the Helm on their local network and get access to all their data. Running without a subscription is not something we currently support because of a lot of variables that can prevent email from working consistently, creating a heavy support burden (which is costly) along with bad customer experiences. It's best for people wary of a subscription to go down the DIY path (and we end up with a lot of DIY switchers once they realize how much effort it is).
Earlier quoted context omitted.
Would love to see what documentation you have around both of these points. I have not seen anything that indicates the SoC for the Pi supports eFuse or any other OTP storage.
Not OP, but this looks promising after a little searching: https://askubuntu.com/questions/599825/yubikey-two-factor-au...