Hey there everyone!
Some of you might have seen it, this Wednesday, Wayne from DIYorDIE talked about E-Juice Calculators during his stream, and how we finally need something better than ATF or ELR.
While ATF or ELR are mostly good, they're not great. I was hooked by the idea to create something and give back to the community. So I've started looking around for people to get some help, since this project is probably going to be quite big and will need lots of time.
Thankfully, I found u/mixnjuice, who has been working on creating an open flavour API database, and really wants this to happen too.
Now, in order for all this to happen, we want to work close with the community. If everything goes well, the project should be open-source, for anyone free to use. DIYorDIE uploaded a video just yesterday, where he spent some time explaining how he wanted the website to build up and work. While this is a great starting point, we want more input on each and every feature.
This is where all of you guys come into play. If you have any programming experience, or similar, and want to chime in, we would highly appreciate any of your help! Just send a PM or join the DIY_ejuice discord and do @Korlimann.
Don't worry though, even if you have no programming experience, you could still help us out a lot!
Think about features you always wanted on ATF or ELR. About stuff that annoys you when using ATF or ELR. Comment and upvote other comments so we have an idea what the most wanted features are.
Have an idea for a website layout that would be easy to read and have an overview? Make a sketch, upload the picture to imgur and post a comment with the link.
Everything else? Write a comment and let us know! Hopefully we can make this happen!
Thanks for reading and have a great day! :)
The main thing missing from both ELR and ATF are "tags" for recipes.
When you search for "strawberry" on ATF - you only get recipes with "strawberry" in the name.
When you search for "strawberry" on ELR - you get recipes with "strawberry" in the name or contain any flavor with the word "strawberry" in the name.
There should be a way for the uploader of a recipe to enter a handful of searchable "tags". The it would be easier for find a recipe for the flavor profile you're looking for. There should also be room for tags like "123" or "simple" or "SnV" for the other attributes people like to search for.
Importing/parsing recipes is another area where both are lacking. I’d like to have a master list of my favorite recipes from both sites and Reddit as I often forget where I saw that interesting recipe I just got the flavorings for. Neither site makes this easy. It’s not a trivial thing to accomplish but even a semi-functional recipe import feature could save a lot of time and dramatically reduce the time investment needed to get set up. And how cool would it be to be able to paste plaintext/table-based recipes from Reddit or your notes app? I know that is not trivial from a coding perspective, but even a mostly accurate import from ATF, ELR, and Reddit is a killer feature that would convince me to switch.
ATF and ELR importing is easy as it's presented in a uniformed way. Here on reddit people post things in whatever fashion they feel like so it's harder to parse. It would be easier to put a "Copy for Reddit" that created the reddit markdown for pasting the recipe into a post than it would be the other way.
Admittedly that last “wouldn’t it be cool” part was more of a version 2 feature concept as it would take significant development and testing to get right— but a Reddit import feature wouldn’t need to be failsafe to be useful. Even if it only worked for the standardized recipe table format that’s often used here, it would still be quite useful. I know from coding solutions to similar challenges that those could be parsed fairly easily. Going the other direction is a great idea too, but solves a different problem.
ATF has tags so you can sort by tag but only if you pick it from the drop down menu—for some odd reason Q didn’t include them in the search results.
First inpression -> your title doesn't accurately reflect your goal. A calculator only figures out how much of what you need to add. Sites like ATF and ELR are much more than that. Their primary use is as a recipe repository. They also have some minor tools for researching flavors. So accurately stating your goal would be a good first step.
Before you start assembling a team of programmers, you need to figure out the structure of the database - list of fields, relationships, potential queries, etc. Once you have that down - it's relatively simple to add a web-based front end to it.
Your main obstacle will be generating the data. You'll have to convince people to upload their recipes to the new site - and that's not necessarily the easiest task.
Yeah, you're probably right, title wasn't the best choice. But "Calculator" was the word I heard being most used for sites like this, so I figured I'll go with that. I see your point though!
That's right. While I've been studying database engineering for about 3 years, it isn't really the thing I do best. Databases and I are just, let's say, not the best friends. I could definitely come up with something, no question, but ultimately, this thing might have some flaws. So I'd rather have someone with more experience in this field, if possible.
And yes, you're right, that probably is not. But if we manage to get this far, I'm sure there will some people promoting it. I can imagine DIYorDIE doing this for example, but of course, that's not 100% sure.
Thanks for your feedback!
Wayne (DIYorDIE) has absolutely been my best partner in promoting ATF to date - I was proud to be one of his first paid supporters, and I still am.
I too was confused when I saw calculator in the title. I use vape assistant on Android and it works great for converting percentages. I think database would be a better term. As for ideas, I would like to have a working "what can I make with my flavors" option. The ones on ATF and ELR are worthless. Half the time it doesn't allow to import what I have and most times they don't have the flavor in the brand available.
Obligatory: https://xkcd.com/927/
The hurdles to accomplishing this are nontrivial, and have little to do with implementation. Anybody can come up with a shiny new recipe/DIY site nowadays, and it'd probably be pretty good, but the real challenge is collating and keeping up with recipe and flavor product data, plus gaining and growing an active user base. You'd have to sell people on it and get them to *want* to move their data over from something they're already using to your platform, and...well...good luck with that.
If I could propose something, I'd think you'd have much more luck reaching out to ATF, ELR, etc and offering to help improve their infrastructure. In other words, rather than asking the people to come to you, go to the people where they are already. Alternatively, make switching painless by prioritizing attention to streamlining the import of user data. This removes one of the biggest user pain points, but would necessitate some cooperation from other sites.
Or, if you're up to it, play the long game and grow it slowly and steadily.
This is about open data and for the community to have the ability to sustain that data without us. ELR or ATF could shut down tomorrow and all of that be lost forever. If they had any intention to make their databases open, exportable, and community curated, I feel they would have already done it or will do it within the next month or so before our project becomes a reality. If they make it open, I'd love to help! Otherwise, it's just another closed system.
This isn't about competiton or out-doing a current site, this is about creating an open system that can be grown organically by the community.
ATF is community curated - flavors are entered and tagged by members of the community , and I've offered the flavor database to several groups people who have suggested the same thing you are suggesting now. Those efforts unfortunately all petered out relatively quickly, it's a lot of momentum to keep moving.
​
But if you've got momentum, I'd be happy to be involved.
My point still stands. Very few users care about stuff like that until they actually have a reason to use it. Like, if by some miracle ATF and ELR collaborated with you on some kind of open data exchange standard, people still wouldn't have much of a reason to export their data unless there's a really compelling reason to, like a much better site to bring that data over to. At that point, you're kinda, uh...still competing with ATF and ELR anyway.
There are many functionalities that could be added that aren't on the current websites. Like flavors stock management. Something like that integrated with a recipe database as well as an easy way to reproduce existing recipes and linking the source would make this site superior by far.
If it looks outdated and cluttered and lets people add nonsense flavors and fake reviews like ELR, I probably won’t use it.
If it looks and functions a lot like ATF, but with more functions like tags that work, collaboration tools, improved user pages, and other cool stuff that people want, let me know how I can help.
Essentially, an upgraded version of ATF is what we're going for. ATF ifself is pretty good, but like you mentioned it's missing a lot of features. If you have any other or more specific ideas, either on design and layout or features and functions, let us know! :)
On the topic of people adding nonsense flavors or the same flavor multiple times, one would need a group of trusted ppl, like the wonderful mods of this sub, to curate the input flavors correctly and tag the removed flavors to the correct ones so the recipe's get updated correctly. I think this would be the only way to prevent this problem that pleagues both ELR and ATF.
I think that there should be an "other" function though, as a placeholder because there is always going to be a lag time between new flavours being used and new flavours being added.
Then, nonsense isn't returned by the search, because only the "other" should show up. Then perhaps further down in the notes, they can refer to it by name.
I'd be happy to provide the flavors database, if someone needs one. A while back - (maybe years back now?) I attempted to get an open-source conversation going around a universal flavor database, as well as import/export mechanisms, vendor connectivity, etc , and I didn't get a single response. :)
​
If there's real momentum now, I'd be happy to throw whatever resources ATF can spare behind it.
Wow, that would be awesome! Thanks a bunch! ATF itself is really great, but as you can see, there are many more features being wanted. As of now, we're currently 4 people willing to invest some of our time into this project, and many other have offered their help. Do you think it would be possible to build upon what ATF already has? Of course, we could build up all the Front End and Back End on our own, but as other people said, we don't need to reinvent the wheel.
There are definitely collaboration options here - one issue I have is existing subscribers who have paid for a service, regardless of how bad some people think it is ... and the fact that the infrastructure I'm providing depends on the income it generates, so I can't cut my own feet off on day 1.
​
I'm completely open to a discussion about how to work together, and support the idea. ATF already has quite a few community members who use it's open (but not advertised) tools to maintain the flavor and tagging database - the issues are around trust, signal vs noise, continued involvement, etc.
​
I get flak for the "paywall" - but that paywall is really built around maintaining the effort and infrastructure, and reducing noise... I serve millions of pages a month to free users, and bring in a few hundred dollars in advertising revenue, with 20-30 or so hours a month of tech support to people who generally can't remember their email address. :) In addition, a completely open system results in anyone posting anything, increasing the noise to crushing levels. Charging a nominal amount keeps the lights on and lowers the noise volume.
That's definitely an issue I already thought about. Of course, you wouldn't want to cut off your own feet, and what about the people that have already payed for some time, I bet there would be some calling it unfair that they had to pay it and now it's free for everyone, or however we'd handle that then..
If you'd like, you can add me on Discord (if you're using that) using Korlimann#9785. We could discuss anything over there. If you're not comfortable using Discord though we can definitely find another way for communcation - that shouldn't be the problem.
Good luck. Unless there is an easy way to import my stash and recipes I won't be using anything but ELR and ATF. I use both now because I want the exposure of ATF for my recipes but I don't trust that q won't one day hang us all out to dry.
The big hurdle here boils down to "is the juice worth the squeeze?" Are you willing to do the monumental work to accomplish this without monumental compensation? Are you willing to take on the monumental task of maintaining this for the forseeable future without monumental compensation?
Big ideas are lovely if you don't mind working your ass off. Are you willing to work your ass off for free? DIYers already balk at a minimal subscription fee. That's just the nature of our hobby and community.
I'm not trying to be negative. Just pragmatic.
There will be ways to import your flavor stash from any site that lets you export it, I'll make sure that happens. I would probably export now, you never know when a site's feature may break suddenly.
I can't say no one will charge for what they build with the data, but I'll die before there's a charge for the data.
Hang you all out to dry? WTH does that mean? :)
Stop maintaining the site... Take it down etc. You have to admit that you have been majorly MIA and unresponsive to people's issues for the last year. Doesn't give people a lot of confidence.
A lot of the things I'm seeing from people here are:
Technical side
- Database relationships
- Tagging
Visual/Features
- Tagging
- Collaboration
- User pages
- Curated flavor list
- Importing from other sites (which is a super simple js that you could add as a bookmark so it copies the data while you're on another site and then paste it onto your site or you could parse directly from your server to theirs...but of course I highly advise against scraping for many reasons)
From yourself it looks more like you're looking for data analytics on a per X basis.
I know that /u/queuetue does programming for a living and has openly stated that our $2.50 a month for ATF hasn't justified the cost of adding new features or upgrading what's currently built.
Unpopular opinion but everyone's always trying to re-invent the wheel and build from the ground up when a lot of the requests and features that I'm seeing missing/being requested are easily do-able with a few modules in Drupal CMS. There's really no need to re-establish a custom CMS for vape products and it cuts down on development time. There's a handful of custom modules that might need to be developed for this specific case but the Drupal API isn't too bad about that.
That being said if you need anything let me know, I'd be interested in whatever git repo to see where you're at and also what /u/mixnjuice 's current repo/api looks like.
Thanks for the interest. I'm going to skip down to the CMS part. It's true any of the features people are wanting can easily be implemented in drupal or wordpress or ghost or any CMS. I agree. I think they should be implemented in all of the above and available for anyone to use. It's not necessarily the frontend side I'm concerned about currently. This discussion jumped way ahead of where it needs to be, because of Wayne's video.
The major thing right now is preventing this situation from happening all over when the next site becomes out dated. We need an open system that can be the backbone and curate legit data that can then be used in the frontend of anything else. There doesn't have to be one site that holds everyone's recipes, there could be hundreds of copies of propogated data from a mirrored source of base data. This could be as simple as an HTML file running on your desktop (or a github page) that pulls in the data you want and lets you build a recipe, then sends that recipe to a server for someone else to pull. Or you downloading all of your tagged flavors into an excel sheet to see which ones you need to order.
I don't want to create competition for what we have, I want to make it open.
That's where things like the Services module come into play. You're creating a number of services that Drupal (which is truly more of a backbone than a legit CMS [which is also why it's unpopular vs. Wordpress]) already has available.
Like I said you're looking at an open source project that when the next person comes along to fork it will probably more than likely end up doing the same as you. It's a constant re-invention of the wheel, I get it, I've been there, the amount of in-house MVCs I've developed that just end up being a CMS that 1 person has to carry on developing for is maddening.
Call me a defeated developer, but when there's another company that is OS and can carry the development for 95% of projects that people ask for I tend to lean towards it. It really comes down to having a stable system that isn't going to require a fork. When the next big thing comes around and it becomes freebase nicotine vs. salt nicotine vs. future nicotine, or diketones vs. the next scare, you're database will start to spaghettify because you're pushing quick fixes to adapt, or you're re-starting from the ground up.
Literally everything you're asking for can be functionally put together in Drupal in 1-2 days. Then designing a beautiful frontend takes however long that takes. After that then it's how widespread does it come in? If you put an app out that just allows access to your API how many users do you get before it starts to out pace your financial cap on bandwidth?
Open Data is as easy as making a Google Sheet in Drive and making it fully available attached to a Google Form that people can access. You can even pull from that Google Sheet as a csv and format it into JSON through any language that you choose. An Open API is as simple as uploading to any current big data services like Socrata. There's a lot of development time and resources involved and I may just be old and tired about having to develop another (see that xkcd comic in one of the other comments) system when the systems already exist and nothing that's being stated is some kind of groundbreaking revelation requiring yet another framework.
Either way, as I said before, if I can help in any way I would be more than happy too just send me a link to the repo and I'll take a look and try to help further it along.
I appreciate your offer and I will most definitely need it, I just need to do some more testing before I put this out for scrutiny. If it makes you feel any better, Drupal uses the same Symfony composer packages I'm using, they just use a lot more and I need this to be as light as possible. I may not even use PHP for the final final backend, this is just the first iteration to give people an interface to the data. The frontend developers can deal with the bells and whistles.
>our $2.50 a month for ATF hasn't justified the cost of adding new features
That's not really a fair assessment of what I've said. It was more like "fuck you and your 1.99, I have a real job." :P
​
- Q
YES. A replacement or new recipe site would be divine.
Almost anything new would be better than the current offerings of ELR/ATF, where one is free, contains a wealth of information but is incredibly messy due to a lot of junk from way back when, whereas the other is newer, looks nice, has a couple nice features, and most importantly has a good userbase but unfortunately hides a significant amount of functionality behind a paywall.
Outside of viewing recipes, the developer limits accessibility, even including basic abilities such as creating (more than 2!) recipes, IIRC publishing them so they’re public, and even rating them, as “premium” features unavailable to non-paying users. All of these so called features are primitive and fundamental to ANY recipe site, at least one that actually allows some form of interaction. Otherwise, what's left would essentially be little more than a paperback cookbook curated by a random dude on the internet collecting (taking advantage of) crowdsourced data, using (relying/counting on) content from contributors who were kind enough to share their hard work in the spirit of knowledge for public benefit, putting a nice wrapper on all of that information (which was obtained for free), then putting it on the market for resale by flipping the valuable data from everyone else’s hard work (using little of their own) for personal profit...
Not to mention the coin mining fiasco, along w/ the subsequent and very immature replies to anyone who (rightfully, IMO) called him out on his bullshit. I know this community isn’t very tech oriented compared to other subreddits, but that is a HUGE red flag and invasion of privacy/trust, no matter the excuse or whatever else is said to justify their decision or rationalize that kind of behavior.
It would be laughable to expect some form of payments for tools that (for the most part) are available for free on other established sites, let alone a subscription service for a half-assed, incomplete site. Besides, shouldn't those of us who are capitalist worshipping 'Muricans encourage competition in the beloved 'free market'? Yet somehow unironically, this community is wholeheartedly enthused to use and pay for this site in a diy subreddit where the single common denominator (in some form or another) and primary reason which brought practically every one of us here in the first place, is SAVING money!!!
This is honestly why I'm in a hurry to get the open api up and running; the recent push for improvements has me concerned there will be another paywall lock in and we really need open data. I don't think people realize the possibilities we'll have when anyone has access to the combined wealth of knowledge that exists on this subreddit alone. I really wish this hadn't been expedited to this point.
Agreed. Glad to hear others who are fed up with the current situation in this community actually exist and that the people who have decided to take charge also share similar views, including a modern understanding of tech (which consists of basic human decency & internet etiquette, ie: NOT trying to profit off of every single fucking thing in existence, and abstinence from jacking off to capitalism; essentially anyone who is NOT a baby boomer)...
Hey...let's not forget the Awesome Box fiasco and the fact that there still hasn't been one in another year (2 years? idk it's been forever).
Fiasco? Why was it a fiasco - I don't think I ever got any negative responses to the ones I sent out...
None? None at all? Nothing about a large thread of how disappointing the 2nd box was? Because I seem to recall the reception not being well. Since that box, poof there hasn't been one since; and I may be misremembering but I think that was a few months before the Stripe issues.
Granted, since being unable to see behind the scenes those Stripe issues could have been started during that time and you didn't raise awareness to us as the public until it was at it's final stages. So I'll give you the benefit of the doubt on that one.
You may want to go back to review the "mining fiasco". There wasn't one, and I was NEVER EVER EVER running mining on people's machines unless they clicked "yes, I would like to use this" and there was an indicator on the screen allowing people to control it's resource usage and turn it off at any time - it was opt-in and I announced it.
​
Unfortunately, at the same time, The Pirate bay did a similar thing, secretly and without informing users, and every antivirus company on the planet started warning users about the dangers of mining scripts.
The fact that you even used a coin miner (on a paid subscription-based service, no less) in the first place is the issue. The "fiasco" refers to your childish replies whenever it was brought up
If you were a subscriber, then the coin miner was not available to you. As a free user, it was an optional, opt-in experiment, if you preferred to it seeing ads. I don't know what you think is an issue about making that an option to people, but you're entitled to a dumb opinion if you want to have one. As far as for being childish, in the same vein, I'm entitled to being childish if I want to be. So there.
Besides a new calculator, there is functionality that needs to be implemented. As a newbie what I would like to have:
- Tagged/categorized recipes, with a system (a "karma" or similar) where the simple, tried&true ones would easily stand out. They should be classified by device (MTL, RDA, POD, etc.) to be able to scale them when mixing for a chosen device.
- A solid and *updated* list of flavors, possibly each with a group discussion on their notes (we do not all taste the same things, right?), steep times, prefered %s, etc.
- Joining both points above, the best flavors would naturally stand out! Also it should be possible to easily see which flavors work better together.
- A calculator that would integrate it all, and maybe facilitate creativity: a new mode could be checked to mix, say one flavor at some % (to SFT a small amount) and then be able to later add another flavor and then the % of the first one would change (thus keeping the % of base fixed, only changing in PG if they are PG based flavors). This way we could test different relative %s of flavors to see how they work together until a desired result is obtained.
if its just a calculator to mix up a flavour there are already some out there like http://diyjuicecalculator.com/ which is one the best ive used ... only issue with it is i dont think its been updated anymore.
​
So unless you make something like that with a method of grabbing recipes from sites or its own database, as thats the only thing that i think the above is missing but its not hard to input the data so depends how lazy you are lol
I haven't seen it mentioned but https://www.steam-engine.org/juice.html is what I use, not well versed enough to say it's accuracy tho
Edit: I better understand what you mean after reading about that database project. Something of this sort would be exeptionally helpful
This is what I first thought when "calculator" was mentioned. I would like to note that the steam calc has been inaccurate for me in the past. I am by no means a genius but I can mAtHs well enough. It seems to have some secret minimum value set of pg alone.
My nic is pg and my flavors are pg. I like to mix at 70/30 so most of that 30% is taken up by nic and flavor. I only ever need a little of straight pg.
The steam calc did not think that my mix was feasible when I already calculated on paper that it was. I always double, triple, quadruple check my math.
Odd did you set you VG/PG level boxes correctly (it likes to auto set to 30vg / 70pg) I haven't had any issues and the calculations are correct if I do the math on them. When referring to accuracy they have no means of setting a specific flavouring weight or anything like that just if it's a vg or pg base
Well my main issue was trying to calculate the proper amount of nic. From a 4.8% nic to 3% of a 60 ml recipe it should be about 3.75ml. I had another 3.6ml of pg based flavorings. So far 7.35ml of pg out of 18ml=30% of 60ml bottle. 10.65ml of plain pg and 42ml of vg.
I apologize for the messy comment there
100%; 60ml
++++++++ 30% PG ++++++++
6.25%; 3.75ml (48mg/ml pg) nic
6%; 3.6ml (pg) flavors
17.75%; 10.65ml PG
++++++++ 70% VG ++++++++
70%; 42ml VG
I use Portable Juice Calculator. Its a Windows app, sorry no link as its really hard to find.
I like its inventory management but there are some things which I'd like to see;
- threshold warnings that work (let me know when I reach a threshold, and don't let me mix a recipe if I don't have enough inventory)
- analytics (give me data, historical data - inventory prices, juice prices historically so I can see if I'm mixing cheaper per ml over time or if my expenses have gone up, what I'm mixing more often etc)
- with stats, I would then make bases so perhaps a better method to manage base recipes. So far ELR can create a base but then you need to kind of do some hacks to get that in a recipe..
I think forcing people to enter the suggested steep time in an aggressive pop-up AFTER entering in the ingredients would cause people to think more about the steep time. One of the things I can’t stand about either calculator is that the SNV filter almost never brings up stuff that’s /truly/ SNV.
Hotrod's Calculator is amazing. Can't really see anything that need improvement with this though there are frequent updates.
https://www.e-cigarette-forum.com/threads/new-calculator-to-try.480587/
Wish there were a Mac version...
You can try Wine if you want to check out the program, https://www.winehq.org/ . I haven't used it for that particular calculator however it works great for all those little utility/small windows apps.
​
Yes, it's a bit of a pain to do - but it works. Also if you're feeling masochistic, you can set up https://www.virtualbox.org/ with a Windows install on your mac - it is fun to play with.
I would love for a website to save the juices I have in a database as well as the recipes I make. It could let us rate the recipes and have an integration with http://e-liquid-recipes.com/ maybe. That way when we mix a juice we would tell it to the website and it would automatically deduct the amount of flavor one has in stock. It could also be helpful to discover recipes that make use of the flavors one has in stock, as well as remember what recipes were made when, and give you a heads up when you don't have the flavors to mix a recipe and need to restock.
chukr.xyz, praise be its name, had a really great feature: substitution suggestions. You click on a flavor, it showed you suggested flavors to substitute it with and suggested percentages. I have no idea how this was achieved, but it was an awesome feature.
I see others in this thread are talking about tags, chukr.xyz had a tagging feature combined with an inspiration feature where you show it a recipe you like and it rolls you a new, random, recipe based on tags for the original recipe.
god, I miss chukr. just remake chukr :'(
I find that dot1ml and mixejuice from the sidebar, are fine calculators and I believe it will be rare that someone will need something more complicated than those without going into chemistry equations.
I think I shouldn't have written this post while being in a hurry. And the title is poorly picked too. It's not just about the calculations, but more about the general website. Finding different flavours, like the most mixed flavour this day or similar things DIYorDIE already proposed.
Best thing that could happen in my opinion is it tells you grams instead of percentages
What is ATF and ELR?, It sounds like you want a web app designed around the features these apps or w/e already have, with a built in calculator and a modern looking/feeling design. Do you have a preference on what the back-end should be coded in? A very detailed and thought out list of features is needed to help. Also do you have any ideas on what you what the design of this web-app to look like?
Nobody uses http://www.ejuice.breaktru.com ?
that's what i started with, and i still have it and all my oooooooooold (2013) recipes on it somewhere. i should go dig those out and have a laugh.
i moved on to web based calculators for sharing and ease of use, but the breaktru calculator is solid
See, I'm not a really a.. What are you guys calling yourselfs these days? Mixologists? 😀
For the longest time, I've just been buying a flavour, for instance, Capella New York Cheese Cake, and mixing a big batch that lasts me ages, so this app does me just fine.
I keep meaning to get back in to mixing, but I've got so much other shit that I haven't dealt with yet, it keeps being put on the back burner.
A lot of the things people want, is already on my ELR-todo-list. However, I don't collaborate with developers at this point (other than with my friends that are also programmers). I've been a bit inactive recently, because of my normal work. However, I have no intention of leaving ELR alone - and it won't suddenly disappear.
​
When the flavor database on ELR is more or less fixed and stabilizes, I might make an open API for it.
Please purge all recipes 2016 and older... And get rid of the random flavor names. You took a step in the right direction with making the correct names highlighted when entering them in a recipe.
I know that would screw up some recipes but to be fair, if people aren't using the correct names for flavors, they should pay more attention anyways.
>Please purge all recipes 2016 and older...
Why? I sometimes vape recipes from 2014 - if they're good recipes, it doesn't really matter their age. A filter of some sort would be better for this. Also, ratings that are from the, say, last 30 days, 3 months and past year...
>And get rid of the random flavor names.
Yes, by making the site so free to use, kind of backfired ;P In the future, when the base has been cleaned a bit up, it will be harder to add flavors and easier to pick the correct ones.
>I know that would screw up some recipes but to be fair, if people aren't using the correct names for flavors, they should pay more attention anyways.
Kind of agree there - Using the correct names is for the best of the community at large!
Just a suggestion from someone that only uses ELR. It would be great if you could get rid of publicly posted duplicate recipes. Even if that's too hard, something like a 'This recipe is a duplicate of one that already exists. Please consider making it private' to curb the amount of 'Strawberries and Cream' recipes that are exactly the same.
I know you're busy, but I just thought I'd throw it out there.
I would love some sort of recipe revision system. I have made 20+ different versions of a single profile before trying to nail it down and that has resulted in 30+ pages of recipes on ATF that makes finding an older revision that I liked better a huge PITA especially if I have multiple different profiles going on or if I jump back and forth.
Maybe I'm a huge hoarder but sometimes going back in time and looking at an old version helps me find where I went wrong
Thanks for your suggestions! This post is a bit outdated though, check out the "ATF Thursday", in the last post we asked the Community for feature suggestions, and this was a wanted feature as well! You can still go and upvote it there (sorry, I don't have a link, on the phone right now)