Hey, I really relate to this. I’m not a photographer myself, just a photography enthusiast who happens to co-run a small platform called Glass (https://glass.photo). We built it because we were feeling exactly what you’re describing: the joy of making things getting slowly drained by the systems we’re supposed to share them through.
Glass is our attempt to create something gentler. A calm space for people who love photography. Not performance, not algorithms, not infinite scroll. There are no public metrics, no ads, no dopamine traps. Just photos, shown in full quality, in the order they’re posted, among people who care.
It’s not a viral growth machine, and that’s by design. It’s a small, sustainable, subscription-based community. No investors, no data mining. Just a place that exists because enough people want it to. If that sounds interesting, come check it out. And if not, I still hope you find a way to keep sharing your work. It’s worth the effort, even if the internet makes it hard sometimes.
You could also implement tiering yourself, depending on your workload of course. If you know you're storing objects for long-term archival reasons (or backups), you could opt for using S3 Glacier Instant Retrieval at $0.004/GB.
I am not a doctor nor a physical therapist, but what helped me a lot was focusing on fixing anterior pelvic tilt. If your hip flexors are too tight due to prolonged sitting, there are a couple of things you can do that will combat that:
1. strengthening your abs / core muscles (planks, hollow holds, deadbugs, loaded carries, etc)
2. strengthening your glutes (air squats, lunges, glute bridges, etc)
3. stretching your hip flexors (kneeling hip flexor stretch, couch stretch, 90/90 stretch, etc)
Similar experience for me. I found that many of my aches and pains as I get older are resolved by exercise and stretching. For example, I hurt my lower back in my 20s. Not extremely bad, but bad enough that it still gets sore if my back gets too weak after 20 years. I stretch and strengthen it without using weights, and it eventually gets better. I stopped running for a decade then decided to pick it back up. My knees were sore or hurt mildly initially, but eventually they got strong enough that they got better. Running is also great for strengthening the lower back.
Trial and error. I recommend looking up non-weighted exercise, stretches, and activities that target the body parts you are interested in, and start trying them.
There's a near-infinite amount of not-so-small gotchas when implementing magic links:
- If magic links are the only way to sign in, authentication success rate is now directly tied to your email deliverability rate.
- Single-use tokens (immediately expiring after clicking) can be followed by spam filters, and thus immediately become invalid for the actual user trying to sign in.
- MTAs using greylisting can cause unexpected delays in email delivery.
- If a session audit trail is implemented, malware scanners following links might cause sessions from unexpected locations showing up.
Also, they only work if I have an e-mail client on the device I'm trying to log in from. Otherwise having to transfer this link becomes a burden.
Additionally, even if I do have the e-mail on my device, clicking the link on mobile often opens it up inside some alternative web-view. Thus the session is tied to my e-mail client, not my actual browser.
This wouldn't be a problem if the Magic Link was used only to authenticate your original login session, and not to start a new session wherever it was opened. Like I mention here: https://news.ycombinator.com/item?id=32081608
Great points! The deliverability (and delay) issue is the one I’ve found most challenging. For the others, here are some mitigations I’ve come across:
- instead of single use tokens, set them to expire within 60 mins
- to prevent spam/malware checkers signing in when following the links, have the magic link take you to a page with a sign in button to ‘complete’ the sign in process. And, optionally, add some JS that clicks it for you on page load. This is the same approach used for unsubscribe links.
Amazon Web Services | Solutions Architect | New York, NY | ONSITE
In this role, you'll be helping scale a $10B/year business that's still growing like a startup.
Eager to immerse yourself in the latest technologies in IoT, machine learning, devops, and big data? As a solution architect, you'll get actual hand's on experience with all of these while helping some of the coolest customers in technology today.
Want to contribute to technical communities through thought leadership? AWS Solution Architects regularly present at meetups and conferences, including the flagship re:Invent conference in Las Vegas.
At AWS, you'll be surrounded by some of the best minds in technology and you'll have endless opportunity to learn, grow your skills, and become an expert in cloud computing.
Sound interesting? Please feel free to reach out to me directly at sborsje[at]amazon[dot]com and include HN in the subject.
We actually use syslog-ng + Loggly for distributed Loggly. We partially solve the transaction problem by slapping a request ID on every action that's initiated by a web request. We then carry this request ID from service to service, which gives us the ability to trace exceptions cross-service. It's obviously not the perfect solution, but it has helped us many times when debugging customer-facing 500 exceptions.
We solved the service discovery problem by simply using DNS. Every service runs behind an (internal) Elastic Load Balancer, and we let the load balancer configuration figure out which instance is up and which one is down. Again, not the perfect solution, but it works great for now and is very easy to setup/maintain.
