Jeremy Saklad
Jeremy Saklad
Note that when I say “energy usage” in that example, I am referring to the energy draw that YAFC already calculates for each recipe. I do _not_ mean determining whether...
> Anything involving beacons is hard to set up because there are so many variables that should be put in. To the point that the feature is likely to cause...
You could conceivably implement this feature by brute-forcing every module combination and selecting the best one. That’s obviously not ideal, but my point is that everything necessary to do this...
Sorry for bugging you about this, by the way. If you don’t want to implement something like this, that is your choice. I am tempted to throw together a script...
I wrote a Python script that does more or less what I was asking for. If you ever decide to implement this functionality in YAFC (which could do it much...
11 parameters is a fair amount, but I wouldn’t call it unusable. Then again, I made the thing. And I didn’t add a method of adjusting which priorities come first,...
It wouldn’t complicate the rest of the model, at least: the idea is that you run it once then use the results, so the parameters don’t even need to be...
One of the other issues causing it to fail validation is that the feed's timestamps, while compliant with ISO 8601, are not compliant with RFC 3339. I believe the precise...
The W3C validator is actually wrong about the encoding: they're using the obsolete RFC 3023, which says that `text/xml`'s encoding is US-ASCII by default, instead of the current RFC 7303,...
It's all very ironic.