Actually… Glass has a pretty stable base and consistent month-over-month growth. It has a sustainable business model, has been profitable since day 1, and is immune to investor pressure (it has none). I think it’ll be fine.
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)
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.
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.
When flying with Iceland Air a couple of months ago (AMS -> NYC), I was surprised how incredibly smooth the whole check-in experience was. I thought I would get into trouble, because I was carrying both a backpack and a guitar (MONO Vertigo softcase), but literally nobody asked me about it.
Don't get me wrong, I totally agree with you on the design part.
But what I'm trying to figure out is if design and a REST API are the only 2 things where GoCardless outexecutes competitors. Especially since direct debit clearly isn't something new and there are other players in the field that offer a much broader support for different kinds of payment methods.
I agree that the site doesn't look great, but their platform works pretty good (well, apart from the abysmal SOAP API) and they offer support for lots of different payment methods (including direct debit, in lots of countries). So I truly don't understand why everybody is suddenly getting so excited about direct debit payments?
We're also using Adyen. The support is pretty good, the API/website/documentation/customization options are all terrible. But it's one of the few PSPs that provides support for lots and lots of payment methods (like: VISA, Amex, MC, PayPal, but also a lot of local stuff like iDeal, Mr. Cash, etc.)
Supporting a local payment method (iDeal in our case) is a pretty big deal in our case, since it accounts for +50% of our total revenue. Don't underestimate this if you're planning to launch a European SaaS business!