Instead of another social network, it’s a bundle of small, practical community tools under one umbrella, combining of the shelf-software with purpose-built projects of our own.

Our current areas of focus are

- help! a neighbor-to-neighbor help board (rides, errands, PC help, garden/handwork)

- hubs! for shared spaces / tool-sharing / events / social hubs

Right now I’m building the integration surface (claims, roles, provisioning), polishing onboarding, and trying to design help!/hubs! so they’re useful even with low activity.

If anyone’s done (hyper-)local community platforms: I’d love to hear what actually drove adoption and what did not work out for you.

I'm building ourrhythm.de, a privacy first intimacy tracker spawned from a drunken thought: people buy those erotic advent calendars with 24 toys — do they actually keep up with all 24 rounds? It turned into a site idea.

I think the original use case is not to know whether a dining hall is occupied at all but about how occupied it is (and if he should go to lunch now or wait another 20 minutes).

It's gut wrenching that I am just a CT scan away to being in the same (somewhat comparable) situation.

I shouldn't compare fates and still my mind wanders around the topic every time.

The facts they both present in a scientific manner (like remission rates) scare me to my bone. I cannot fathom what he and his loved ones are going through and that makes it even clearer what I have burdened on my wife, children and family.

I know this comment is ultimately me shouting "please let us both live" with many words and maybe this is me being a self serving asshole, maybe it is that. I don't know anymore.

I would love to offer the promise that everything is going to be alright but I cannot. I am just scared as hell and somehow I needed to get this out.

From what I could find the 2009 Protection version (then called high security) was more around 400k-450k€. A standard model 7 runs from ~115k up to ~145k€.

Disclaimer: I don't have primary knowledge of this, and it's second-hand information from someone I trust personally. As with all such information, grain of salt recommended.

The main benefits for the customer is physical security, the device is built to be savely stored in a safe or at a bank vault when not in use.

It is built in a way which give total control over the keys to the customer so that our support teams managing the services never have to touch a private key and is easy enough to be used by a non-technical employee of our customers.

For the same audience I'm working on replacing the traditional multi-hub-and-spoke VPN we've built over the last few years (around 500 Hubs in Germany + Spokes) with a true End to end encrypted Mesh system with around 2000 wireguard nodes.

Lastly this is something I hope to do in the near future, building out the first cloud strategy, team, infrastucture and procedures for said sports retailer.

Oh I built a Powershell Wrapper around some parts of the Dynect API and a mostly complete wrapper around the tailscale API which is not widely used but made an impacton a handful of people.

At the start of the pandemic I ran a couple of Jitsi Meet instances for people to connect with their close-ones which was used by a low five figur number of people.

I started a project where we 3d printed a few thousand earsavers for wearing A FFP2 mask for for our local school. I think we at least got two school fully supplied and about a thousand pieces where donated to the hospital that saved my life.

Most of users want a way to find / lock / remotely wipe their 1000$ phone in case it gets lost or stolen.

No it's not a solution, Netflix already heavily uses IPv6 and most sane v6 endpoints will not be NATed. Maybe they could use v6 Subnets as an Identifier but this would be wonky at best.

This would be a support ticket pandemonium since there are more than enough providers with dynamic IP adressing on v4 and v6.

But to be honest I think they might not need all that, more likely is they use some sort of device ID the modern Smart TVs already have Baked in or build some hash of their own with some device specific identifier (size, resolution, manufactuter, User Agent).

The article and information out there seems to imply they're primarily targeting TVs and devices that are used with TVs (SetTopBoxes, AppleTV, Firetv, Roku et al). So it makes no sense to use a device type unspecific Identifier like the IP in any way

It feels a bit like wanting a surprise gift for Christmas (contrary to something you wished to get) but then being upset because you did not get what you wished for...

I would love, to hear your theories maybe this willhelp explore that feeling a bit more

As one sibling comment - I too have noticed this: I can remember friends of my parents showing by having a good time completely spontaneously. I liked it very much.

On the other hand I’m one of those people who get irrationally upset by random visits especially when it’s from family.

I guess that’s one reason why it’s so hard for me to be happy.

I am in no way qualified to trample on your parade but two things came to my mind that pinch a personal nerve of mine and I would really like to have alleviated by you or the folks who know that stuff:

- if your Goal was "secure by default", why did you allow passwords in the first place? Following Caddys recipe would be more like SSH-Keys only, wouldn't it? Is there a reason other than compatibility?

- In that same avenue? Why allow such a thing as downloading authorized keys from a third party? Domain takeovers or account compromises on say Github are a thing - so again while it may be a nice usability aspect isn't that contrary to the secure by default pradigm?

Again thank you for your work and congratulations on the project - those above are just honest questions that came to mind which I would really like to be educated on

CertPinning and CT will go a long way, but do you know that all your software components (not only your webbrowser) use these effectively?

What is about credential snagging with tools like responder? Maybe your client will freely send a set of credentials down the line because of corporate shenanigans.

Depending on the protocol used it might be trivial for a MITM to prevent a secure connection altogether and transparently downgrade your connection to a less secure method (ie Filtering STARTTLS).

That is definitely in the realm of the server being tasked with delivering your mail.

In traditional desktop Mail clients the Outbox is a local folder and stores Mail that hasn't been delivered to the Server tasked with sending out the mail.

The retry method mentioned here is about a Mail that has been delivered to the outgoing mailserver which in turn may have trouble reaching the destination server

I will happily give 15-20% tips for great service, but that is a additional and is given freely - not what is to be expected.

There really isn't something new here other than a fancy name - or I am not seeing the point.