Wait, so the bash script that I broke down into multiple files because I was unable to create and use functions properly, could not be considered a script?
The word 'pan', came to me from using 3D CAD software and I considered the Jib and Truck actions as 'pan' and the original Pan would be camera rotation, which might be 'turn' (didn't use it as much so don't remember) which was less favourable than using 'orbit'.
Good to know the word origin.
When I started using Odysee instead of YouTube, my page was full of "women vs men", woke culture and onlyfans-esque videos.
I realised, subscribing to a creator actually made a big difference in this case, to get them on you page, because it's not a feed (controlled by an algo), but a simple, categorised list, with the "Following" on top.
In contrast to that, the YouTube's algorithm tended to create relations between videos (using who knows how many criteria) and showed them along with videos from the subscribed and more-often-viewed channels.
It used to show some pretty useful results and it would be a crime for me to downplay its usefulness.
Sadly, by the time I left YouTube, it had started putting the doomscroll content on my page, which is probably another reason for why I stopped using it.
I would call it: Another great mechanism, ruined by capitalism.
An irrelevant but interesting take is that this applies as an analogue to a lot of stuff in electronics related space.
It is harder to receive data than to transmit it, because you need to do things like:
match your receiver's frequency with that of the transmission (which might be minutely different from the agreed upon frequency), to understand it
know how long the data will be, before feeding into digital variables, or you might combine multiple messages or leave out some stuff without realising
this gets even harder when it is wireless, because now, you have noise, which is often, valid communication among other devices
Getting back to code, you now need to get in the same "wavelength" as the one who wrote the code, at the time they wrote the code.
It doesn't require you to put a double space in the end off a line to get to the next.
This is similar to a lot of other implementations you see on web pages.
But it does at least follow through with single level ordered and unordered lists (bullets and numbering) and even automatically adds a bullet when you press Shift+Enter
Also, single line code and code blocks, work.
Then there is the usual italics and bold and even a quote block.
It also converts most of them while you type, instead of you having to wait until sending it, which is better than UIs that don't even have a preview button. I like Preview buttons.
OIC. I should have thought about that.
And here I was considering making this the default way of doing a strikethrough.
On the other hand, perhaps we should update the screen readers to make that work.
Maybe it can be added as a category of stuff that is to be explained separately.
The least I can do is install a screen reader and know what it does with this.
Google Translate's "Listen" option seems to work well with it though.
My phone started doing the thing, where, if I let it discharge to 18% before setting it up to charge, it doesn't charge unless I turn it off and on again.
Wait, so the
bashscript that I broke down into multiple files because I was unable to create and use functions properly, could not be considered a script?