Author: wordpress_nq07cz

  • Ch-62: H2S9 H3S2: Fringe Communities:

    All of these companies are what would traditionally be considered as โ€œfringeโ€ or โ€œnicheโ€ markets, with a total user base of <10% of the American population, which is 330,000,000 as of 2022 <ref:>, a financial valuation #defd between $10 million and $1 billion, however but not having # any theoretical limit in adoption among […]

  • Ch-62: H2S2: Treatise On Marketing:

    <Back<content.writing-portfolio>From page-703 in Material in Chess ’22. X-ref <ch-19 H2S2 companies and organizations> In the processing of crafting Material in Chess, it occurred to me that the body of knowledge in my field greatly outshined its valuation and that the limitation to growth was not one of inherent value but rather relatability to the end […]

  • H2S135: JS-blob lit-rev[lol]:

    Push: I’m going to spend three days doing a deep dive of IETF documentation on web RTC frame by frame payload, reviewing my list and first identifying a list of docs to look at, reduced now to three hours, before I start working on any recording. I’m also going to meditate on retrieving my video editing […]

  • H2S134: Brief lit-rev of Object.oriented-prog:

    <WP.MIC-H2S72,H3S3.H4S5, interfaces>: Hu: An interface is analogous<half>to a func–fam in PHP, usually defined separately; however, in JS, the fam is described under a single | header, such as MediaStream, and they require a variable to be declared before they can be used, because they are assumed to act upon a value<Turing>. Generally, interfaces are associated […]

  • H2S133: Investigating intermediate paths of mp4 from mediaRecorder.start() to download:

    Hu: Following<WP.MIC-H2S123,H3S4.H4S1-H5S4,H6S4>-><WP.MIC-H2S131,H3S1.H4S4>, we were able to turn on camera, and display its feedback in the user’s browser. We have established the capacity and grounds for media capture, but no recording is made yet, to our local files. There are existing libraries for recording, but our requirement is 30/s, and automated, such that the user need […]

  • H2S132: Writing a MySQL.db-conn that spans the internet:

    Hu: Here’s my template db-conn<Hu-Github, a-r>: Presently, the $servername is set to localhost. However, if I can traverse this to a web-IP, then I can make SQL-writes, across the internet<Turing-dirty>; with this, comes the ability to reset GET-polling to local<Turing.dirty-2> References:

  • H2S131: Manipulating the video tag in HTML:

    Hu: In our RTC-implement,<video>HTML will need to be used multiple, in auto-cam and streamed-record<Turing><WP.MIC-H2S123> H3S1: Associating a video source, generally, with a particular<video>element<Turing>: Hu: has a working demo in browser<fbno>, let’s follow this thought line. H4S1: Displaying a, Hu: Kirupa declares an autoplay property as “true” and assigns an id to this video, […]

  • H2S130: Experience-design in prog:

    <WP.MIC-H2S2><WP.MIC-H2S37>: I would like to # cue up the following clips, for my stream, in a humorous order, with no breaks:; the problem is that within /Entertainment, the aforementioned-2 are in 3-dash: Humor-soundboard, whereas my PSY tracks are buried deep in /Entertainment/Music, and it takes several clicks to get there, and some […]

  • H2S129: Open.SSL-lit,rev:

    Hu: Open-SSL is an open.sourced-software for generating a private | key and an SSL-certificate, a public-key, for the purpose of enabling the TSL-protocol to transport data, via HTTPS, where S means secure, from a browser to a server, and vice versa. HTTP/S works on a toggle-binary, and some finagling would have to occur, in order […]

  • H2S128: Audio type recommendation for web transfer:

    <Mozilla>: Even modest quality, high-fidelity | stereo sound can use a substantial amount of disk space. For web developers, an even bigger concern is the network bandwidth needed in order to transfer audio, whether for streaming or to download it for use during gameplay. The processing of audio data to encode and decode it is […]

  • H2S127: Video type recommendation for web transfer:

    Hu-red<MIC>: ๐Ÿ”‘ Asynchronous video is delayed delivery for differential thought bend timelines<biochem> CM H4S1: Bit rate recommendations: <Mozilla, “Codecs Web-RTC”>: Given a 20 millisecond frame size, the following table shows the recommended bit rates for various forms of media. Media type Recommended bit rate range Narrow-band speech (NB) 8 to 12 kbps Wide-band speech (WB) […]

  • H2S126: A materials science view of computing:

    Hu: Programming languages are made by people closer to Earth, and the rules of prog-lang are to prevent you from providing instructions, giving way to conditions, in which the chip does not fire, a q.tum-Event. // MIC-ref Post: Therefore, understanding q.tum-mech will always provide one with an elevated programming output, as one’s brain will be […]

  • H2S125: A lit-rev of how video game engines generate moving graphics:

    Hu: Video game engines have the unique capability of generating moving graphics, with user input, in real-time, including on the user’s own screen, and deployed remotely; however, this remote deployment is not by video, but rather, the granular user input. Therefore, video games, all, are a unique rendering | engine, that can take a lower […]

  • H2S124: A lit-rev of how human brains generate a visual experience:

    Pre<fbno>: Hu: I need to consider and maybe research how the brain experiences visual input also has build a system that force replicated that, then make the metrics match industry standards. 11:03 PM: The current generation of live video streaming either 1) stops, and does not auto-restart, permanus, unless it’s hard-netted to a television, which […]

  • H2S123: getUserMedia-JS/ PHP/HTML/AJAX/MySQL live video transmission

    Hu: This will be a Web.RTC-less simple | build that nevertheless will transmit video with ultra.low-latency, defined as 100-ms or less: H3S1: Live.code-read: STAR TECH Web-RTC: Hu: Without any idea of the structure yet, I will attempt to extract single lines of code # that I believe are relevant: H4S1: 8:08 in pt-021: H5S1: await<built-in>: […]

  • H2S122: Building a minimalist.TURN-Ser w/ AWS:

    Hu: I’m currently WP-hosted on Dreamhost, but I dare not stretch that platform, for the needs of a raw PHP-install. I’ve had a good experience, previously, with AWS 1) it’s bare metal ready 2) no limit to scalability, theoretically 3) tons of flexibility, with room to be fundamental. I should have no issues running raw […]

  • H2S121: An AJAX / PHP / MySQL live messaging w/ char-by-char paradigm.

    <WP.MIC-H2S112> Reverse chron self.notes-dump, from 11/16/22 to a few days prior: Hu: A socket is also just a file that you write to, which handles the storage, and may not be significantly more efficient. PHP to MySQL might also use a TCP connection, like sockets. MySQL in 2022 is probably significantly more optimized, by about […]

  • H2S120: Socket.protocol-liberation is impossible without import.command-economy:

    Hu: It is precisely at this point #p-f that I have to get into a politico.econo-comp,sci treatise that expounds several of my viewpoints, which includes my perspective, as a Han Chinese having been born there, and now, an American citizen. Shortly put, the United States must implement China’s command economy, which, contrary to misconception, is […]

  • H2S119: Granular control of interpreter waterfall between https:

    Hu: If I can use some combination of blocking and non-blocking, to in conjunction with some parsing controller, that can bounce the interpreter line back up the script, then I can have a smart-script that executes functions on demand. The blocking mode does keep the script “running”, so the smart bounce up would have to […]

  • H2S118: A brief doctrine on indirect solutions:

    When hacking is appropriate: we’ve decided that something is possible, in a domain, but the direct tool to achieve that, by our granular research, does not exist. Forced to choose between not being able to accomplish our task, and creating a temporary inefficiency, that is not of our own fault, we will hack together an […]

  • H2S117: Researching how to push p-dash to users with minimal pc-capacity usage:

    Hu: It seems a bit unreasonable to force users to download WAMP, which also comes with, separately, PHP, and MySQL, both of which are over 1-gb, just to run p-dash, which, itself, is <200-kb. [D]: The raw file size, of the entire wamp64 folder, after the prog-langs have been installed. Only if I can convince […]

  • H2S116: Require-construction lit-rev:

    Hu: PHP reports that # the code from a required | doc will be inserted into a requiring | doc, and run, as if it were written, on and from # the line in which the function require is written<Turing>. This is analogous to the ROW.INSERT-func in Excel: if 100 lines of code, in a […]

  • H2S115: Loop.constr-lit,rev:

  • H2S114: Apache.HTTP-serv,lit.rev:

    Apache is a pre-built and hard-coded 1) perpetual listener, 2) HTTP/S response function and 3) a filesystem directory Imagine a troop quarters: as long as everyone can be awoken, you only need one guy who is not asleep. That guy, in WAMP, is Apache. H3S1: PHP x Apache-HTTP: Hu: Pre: Most of the protocol selection […]

  • H2S113: A +1 o.o-m granular testing paradigm for protocol-dev |=full research:

    <WP.MIC-H2S39,Troubleshooting.lvl-1> Working outside of the explicit | specifications of a product’s features requires rigorous |,testing, at least 1 order of magnitude<Turing>greater than developing features on the MVP. The lack of explicit | instructions indicates that even the og-devs are unfamiliar with the behavior of the logic-strs in these bounds<damn-son!>If the platform.built-upon is intricate<Turing>such that […]

  • H2S112: Socket programming in C:

    Hu: Running out of options, sadly, even in the PHP.Web-Sockets hive, I’ve had to turn to lower-level documentation: Socket Programming in C. This decision is rooted in my fundamental understanding of how chess is studied, and played; try to stick to thick density bodies of theory, within thought space, and venture out, minimally, in the […]

  • H2S111: Converting p-dash into a general cMS Frame-lib:

    Maybe make a basic WP template for streamers and shop it around for $200.

  • H2S110: Group Texting paradigm for real-time character ๐Ÿ•ณ๏ธ:

    One interesting problem could be to negotiate the group chatting aspect, if I can figure that out, then it could live without video.Can just display one live message at a time, always. You will miss some asynchronous messages, because they’re not shown over live.9:53 AMFor group chatting: once you have typed a character, you will […]

  • H2S109: Chaining video-frames into a coherent streaming experience:

    Push to WebRTC video payload frame: The payload frame of a video has to be at least an image; each frame arrives at a finitely different time point; the entire picture at a moment has to be complete. Images need to play back, in the correct order, at a certain frame rate. H3S1: Establish <100-ms […]

  • H2S108: Display a micro-video/audio file in a browser from a,frame:


  • H2S107: Browser APIs for Web.Camera Input lit-rev:

    STAR TECH<a-r><vid-021> at 8:13<anthro>, in line 35, he writes: mediaStream = await navigator.mediaDevices.getUserMedia(mediaConst): H3S1: An anthropological survey of getUserMedia()<fbno>: H4S1: dev-Mozilla<a-r>: The MediaDevices interface provides access to connected media input | devices like cameras and microphones, as well as screen sharing. In essence, it lets you obtain access to any hardware | source of media data. <dev-Mozilla>: […]

  • H2S106: Peer-to-peer HTTP and Web-Sockets:

    Hu: Initial notes: Pull the trigger on WebRTC but make sure they have ICE STUN TURN.

  • H2S105: Base^2 Stream Content: Dynamic User.Gen-Control,Test!

    Hu: WebSockets and all these protocols might all be written for asymmetrical peers, to standardize communication, but if I’m writing internally, I might just be able to strip bare, or even invent my own simple paradigm, just using sockets and fwrite. Once I figure out the resource ID, make a simple test, where I can […]

  • H2S104: How WebRTC splits and sends a video payload frame:

    H3S1: Frame size limits: WebRTC data channels support buffering of outbound data. This is handled automatically. While there’s no way to control the size of the buffer, you can learn how much data is currently buffered, and you can choose to be notified by an event when the buffer starts to run low on queued […]

  • H2S103: Next.Gen-Workouts Personal Metrics Tracker:

    ^^ go through notes, and create a post, for every type of app that I can create; make a dash to track these is all, mostly add to these very soon, go lighter on the “research”, lol, good base, research contextually, tend to these one by one, and lots of blindfold write, until the test. […]

  • H2S102: Superconducting Counter Functions in PHP:

    H3S1: Count to 10,000,000: H3S2: plus.1-perpetual,test: H3S3: plus.1-perpetual,fwrite.test: H3S4: plus.1-completion,time.test:

  • H2S101: Meditation Buttons w/ PHP Background Calculations:

    H3S1: thought_space.collapse(): Start by echo 0;Then, generate counts 10 column table, each column to 1,000 rows, just the boxes, but also maintains a counter. Echos all of this. Then, shows the individual results compiled into an array. The array is then compiled into a string, 1000;1000 etc. A strtok function divides the string at ;, […]

  • H2S100: Chess E-Analyzer:

    Hu: Plug in a FEN, and interact with a chess board to visualize E-diff.

  • H2S99: Personal Health Tracker:

    Hu: A deep stat # health tracking form with API inputs, that is easy to export in .xls format, with HIPAA compliant sharing with doctors.

  • H2S98: PHP Math Visualization for Education:

    Hu: The following document will contain a list of PHP/HTML only functions that will echo a series of lines on a page, that will help students visualize various layers of mathematics.

  • H2S97: Live code reading walkor/workerman: An asynchronous event driven PHP socket framework

    Hu: A cursory glance at the work of Github/u/walkor/workerman and one can gleam the insight of an exceptional–IQ: walkor has the idea to enable generalized | connections, using a browser, and php.web-server to a variety of protocols, thereby unlocking the power of the modern browser<Mozilla, a-r> Hu: A wide range of real-time protocol connections can […]

  • H2S96: IETF Web-RTC RFCs Lit-rev:

    References: Transports for WebRTC<2021>: Overview: Real-Time Protocols for Browser-Based Applications<2021> WebRTC Video Processing and Codec Requirements<2016>: WebRTC Security Architecture<2021>: WebRTC Audio Codec and Processing Requirements<2016>: Web Real-Time Communication Use Cases and Requirements<2015>: WebRTC is now a W3C and IETF standard<2021>: Real-Time Communication in WEB-browsers (rtcweb) TURN URI: […]

  • H2S95: ICE: STUN | TURN Lit-rev:

    H3S1: A desktop TURN server<Turing>: The reason STUN is needed is because the clients cannot discover each others’ IP address, but private web implementation, I am sending the other person’s IP address manually. This needs to be accounted for, in my research. The other part of STUN is to determine peer connection restrictions, which could […]

  • H2S94: Network Address Translator lit-rev:

    References: Reasons to Move the Network Address Translator – Protocol Translator (NAT-PT) to Historic Status<2007>: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)<2008>: Network Address Translation (NAT) Behavioral Requirements for Unicast UDP<2007>:

  • H2S93: IP addresses lit-rev:

    It seems like the current model of IP addresses does not assign each device an IP based on that device but rather, to the router, so your IP would change if you went to Starbucks; IP cannot be the only identifier then, for any application that requires a persistent identification, beyond location.<Turing> References: Realm Specific […]

  • H2S92: Comp-sci x sci-method:

    Hu: Reasonably, the earliest comp-scis, such as those who invented the first OS, and prog-langs, were hobbyists, academics, and people who had the free | time, and mental capacity, to go about comp-sci, at a low | level, with an experimenter’s mindset. Ch.19-H2S3,H3S1: Observations: Why should a change of paradigm | be called a revolution? […]

  • H2S91: BOWSER for business: my next 10 investment decisions:

    H3S1: I will seek $1-mn seed funding for 10% H3S2: I will dump this company back into Distractify, to form a $100-mn conglomerate, and resume 90% control. Hu: Some cash might be required on my part, to re-purchase Distractify, but the investors have either 1) negged the company’s value down to $1-mn or lower at […]

  • H2S90: How to identify the correct scheme for a web.socket-conn:

    Hu: http://, ws://, vs tcp:// H3S1: PHP-testing: H4S1: HTTP.client-test,int.server-2 tcp:// worked to establish socket_server, and socket_client, whereas neither ws:// nor http:// worked as well, in our initial 11/5/22 test. H4: Suspend. We will suspend update on this note, for now. Fin.v-1<fbno>

  • H2S89: How to identify the correct port for a Web.Socket-Conn:

    H3S1: TCP-ports lit-rev: <Wikipedia x Hu x Keith from WP.Buffalo-Slack x RFC-6455><a-rs><fbno>: H4S1: Port #80: <Wikipedia>: The Internet Assigned Numbers Authority (IANA) is responsible for maintaining the official assignments of port numbers for specific uses. The port numbers in the range from 0 to 1023 (0 to 210 โˆ’ 1) are the well-known ports or […]

  • H2S88: How to send an HTTP-req, in PHP:

    Hu-red: ๐Ÿ”‘ A GET request is copy pasting the URL of a Google doc into the body of the doc. Code via <><a-r>: Hu: This code also tell us that the Web.Sockets-server needs to be located in a specific file, since fopen is a function that reads files # H3S1: Web.Sockets-agonostic, Hu: We need 2 […]