December 2019

159 tweets

Replying to @afanad

@afanad @useloom
They wrote yesterday:

"Our Engineers tackled this bug and released a new version of the extension
3.3.60.

Please make sure you're on the latest version and verify that the issue is no
longer happening."

In the age of #DevOps, all getting started examples should always include how to
get everything in place using #gitops, not using the browser.

As developers we need to learn about how your platform supports reproducibility,
scalability in an approachable way.

Replying to @itsdaneesaur

@itsdaneesaur It's not very straightforward,
you need to upload the media file to S3 and then create the job.

Here is an example I just ran: mp3 (HR Info Podcast):
https://itsdaneesaur-transcribe.s3.eu-central-1.amazonaws.com/der_tag_in_hessen_20191210_83793670.mp3
and the SRT file:
https://itsdaneesaur-transcribe.s3.eu-central-1.amazonaws.com/der_tag_in_hessen_20191210_83793670.mp3.srt
I can show you how to do this yourself, or I can automate it.

Replying to @coderbyheart

This approach only solves 4 of the 5 examples, so I have to read a little bit on
what to do different. My solution is using the shortest path, while keeping
track of visited state with the list of collected keys, so fields can be used
multiple times if collected keys change.

I totally forgot that through https://czds.icann.org/ everyone can request
access to root Zone files. You can download the entire list of domains in the
@dothiv Zone, which still today has 284 domains. It's still amazing that i got
the chance to launch a segment of the internet.

Replying to @coderbyheart

It doesn't cost us much to provide this service but as a small team of
volunteers we can't provide the level of service that's needed when operating
internet-facing systems. We never charged for this service and we have no
obligations, but we want to make this situation explicit.

#React is getting weirder, Hooks are a great improvement but it's still to easy
for novices to break out of the declarative React world into wild JS because
React and JS are used side by side in the same context.

Maybe in 2020 I find a good project to look into
@elmlang again.

Replying to @coderbyheart

@arne_mertz That's the dilemma, you know that
you have a different team in a few quarters, and features take time, so which
configuration do you optimize for: the small team you have now, or the bigger
team you haven when the feature is complete?