154 karma · joined April 25, 2008
http://twitter.com/noaheverett
noah@ark.fm
The Ark itself fascinates me 1) as a Christian and 2) well, look at my name :)
So I am sad to hear this as it's a great loss to the LXD/LXC community, but I do hope the best for Stéphane and hope he lands somewhere he enjoys!
Thank you Stéphane for what you did for LXD/LXC and for helping me with my dumb newbie questions some years ago :)
[1] https://discuss.linuxcontainers.org
[2] https://ark.fm
No gotchas / issues, works well, easy to setup.
I am looking forward to the Direct IO speed improvements for NVMe drives with https://github.com/openzfs/zfs/pull/10018
edit: one thing I forgot to mention is, when creating your pool make sure to import your drives by ID (zpool import -d /dev/disk/by-id/ <poolname>) instead of name in case name assignments change somehow [1]
[1] https://superuser.com/questions/1732532/zfs-disk-drive-lette...
Regarding distributed protocols: I am interested/watching those, especially the domain based handles, to see if there is a way to integrate as Glue already supports custom domains. Short answer: Yes, I'm watching to see if there are ways that fit Glue's use-case to tap into those protocols.
Glue is one app in an ecosystem of apps I'm working on under Ark (https://ark.fm): Pingly: email / calendar / team chat, Glue: social networking / blogging and a third in progress. I haven't really said what Ark is going to be as what connects all these apps is still in works and honestly is evolving as I go :)
Thank you again for your comment, cheers
Timlines/activity are built from the RDBMS and served from Redis as a cache. New posts are added to the cache directly as well so only needs to rebuild if you lose the entire cache which only happens if we need to restart the server. Also not storing full posts in Redis, just IDs, pulling via primary key from DB is very fast.
That same setup was used for a previous app that had a few million user base (don’t remember the concurrent user numbers though) and it ran well with a clear path to scale it up.
More thoughts: build a mobile friendly web app first, you’re gonna need some sort of back-end to run the iOS app anyways and tweaking a web app UI is much quicker than resubmitting iOS builds to the App Store.
At least that’s what my hope/gut tells me.
Our email service runs an image proxy (to hide your IP from email trackers) with probably about 30-50 lines of code in Crystal that's been in production for multiple years and it just works.
Current project (in the cloud hosting space) that will heavily use Crystal for backend management and WASM which was recently introduced into Crystal and is a game changer for our use-case.
Also wrote a command-line tool with it and it feels like I'm cheating at how easy it is to do so.
Coming from the Ruby/Rails world where you have to cap deploy/bundle etc to push to a production server and hoping nothing breaks on dependancies makes Crystal's single binary deploy a breath of fresh air...not to mention the performance. We run our own hardware so being able to (eventually once we've moved over fully to Crystal) run the same workloads on LESS hardware with electric prices spiking is financially attractive.
As you can tell I'm a fan boy. I'm betting heavily on Crystal and going all in with our stack.
Did I mention it is fast?
MySQL has been great for every project I’ve used it in and haven’t had any issues. Largest app we used it in was Twitpic which handled high query traffic and along with the built-in replication, it was easy to use. We had replication lag on spinning disks (this was 2009) but switching to SSDs fixed it. Backups with xtrabackup from Percona is a key piece though for taking incremental or full DB backups.
I think back-in-the-day, PG didn’t have replication built-in and that always kept me using MySQL, but I’ve honestly never understood the bad rap MySQL got in years previous as I’ve never run into any of the described issues and it has been rock solid for me in apps of all sizes.
My own project Glue[1] is taking a stab at this segment so I have vested interest in this space. Trying to marry all the various content types into a single UI experience has been a fun challenge (short text, audio, quotes, code snippets, blogs).
We will see...
I personally wish issues weren't auto-closed as it can give the wrong (i.e. feature is dead) impression, however I know popular OSS maintainers get a TON of issue requests and are doing a work of love.
So, thank you OSS maintainers, you the real MVP.
P.S. For those interested, the issue[1] is NVMe performance for OpenZFS[2]
Disclaimer: I run Pingly [1] an email hosting service, but ironically our signups are turned off at the moment due to a botnet that hits us with fake accounts to send spam that I'm working to mitigate completely.
Shameless plug: I launched Glue this year which succinctly put is like Twitter and Medium had a baby [1]. Glue has your standard microblogging features, but you can "expand" into a full blog post if you want [2]. I specifically wanted to tackle the melding of a microblogging timeline, long form writing (blogs) and the ability to use your own domain if you wish.
Disclaimer: Hopefully I'm remembering correctly, it's been a while!
Long story long, I basically ended up giving Twitpic to Twitter (I wanted the photos to live on). We were already feeling the squeeze from their own native image feature plus some other compounding events like Google Adsense banning us out-of-the-blue with no recourse that really affected our margins [Hey Google, you still owe us $100k+ ;)].
It was one of the best, most educating times of my life. Just thankful I had that opportunity to run Twitpic for those years, God blessed me.
The End.
P.S. I'm still tinkering https://ark.fm
Reminds me that I bought gopher.io years ago for a project that never came to be. Figured it would be suited for something Go related…hey Google it’s for sale ;)
Circles looks cool as decentralized and E2E are fascinating to me. Glue doesn't have a whole lot in common with Mastadon, but similar microblogging features I believe.
Hit me up sometime, would like to hear more about your project. - noah@ark.fm
I ran my previous startup (Twitpic) completely on ads and it wasn't an enjoyable experience from the business side. It also does not (usually) align with the user's best interest. Ad business models requires attention to feed it, which in turn requires social media companies to build features to get as many eye balls for as long as they can on their app.
I also don't think paid only is the answer either for most cases. Some are ok with seeing ads in exchange to not have to pay to use. I'm curious to see if there is a balance that can be struck with services offering both options.
Brave's new search engine[2] is another example saying they will offer a paid option in the future. I used their beta and it's solid. I'd be willing to pay for it to be free of Google and help sustain it.
[1] https://glue.im/glue/glue-a-social-network-that-respects-you...