xb95
Usually people follow the network -- find one person that's interesting, see who they talk to, and go from there.
Another approach is to see what "interests" are popular and click through to see who shares those/is active: https://www.dreamwidth.org/interests?view=popular
But, TBH, there's a lot of happenstance and serendipity (or are those the same).
Pretty cool to see my project hit the front page of HN, but definitely a bit of a /shrug moment on the subject itself. "Facebook gonna Facebook" I think is approximately how we feel about this.
I know here on HN we're used to hearing stories about scrappy startups trying to carve a piece of the pie big enough to exit on, but that is pretty much the exact opposite of what Dreamwidth is. Our motivations are very different, so this FB block is mostly a curiosity to us.
Dreamwidth is a small, neighborhood corner store kind of site. We're run by a couple of dedicated part-time staff (who have other jobs/responsibilities in life -- I personally work for Discord!) and a cadre of amazing volunteers who donate of their time and energy to make a nice little corner of the Internet that isn't driven by the cycle of VC and growth and user monetization.
We do not have any goals around growth, we don't advertise, and we ultimately don't care that much what the other platforms do. Our goal is to give people a stable home where they don't have to worry about their data being sold, their writing being monetized. Users choose to pay us for a few more advanced features (like full text search), and we support ourselves entirely off of that.
We are home to a large group of online roleplayers, Hugo Award winning fiction writers, Linux kernel developers, parents, security researchers, artists, activists, recipe bloggers, educators, and everything in between and around the edges who would rather work with a service owned and run by people who are motivated by something other than get-big-and-exit. Large communities of online roleplayers who get together and build whole worlds on Dreamwidth, who tell stories together. I'm constantly impressed by the creativity of our community.
Anyway, it's super cool to see Dreamwidth on the home page here. It's been my side project for over a decade now, and I'm quite proud of it. Even if modernizing a 20+ year old Perl project is a hellish undertaking at the best of times... but we keep going. :)
Actually we didn't update the reference to Cassandra in the article -- the read states workload is now on Scylla too, as of last week. ;)
We'll be writing up a blog post on our migration with Scylla at some point in the next few months, but we've been super happy with it. I replaced our TokuMX cluster with it and it's faster, more reliable, _and_ cheaper (including the support contract). Pretty great for us.
Anyway, Choopa is a common source of DDoS in our reports, so I can corroborate the OP's comment to some degree. They aren't the largest we see, but they're in the top 10 sources for us.
The Fortnite Official server has exceeded 100,000 concurrent users, Discord itself is way past that 5M concurrent number, we're now using Rust in certain places to make Elixir go faster, we've built a general purpose replacement to Process.monitor that scales a whole truckload more that we're open sourcing next week at Code BEAM SF... the list goes on.
There's a lot of fun stuff going on to try to make this system even more efficient and reliable, there's a lot to do still. We run everything on a very small engineering team (there are 4 fulltime engineers on the core infrastructure, only about 40 engineers in the whole company) and we're always looking for a few more. Feel free to reach out to me (zorkian#0001 on Discord) if this blog post sounds up your alley!
For General Aviation safety, read the Joseph T. Nall report: https://www.aopa.org/-/media/files/aopa/home/training-and-sa...
To summarize, helicopters and airplanes enjoy a reasonably similar lethality. Approximately 15-20% of accidents (total) are fatal to one or more occupants. However, if you break it down to fatal-accidents-per-100,000-hours then helicopters are worse (1.5 vs 1.0) at least in 2013.
When it comes to general aviation safety, however, the far and away most important factor is the pilot. Unless you get damned unlucky, the vast majority of accidents are either avoidable or survivable if the pilot doesn't do something wrong. In helicopters, a controlled autorotation will be survivable most of the time. In airplanes, a controlled forced landing is the same.
Of course, you can have your cake and eat it too -- I recently purchased a Cirrus SR22-TN (airplane) which has a Ballistic Recovery System aka a parachute. If anything goes wrong you can pull the chute and the entire airplane will descend to the ground. :-)
Yes! Dreamwidth is a fork of the old LiveJournal code that is still being developed by a small team of folks who would rather see a small site run in an open, transparent fashion than be beholden to large corporate interests and the whims of monetization.
We're a very happy little family and it's always exciting to see Dreamwidth links end up on HN. :)
I ran into the same sort of thing you did re: Delphi jobs. I was pretty sad, honestly, having started in the original Delphi days (version 1!) and going to 6 I had gotten pretty good at it...
In random point, I (while a dev) was a member of ASCN. I was there the day Steve was unveiled and the day it died in C9N-CC. We lost to BoB "fairly" (everybody suffered from the state of the servers in those days, so maybe it was "CCP won"). There was some bad blood, of course; I'm still a little bitter about Steve's death. But the cookies crumbled and that was that.
Ultimately: I don't think t20's actions contributed substantially either way to BoB's ascendancy. Organization, good play, and a willingness to use all avenues (within the game) turned out to be pretty successful.
(Also... no longer employed by CCP, but still play EVE. 12 years later... still the best game I've ever touched.)
Unrelated, TypeRacer is amazing. We had a bunch of contests at my last job and they ended up making a trophy because I was the King of Speed. It was pretty fun. So, thank you!
Edit: Bias alert; I work for Dropbox on our infrastructure team. I'm just curious about that particular incident, since it predates me and I'm always curious about these things.
I echo what they said in that post, though: don't prematurely optimize. If you find you have tons of objects and need the RAM or you're actually paying a premium for hash accesses, then fields can save you some effort... but if you've a small use case, don't bother.
All joking aside, this could be interesting. It makes me think of that service that existed for a while where you could ask a question of a topic area, and it would send an IM to people and ask them to answer it. I forget what it was called, but I used it for a little while.
The payment/HIPAA compliance aspect are pretty interesting, too. I would easily throw $50 at a 10 minute consult with a doctor instead of having to make an appointment and haul myself in to the local clinic. Particularly if said doctor could then fax a prescription for something completely boring but still not OTC to my local pharmacy.
I'm a strong introvert and I find that a few drinks makes me feel like what I suspect an extrovert feels like. Personally, I'd much rather socialize with a few drinks in me; and if there's a large group involved, it's almost mandatory for me to enjoy myself at all!
Dancer, Moose, DBIx::Class (a bit more advanced), Plack/PSGI, etc etc. Not to mention the language changes they've made with 5.10/5.12/5.14/etc (I'm in love with the defined-or operator).
I'd argue that spending 0.01% of revenue on key executive compensation (which is the 'paying executives millions' you talk about) is irrelevant to Wal-Mart overall and how much they can or can't pay their workers. Even if you stripped the executive compensation and gave it to the workers (2.2m of them), you'd only be handing out $30 to each person. That's a few hours of work total, and amortized over a year? Not a factor at all in the grand scheme of things.
...
The article is well worth a read. It's interesting and insightful and discusses more interesting things like business models, target demographics, value-mindedness, etc. I recommend it if you can get it to load. (It was fine for me.)
That said, whiteboards are still usually better for conveying ideas. If you don't understand the problem you're trying to solve or the data structures you need, you might want to start on the board before sitting down to code.
So: kudos for learning an aging and mostly deprecated form of communication. Some folks still do it for hobby (I've lost all skill by this point), and I highly recommend the experience.
If nothing else, find a local ham group and go poke around in late June and see if they're doing anything for field day. It's worth checking out.
set shell=/bin/sh
No more problems with plugins in fish.
I was pretty excited to see what this project was about -- then I saw they were asking for $30,000 in funding to build this and wandered off to make a snarky comment on HackerNews. I don't really want to see this kind of stuff here.
Or at the very least, it should have a subject that says something about funding, etc.
Edited: Also, your "$100/month" quote is pretty fanciful. Who is handing out 32GB with SSDs for that price? I'd really love to know, because the best I've been able to get for a database quality machine (RAID-10 with BBU, SSDs, and lots of RAM) is closer to 10x that.
Even if they are new, though, you never know if it's completely good until you've tested every block on the device. These days most format operations don't actually wipe out the whole disk (takes ages!) so even formatting on a brand new disk won't tell you if it's valid.
That said, the odds of having multiple disk failures on a brand new RAID in 72 hours are pretty low. If that's the case, I'd start to suspect a bad batch of disks and/or bad backplane or other hardware (bad power?) that is causing the hardware to fail.
They then asked the provider to swap the disk. They had a RAID1; it's a common enough setup.
SSDs fail in many of the the same ways as spinning disks, they just add a few more failure cases.