I was quite excited to try this when Fujifilm first announced it, but then immediately dissapointed when I found out it does not support the x-t30.
44 karma · joined July 29, 2019
I'll have to look at the benefits of that over Netlify, too.
I've used GCS before and I agree it's not easy/hard, but certainly not as simple as Netlify.
> I would be interesting to have a matrix of supported features on different platforms. And how deployment compares to Nginx, letsencrypt, git.
That would be useful, especially now that there are more and more options out there. I've seen benchmark comparisons but features would be more useful in my opinion, unless the speed is really poor.
Perhaps I've been spoiled by services like Netlify. I'd be interested to know what the benefits are of using DO's service over free alternatives.
I have vivid memories of making websites during secondary school. First for free on Geocities and then later on my first paid hosting (Lycos if I recall correctly) so that I could host my PHP projects. At some point I started making websites and animations in Macromedia Flash and those glassy buttons easy but cool to make at the time.
I admit it would be useful on my team too, I'll have a think about the best way to implement it.
>Either way, I've submitted this for a security review
I appreciate it, thanks!
I decided on a subscription to help support the server costs and continue development. I do appreciate that not everyone likes subscriptions and I think that has hindered traction somewhat.
I send out automated emails a week before renewals to remind people about the subscription, and of course I'm happy to refund anyone that mistakenly rolls over.
> 1. Are you open to letting people pay once, without setting up a subscription? More of a year-long license model?
I'd love to do this but both my infrastucture and payment system aren't really set up to do so. I'm more likely to do a limited run one time cost (Pay once and access forever), but I haven't fully decided on that yet.
> 2. Do you have any infrastructure setup for teams? I could much easier justify putting this on my AMEX and allowing my entire team access.
Not currently but I do have some ideas in the works. Either sharing snippets between users, or a public directory where the community can share useful snippets. A team subscription also does sound like a good idea, I'll mull it over :).
For now, since it's all synced to the server, your team could all log in with the same account and share access. Not ideal, but it is a work-around!
For anyone wondering, it's called Snipline (https://snipline.io). It has very few users, but the people that do use it tend to reach out to me and it's really nice to see the value that they get out of it.
Getting hearing aids has given me significant relief from tinnitus and if my hearing aid battery dies the tinnitus comes back fairly quickly. It's as if my ear is trying to compensate for the lack of sound.
Of course, there are multiple reasons for tinnitus to occur so your mileage may very, but it's absolutely worth checking out.