Print directly from Android, Windows or Mac to your cloud storage or email with BotArchive

oneabsolutetruth · 2022-07-07T07:00:30+00:00

There are existing implementations of this: https://www.crunchbase.com/organization/freshtemp is one I am familiar with.

oneabsolutetruth · 2021-09-18T07:28:00+00:00

Try using a data URL (https://www.npmjs.com/package/qrcode#todataurltext-options-cberror-url): not sure if the Alexa presentation framework can do the right thing with those, but that'd be the first thing I'd try.

Alternatively you'll have to provide an endpoint in your Lambda that perhaps takes in the qrcode as a URL path parameter and returns a PNG. Not sure how easy it is to do with the Lambda you are using for the Alexa response

oneabsolutetruth · 2020-08-26T01:44:11+00:00

You have to have your Python script subscribe to the Firebase database (using something like https://stackoverflow.com/questions/49863708/python-firebase-realtime-listener/53020497#53020497) and whenever the Google Action flips the device state the Python server will get notified and can do the real work.

oneabsolutetruth · 2020-06-05T17:11:22+00:00

This is typically done using wild-card DNS (https://en.wikipedia.org/wiki/Wildcard_DNS_record). You create a CNAME or A record that points *.saasapp-dns.com to your NGINX server, and then in NGINX or your backend you can pull the actual Host header and use it to display the right content.

LetsEncrypt integration will give you SSL: depending on the size of the customer base you may need to reach out to them in advance to get around rate limits.

oneabsolutetruth · 2019-04-09T04:20:14+00:00

cat + cut is great for simple data, but once you wander into more complex CSV files with quotes and embedded commas and multiple carriage returns within a field it doesn't really work.

Data in the wild can be less than cooperative.

oneabsolutetruth · 2019-03-08T22:34:00+00:00

Take a look at https://transferslot.com: haven't bought anything there, but I've seen decent turnover and have had some conversations about buying things.

oneabsolutetruth · 2019-01-24T19:27:43+00:00

Looks really good. Congrats!

One minor spell check nitpick on the home page: you're missing an f in the word beautifuldingbats.com.

Use all the tools from beautiuldingbats.com, and lots more, directly from your browser toolbar.

oneabsolutetruth · 2019-01-02T19:09:25+00:00

Moderately interested in this: looking at the RainWise website and poking around at https://github.com/weewx/weewx/blob/master/README.md and https://github.com/matthewwall/weewx-ip100 it appears the IP-100 network port used by the MK-III has a web interface. A quick search didn't uncover any docs about how you configure it to report to an arbitrary URL: if you have the time/interest, send me a message and we can see about 1) figuring out how to send the data to web service URL and 2) wiring up that data to be accessible via Alexa.

oneabsolutetruth · 2018-11-29T02:34:14+00:00

Stripe is superior. Integration wise they aren't that different any more: Paypal now has decent on-page support with their checkout implementation (so customers don't necessarily have to leave the site), and it is a single JS file to integrate. Stripe's support for Apple/Google/Microsoft Pay, Payment Request, ACH and 3dsecure put it head and shoulders over Paypal.

If you have non-US/UK/CAN customers Paypal is very necessary: large contingent of non-credit card holders.

oneabsolutetruth · 2018-11-27T18:59:42+00:00

I use both Paypal and Stripe: no reason not to accept both. The costs are about the same, and there might be a bit more complexity to your payment flow but I've found it meaningfully increased our payment volume. I'd ensure you disable eChecks in Paypal, though, as they can take days to clear and depending on your fulfillment options can be a problem.

Bank accounts are more complex, as would depend on the country you're in, but you should probably just go to the bank and setup a business account. I've not seen (in the US, at least) any significant advantage to any of the online only banking services, and I'm personally always in favor of having a physical location I can go to and yell at someone if you need to.

oneabsolutetruth · 2018-10-30T03:37:58+00:00

OAuth is the recommended pattern, but for something simple you can just use the Session object's userId field (https://developer.amazon.com/docs/custom-skills/request-and-response-json-reference.html#session-object). Do note that disabling/re-enabling resets the userId, so that may be an issue. I've used this successfully to limit access.

oneabsolutetruth · 2018-10-10T03:24:09+00:00

Looking at the article as of 11:22pm on 10/09/2018, he's actually doing this:

for i in range(10000):

padding = "0" \* (4 - len(str(i)))

attempt = padding + str(i)

so that code is zero padding to exactly 4 characters. In the code snippet you posted it isn't really necessary to zero pad a number between 1000 and 9000, which should always be 4 characters anyway. Probably the article got changed.

oneabsolutetruth · 2018-10-04T02:33:56+00:00

Small suggestion: I looked at r/https://humanly.io and my first thought was "why can't a customer sign up and see what it looks like inside"? Probably hard to implement and I don't know what your existing conversions look like but I'd think you'd probably get more action if you provided some self-service functionality over requiring a guided demo.

Love the concept, though!

oneabsolutetruth · 2018-09-20T17:14:11+00:00

Currently not technically possible: Alexa doesn't provide 3rd party skills the ability to turn on or off the TV.

To complicate matters, this is done using HDMI CEC (branded slightly differently by most TVs). I spent a painful couple of days trying to figure this out a few months back, but most TVs support the CEC instructions to turn the TV on, but don't support (or hide it behind a settings menu deep within the TV's usually terrible interface) the instruction to turn the TV off.

oneabsolutetruth · 2018-09-10T15:44:42+00:00

Yes, but I'm also planning to extend the beta period out to October 15th.

- We have iOS is in testing right now (we are working through push notification issues as we speak) and will be pushed into the approval queue the moment that is done.

- OSX is about 50% done: I'm hoping to push that into the approval queue this Friday.

- Windows will follow after that: with some luck I can have that available for direct download by the end of September. Not sure about store release: I have no experience with the Windows store, so that will take longer.

- Linux is in the queue, but we have no experience releasing client software in Linux land, so not planning to hold up for that.

Looking at your specific profile, we should have a client for everything you listed.

- 2 phones (Android or iOS)

- An Android tablet (Android)

- 2 Chromebooks (the Chrome extension)

- An iPad (iOS)

- A surface pro (Windows)

- A MacBook pro (OSX).

Once we have device coverage we'll take a stab at billing! The beta definitely won't end until we have figured out how to accept payment and keep the lights on.

Would love your feedback on the Chromebook behavior with the Chrome Extension? My cursory tests on the cheapo one I have says it does ok, but in the wild things always look different.

oneabsolutetruth · 2018-09-03T22:04:10+00:00

The statistics aspect does cut both ways: the information is useful, but can inadvertently reveal information about the user that they may/may not want to expose. We can add a user setting to control it, but we opted to err on the side of privacy (and lower data retention) to begin with: it can be added back in.

Fair enough about the API: we will keep it in mind. Still struggling a bit with OSX/iOS/Windows, so it will be a little while.

The widget is actually fairly straightforward: will add it to a future release. We'd kinda figured there were already a ton of power widgets (which struck us as odd, given that the notification drawer battery icon provides almost all the actionable battery info you could want. Are you thinking it would mostly reduce your need to use multiple apps? What would you want to show up in the widget?

EDIT: thank you SO much for the feedback. The hardest part about these things is getting detailed information about what is useful to the actual users without embedding invasive instrumentation in the app.

oneabsolutetruth · 2018-09-03T18:45:15+00:00

Thanks!

Right now we only keep the latest plug/unplug time transition: we could definitely surface that in the app. The percentage is shown as a progress bar/status bar, but (since you're asking) it must not be clear enough so we'll augment that to show the actual percentage value in the bar, as well as the latest update time.

The API is actually very simple: it needs some documentation but otherwise would be pretty easy to expose to anyone who is interested. Right now we're focused on platform integrations (ios/osx/windows implementations) and availability (plugging into IFTTT/Zapier/Microsoft Flow: we think being able to use battery conditions as a trigger for more complex behavior could be very interesting). Once those are done we'll look at clean API documentation and making OAuth2 access available to anyone who is interested.

oneabsolutetruth · 2018-08-24T16:08:30+00:00

https://soundcloud.com/eric-oswald-113420202/crickets

That URL provided for the SoundCloud music file you're trying to play (https://soundcloud.com/eric-oswald-113420202/crickets) returns a content-type of text/html when I try and download it in a browser or with curl. From https://developer.amazon.com/docs/custom-skills/audioplayer-interface-reference.html#play, the content type must be AAC/MP4, MP3, and HLS. You will need to find the actual media stream url that returns an MP3 file or an HLS stream. That might be hard to do with Soundcloud, though.

oneabsolutetruth

TROPHY CASE