httpsterio

Thank you for the extremely thoughtful answer. You hit everything right in the head!

I don't mind coding but I like you might've surmised from my post, I don't feel that capable. Frontend js and doing stuff in the browser that isn't just plain html and css, goes mostly over my head.

Stuff on the server end is a bit easier to grok for me, as long as I can find semi-relevant examples to base my working on :)

I did look at most of the services you mentioned. Obviously, the hardest part is going to be estimating usage. Do I want to pay per video minute, gigabyte or simply by the number of videos?

I did test out Cloudflare Stream and it's almost perfect and the pricing is obviously very attractive. The only thing missing was any ability to sort and manage the videos uploaded unless I work over the API.

I did find Bunny.net which seems like an even better alternative with a lot of more nice-to-haves compared to Cloudflare so I think I'm mostly sorted on that end.

Thank you for your offer. I just might take you up on it when the need inevitably rises :)

Likewise, IRC was also created by a fellow finn back in 1988, Jarkko "Wiz" Oikarinen, at the University of Oulu.

Anyways, you light have to change your locale and/or time zone. I've used iPlayer successfully with Nordvpn myself for a while now.

These jingles are composed by Minoru Mukaiya. He's mostly famous for being the main keyboardist in Casiopea, a very famous Japanese fusion jazz band. He was the keyboardist until the band went on hiatus in 2006, 29 years in all. His style can clearly be heard in these jingles and he apparently has always had a thing for trains anyways as he went on later to start up a train simulator game company.

My Sony A6000 with a 35mm f3.5 lens was 350 euros second hand. Elgato capture card was 99 euros, a mini-hdmi to hdmi cable 8 euros and a dummy battery wall charger was 25 euros. All in all I get a 60 fps 1080p crispy image with great bokeh for under 500 euros.

There's always the Opal C1 that comes at around 300 dollars but imo the image is pretty terrible in comparison.

In my experience, browser side javascript is always the biggest render blocking issue with all the on-the-fly dom manipulation it might entail. Viewport specific css usually adds some kilobytes, a few hundred at most but the browser tends to be relatively swift about those as long as you don't use a lot of stuff like transitions or wildcard selectors on a broad spectrum.

I've myself eaten a soylent type drink for a month straight, at 1200kcal daily intake and I've had nothing bad to say. My basic metabolic rate is somewhere around 3500kcal and even with a huge deficit, I haven't been tired or anything.

As a kid, I got a lot of mileage of whatever our computers came pre-installed with and I don't think it's a bad idea to bundle a scripting language with the machine, simply to have something to tinker and play with without the need to download anything.

The ability to allow contributors to conttibute code is a bonus of it being open source but even if it doesn't accept or merge pull requests, it's just as well imo.

A few things I noticed when trialing.

1. Left sidebar, second icon. What's it supposed to do? I'm assuming maybe export but the button doesn't do anything. I couldn't find export at all either, so I'm not sure if it's broken on my machine or if it's a limitation of the trial.

2. The block type options (paragraph, title etc.), I'd like if the options looked more like buttons rather than just plaintext fit in a box. Just a border around the options (or optionally a background color for them) would already be very helpful.

3. Contrast. The left sidebar icons have very low contrast. The border around the blocks also could use a stronger contrast. I wouldn't actually mind seeing each block's borders at all times just to have a visual outline where one ends and the next starts.

4. I haven't tested this, but does the app support different types of citation standards? Both for the source list at the end as well as the inline references inside a text?

5. do we have any type of control of the final exported product? Can we make our own template with fonts and everything set in place or will I have to export it to LaTeX first?

Sturdy as heck for a keyboard that cost me 60 euros and I've used thousands of hours.

A lot of high contrast combinations are less accessible and even if it doesn't make the text illegible, too much contrast is going to be a strain on the eyes for most people.

Generally, WCAG AA or AAA is enough for most people and you hit that already with #555 on a white background. Something like #1a1a1a is close to the darkest I'd use in most cases.