Mail-In-a-Box (MIAB)[1] comes with a built in nameserver. I think you may use it as a standalone DNS even for the domain names whose email is not managed by MIAB. Not sure about any benefit of doing it this way though.
I can only give you a datapoint but unfortunately no advice
1. I never discovered any movie on IMDB. I go to IMDB to find trivia, cast or some other fact about a movie that I somehow already knew of.
2. My interest in an open source project will not be influenced by its popularity or any other metrics but purely by what it means to me. I submitted my first PR to an open source project not because it is popular but because it lacked something I needed.
P.S. Thanks to all the nice people who generously contribute to OSS and offer their work for free. Hats off and respect.
I discovered gazillions of movies on Imdb, actually it's my primary resource. Through either the "more like this" carousel on a movie, or by filtered search (eg. best rated 50s comedy with at least 15k reviews).
The best resource for me on IMDb is definitely just the lists of "Top 250 Movies of all Time"[1] or the "Top 50 $GENRE Movies of All Time" [2].
@OP: Maybe just finding a way to curate the most popular open source libraries into lists per language, framework, etc would be helpful? For example, for me I'm not particularly interested in all open source projects, but I'm really interested in Django stuff. Hence why I love looking at the awesome-django curated list [3]. Maybe an application to just rank all packages for a given ecosystem? Just spitballing.
I have to read the reviews; I do that for restaurants as well; the ratings don’t mean so much to me personally; people often up and down vote on a whim and emotion (just in a bad mood) so reading why they (particularly) didn’t like something tells me if I would like it.
I always take movie reviews with a grain of salt depending on the genre. Horror & Comedy ALWAYS get the harshest critics. Horror especially, but honestly unless the IMDB is above a 7 or Rotten Tomatos gives it like 85-100 I leave it up to my own personal judgement. I love watching just about anything if the story is interesting (and I find just about anything & everything interesting so that doesn't leave much off the table)... I've gotten off topic though lol.
TLDR you can't always trust reviews (or peoples tastes). If the Trailer & synopsis hooks ya why not give it a shot when you can always just stop watching if it doesn't pan out.
---
Now as far as an IMDB for open source, I'd say maybe even go so far as doing a Letterboxd type deal? When it comes to opensource projects it always helps to hear what the users are saying about it.
- I did discover interesting movies on IMDB. It was more by chance though, while looking up info on known movies.
- Popularity of a piece of OSS may be important when choosing to use it for an org. Something alive and widely used has better chances of survival in the future, and/or speed of reaction to security incidents.
That said, I agree that IMDB is not what I'd like the directory of OSS to resemble. I'd rather go after imitating tvtropes.
Like the other reply, I also find movies in IMDB and it is also my "primary" source, though I use it differently: I generally want to watch movies in clusters of who's involved, so I will watch a movie I ended up thinking was amazing and then want to see more movies by the same director or starring the same actors, etc.
Interesting. I use IMDB as a filter, for score and synopsis. I rarely find new movies there (find recommendations elsewhere), but I basically filter anything out that sits below a 7, or include anything 6+ if it's in a genre I happen to like. I suppose I could use rotten tomatoes for that too.
If you are the owner who foots the bill and has the capability to run your own infra then nothing beats it. If you don't have the capability then cloud throws you the lifeline at a price of course. Pay for it and be happy.
If you are the guy who runs/manages the infra for someone: then there is no point in saving dollars. You peddle Kubernetes and go to the kubecon and post all about it on linkedin and establish yourself as a kubernetes expert. When the owner of current gig goes under, you will have a bunch of job offers to pick from.
Besides, kubernetes solves a problem very elegantly that most companies do not have. Not everyone is google and running apps on web scale with an expectation of 99.99% uptime...
Your site looks really nice and addresses a real problem. Are you targeting US only remote roles? If not then including any domicile or timezone restrictions in job snippets may be helpful.
Also thanks for providing the feed.
Congrats Nico. Came here to tell you about the HN API (https://github.com/HackerNews/API) but I see cheesehead beat me to it.
Using the API it is much easier to pick up the latest thread each month and setup a cron job.
Yes, I am building an application tracking system(ATS) that also includes a job board. Among other sources, I used HN to populate the job board.
My project is not open source, but I am happy to share the HN scraping code with you if you like. My email is in my profile.
Not until it works. But when it doesn't you have an office full of people waiting for someone to fix that broken build server. In terms of lost productivity this disaster is very expensive. Over the years I have suffered only three hardware disasters. One was a NAS+backup screwup but other two were both related to build servers...
This reminds me. It must have been 2009ish. I was at Microsoft. Part of the code I was responsible for ran on the Windows build servers. This code was triggering a kernel bug in the Windows registry. The only way I knew how to reproduce it was by building Windows. Because thousands of Windows builds happened per day, maybe 1 of them would hit it every 1-3 days.
The way I got it in a kernel debugger was to constantly run the problematic race condition inside a VM, when it detected that it hadn't hit, it would roll back the VM to a save state of the code already running in progress ... Took an overnight run to hit it on a machine in the office.
All that said, I'd still say it's not very expensive to run a build machine.
I would do exactly what you have done here if I were the dev of the said app. But with the luxury of being an outsider, a user has expressed an inconvenience and it seems to make sense, then if I were to be the dev of the app here, wouldn't I go and create the ticket in whatever system with a link to this post instead of asking the user of the app to follow the red tape? I know there are places where this is not incentivised so this is a question for your org and not for you.
I see what you're saying and for simple features I agree
However Without the OP creating the ticket there can be no feedback look on the feature.
If i wanted it tested for their usecase, there input and confirmation on if its what they wanted and improvements for the workflow etc..
If I base the whole feature on this comment it could end up only doing half a job. Id rather have that communication loop open!
I tend to agree. As an open source dev myself, I avoid asking folks to create issues, as it puts a burden on the user. I’ve see some highly respected open source leads so this, and I’m
not faulting them, as I think they’re coming from a good place; it may be a difference of opinion on what’s best practice.
Not OP. My take is that if the requester can’t be bothered to create a GH issue, it’s likely that this isn’t really a problem for them. An annoyance possibly but has not risen to “pain” levels.
[1] https://mailinabox.email