STREAMING EXPLANATION
Hi all - just an FYI, we have streaming active but please understand, the new apps where the total streaming fix is present won't be active until approved by Apple and Google P... View MoreSTREAMING EXPLANATION
Hi all - just an FYI, we have streaming active but please understand, the new apps where the total streaming fix is present won't be active until approved by Apple and Google Play (7 - 14 days). This is why you'll sometimes see comments lagging behind or like tonight, not showing at all. The new app updates with new code will fix this. Obviously, they work on the web version, seamlessly. Thanks for bearing with us. I'm going to breakdown why it is incredibly difficult to have it flawless, below:
Getting live video + “instant” comments to feel smooth is one of the hardest things you can build on a social platform, because you’re trying to make *two different real-time systems* behave like one seamless experience:
Video wants stability, buffering, and adaptive bitrate to avoid freezing.Comments want ultra-low latency, strict ordering, spam control, and massive fan-out to thousands of viewers instantly.
When you combine them inside iOS/Android apps, across spotty mobile networks, at unpredictable traffic spikes, and with “free speech platform” abuse patterns… the difficulty jumps.
Here’s why it’s so hard, in practical terms.
---
## 1) “Live” doesn’t mean one thing: latency is a spectrum with tradeoffs
Most platforms choose between two worlds:
### A) HLS/DASH (most common, most stable)
* Video is chopped into segments (often 2–6 seconds each).
* Players buffer multiple segments for smoothness.
* End-to-end latency is commonly 10–30 seconds, even when it looks live.
* You can push it lower (LL-HLS / LL-DASH), but complexity rises and it still isn’t truly “instant.”
Pros: Works everywhere, scales well via CDNs, fewer failures.
Cons: Viewers are “behind,” so comments feel “ahead” or “out of sync” unless you delay comments too.
### B) WebRTC (true low-latency, like FaceTime)
* Can be <1 second glass-to-glass.
* But scaling beyond small groups is hard: you need SFUs, TURN, bandwidth, complex routing.
* Mobile networks + NAT types + carrier restrictions cause random failures.
Pros: Feels truly live.
Cons: Much harder at scale, much more expensive (a 60 minute show with 1,000 views would cost us $100), more moving parts.
The core problem: If your stream is 12 seconds behind, but comments arrive in 200ms, your instant comments are reacting to something the viewer hasn’t even seen yet. To fix that, you either:
* artificially delay comments, or
* reduce video latency (hard), or
* accept that it will feel “off.”
---
## 2) Live video isn’t “upload then play” — it’s a pipeline with many failure points
For a single live stream, you’re juggling:
1. Ingest (RTMP/SRT/WebRTC) from broadcaster → your endpoint/provider
2. Transcoding (multiple renditions: 1080p/720p/480p…)
3. Packaging into segments (HLS/DASH)
4. Origin storage/caching
5. CDN distribution to viewers globally
6. Player logic choosing bitrate, recovering from stalls, drifting timestamps, etc.
Any weak link creates:
* black screens
* long spinny wheels
* audio/video desync
* “works on Wi-Fi, dies on LTE”
* “works for some viewers, not others”
And on mobile, you add:
* backgrounding/foregrounding quirks
* battery/thermal throttling
* OS network stack changes mid-stream
* device decoder differences (some phones struggle with certain encodes)
So even before comments, live video alone is hard.
---
## 3) “Instant comments” is a real-time distributed systems problem (not just a database write)
Comments at scale require you to solve multiple competing requirements:
### Real-time delivery (milliseconds)
* WebSockets / MQTT / server-sent events / push channels
* Connection stability across mobile networks (frequent drops, reconnect storms)
### Fan-out at scale (one comment → thousands of viewers)
If a stream has 1,000 viewers, one comment becomes 1,000 deliveries immediately.
That is a throughput and infrastructure problem, not a “code” problem.
### Ordering and consistency (the underrated killer)
Users expect:
* comments appear in order
* no duplicates
* no missing messages
* “I posted it, I see it instantly”
* “everyone else sees it too”
But real systems have:
* race conditions (multiple servers)
* partitions (network splits)
* retries (duplicates)
* clock skew (timestamps lie)
* backpressure (queues fill)
* reconnects (client may replay)
So you need message IDs, dedupe, ordering rules, and reconciliation logic that works even when the network is chaotic.
---
## 4) Combining them makes sync problems inevitable unless you engineer around it
Even if you nail both systems independently, the *combined experience* breaks because:
* Video is buffered and can drift (player might suddenly jump, rebuffer, or change bitrate).
* Comments are real-time and reflect “now.”
* Different viewers have different delays (someone on fiber is 5s behind, someone on LTE is 18s behind).
So when a viewer types “OMG did you see that??”:
* half the audience hasn’t seen “that” yet
* some already did 10 seconds ago
* and your streamer is actually *ahead of everyone*
To make it feel coherent, platforms do tricks like:
* anchoring chat to video timestamps
* allowing “live edge” sync
* delaying chat to match typical video latency
* showing “you are 12s behind live”
* using stream-time offsets per viewer
All of that is non-trivial.
---
## 5) Traffic on social platforms is spiky and hostile by default
Wimkin isn’t Netflix with predictable demand. Social live is:
* sudden raids
* sudden influencer spikes
* unpredictable concurrency
* comment storms during “moments”
* coordinated spam / bot floods
That means the system must withstand:
* 10× load increases in minutes
* abusive traffic patterns (many new connections, rapid posting)
* moderation actions in real-time (delete/ban must propagate fast)
Real-time systems hate chaos. Social platforms produce chaos.
---
## 6) Moderation and “free speech” positioning adds real-time complexity
If you allow broad speech, you get more:
* spam
* brigading
* doxxing attempts
* harassment bursts
* illegal content attempts
For live comments, moderation isn’t “review later.” You need:
* rate limits per user/device/IP
* spam scoring
* link/domain reputation
* shadowbans (often)
* fast delete propagation
* audit trails (for legal disputes)
* tools that work *while the stream is live*
Every one of those layers adds latency, complexity, and failure modes.
---
## 7) Mobile realities make “instant” fragile
Even if your backend is perfect, mobile ruins the illusion:
* Switching Wi-Fi ↔ LTE drops sockets.
* Some carriers aggressively NAT and kill idle connections.
* Android OEM variations break background networking.
* iOS can suspend network activity when the app is backgrounded.
* Power-saving modes throttle timers and sockets.
So you must implement reconnect logic that:
* resumes chat without duplicating messages
* catches up missed comments
* keeps the UI stable
* doesn’t DDoS your own servers during reconnect storms
That is a lot of engineering.
---
## 8) Cost constraints force compromises that users feel
The “easy” way to make things stable is:
* higher video latency (more buffering)
* aggressive CDNs
* overprovisioned real-time infra
* managed chat services
* paid observability/monitoring everywhere
* global edge presence
But when you’re cost-sensitive (and most independent platforms are), you end up trading:
* ultra-low latency for stability
* perfect chat ordering for scale
* instant propagation for moderation checks
* “always-on sockets” for battery/network practicality
Users experience those compromises as:
* “why is chat delayed?”
* “why are comments missing?”
* “why is video behind?”
* “why does it work sometimes and not others?”
---
## 9) Debugging is brutal because the bugs are emergent (not obvious)
The hardest part operationally: you rarely get a clean error.
You get:
* “stream froze for me but not my friend”
* “comments stopped after 2 minutes”
* “Android is fine, iPhone isn’t”
* “only happens on T-Mobile”
* “works until there’s a spike”
To fix it, you need deep instrumentation across:
* ingest stats
* transcoder health
* origin/CDN cache behavior
* player metrics (rebuffer events, live edge distance)
* websocket connection churn
* queue depth and fan-out metrics
* per-region latencies
* per-device player behavior
Without that visibility, teams end up “guess fixing” instead of engineering.
---
## The simplest way to summarize why this is so hard
You’re trying to deliver:
* a huge continuous data stream (video)** that must not stall, while simultaneously delivering
* tiny real-time messages (comments) that must feel instant,
* to thousands of devices on unreliable networks,
* under unpredictable spikes and adversarial behavior,
* with moderation requirements,
* while keeping costs survivable,
* and making it all feel like one synchronized “live” moment.
That’s why even big companies screw it up—and why it’s a monster for an independent platform.
Our new apps should wipe out all of the aforementioned issues. Once again, THANK YOU for understanding and for your patience! I will push app stores for rapid, expedited approval.
No Faketriots Allowed. WiMKiN is so proud to announce our partnership with America's Future! America's Future is General Flynn and Company’s grassroots effort to bring the country back to faith and fr... View MoreNo Faketriots Allowed. WiMKiN is so proud to announce our partnership with America's Future! America's Future is General Flynn and Company’s grassroots effort to bring the country back to faith and freedom. General Flynn knows not only the fight to protect and advance his country, but also has firsthand experience on being unjustly persecuted and prosecuted much like this platform.
We have flipped 0 seats since Trump won. Democrats have flipped 26 seats since Trump won.
Where do you stand? Are you going to allow the Left to take the power back after fighting so hard for 4+ years?
Please be sure to welcome General Flynn and America's Future and add them by clicking https://wimkin.com/AmericasFuture1
Back to DC again late tomorrow for meetings on Tuesday and Wednesday regarding our tests being listed for sale on TrumpRX.gov
While there is no prescription required, we do have FDA Clearance and CL... View MoreBack to DC again late tomorrow for meetings on Tuesday and Wednesday regarding our tests being listed for sale on TrumpRX.gov
While there is no prescription required, we do have FDA Clearance and CLIA-Waivers on the world's first Over the Counter Urine Dip Card for fentanyl, as well our 16-panel Urine drug testing cup (CLIA-Waived).
Many of you know, our A47 designation is for Agenda-47 in honor of the 47th President of the United States.
More to come. Thank you.
Without this woman, I wouldn't have made it through the last 5 years of starting and running multiple businesses that require about 80 hour work weeks. I wouldn't have made it through the constant att... View MoreWithout this woman, I wouldn't have made it through the last 5 years of starting and running multiple businesses that require about 80 hour work weeks. I wouldn't have made it through the constant attempts at sabotage. I wouldn't have made it through the stress. I wouldn't have had the energy to fight the government, or fight big tech for an entire administration. I wouldn't be motivated in trying to change drug policy, and certainly wouldn't be able to just go, go, go all the time. You are my rock and this life most of the time, isn't fair to you. I promise, our day is coming soon.
Happy Valentines Day, my love. ❤️❤️❤️❤️
More Google AI fun... This is relatively close to what it does cost to run this platform. This is why user contribution is necessary and this rebuild / relaunch is happening. 😀
As emails from us are notoriously diverted to bulk, spam, junk, or blacklisted and not delivered at all, I wanted to make a public post on updates with our drug testing venture as many of you hold int... View MoreAs emails from us are notoriously diverted to bulk, spam, junk, or blacklisted and not delivered at all, I wanted to make a public post on updates with our drug testing venture as many of you hold interest.
For the past 20 months, we’ve been laying groundwork.
Not flashy groundwork. Not social media noise. Real groundwork.
The longest days. Brutal schedules. Constant travel. Meetings that go nowhere until they suddenly do. Federal conversations that take months just to move an inch. Healthcare systems that require patience, proof, and discipline before they ever say yes.
This kind of work doesn’t show up in headlines.
But it compounds.
And in the first 60 days of 2026 — especially in February — it has started to show.
The largest healthcare network in Arizona is now the first purchaser of our 5-panel platform — a system many in this industry said was either impossible or unrealistic to execute at this level. The same people who said, “If someone could pull it off, it would become the model for detection and saving lives.”
It’s no longer theoretical. We have done it. And this health system will be using it to keep patients and staff safe, as well as for detection of fentanyl, medetomidine, nitazenes, xylazine, and benzodiazepines in unresponsive victims' nasal passages, mouth, and injection wound sites for immediate knowledge of how to treat. Not every poisoning and overdose is opioid related where Narcan has a high possibility of saving a victim. In life and death, seconds matter. Our innovation provides better odds at saving lives.
We now have the only 16-panel Urine drug testing cup that is FDA-CLEARED and CLIA-WAIVED that includes fentanyl detection on the Cup.
At the federal level, I’ve now had my third meeting in six months with SAMHSA leadership.
Let’s me be very clear here — SAMHSA cannot endorse any specific test or company. That’s federal policy and appropriate.
But what they can do is educate.
And SAMHSA crafted the idea for a national webinar specifically so I could educate their award recipients on emerging threats (nitazenes, medetomidine, etc.) and present the framework and the science behind why single panel and dilution-based testing creates detection gaps.
SAMHSA is conducting the webinar. I will be the primary speaker to their award recipients (SAMHSA provides $2.8 billion for mental health activities and $4.2 billion for substance abuse treatment annually). SAMHSA is currently reviewing the first draft of the presentation (slides below) for public health alignment, accuracy, and against their no endorsement policy.
That’s not an endorsement.
That’s earned access.
Last week, at the request of the Department of Veterans Affairs, we also submitted a formal proposal to bring this platform into the VA system. That request did not come from cold outreach. It came after sustained engagement and is currently being reviewed by whomever in the hierarchy approves their pricing and budget.
We have a second meeting scheduled this month with Robert F. Kennedy Jr. after meeting with him last year. I am in regular contact with his team and you will now see they are active in substance abuse and just announced their STREETS initiative and have allocated $100,000,000.00 for lifesaving measures.
Sara Carter has now been confirmed (finally after a 10 month wait) as Drug Czar and will soon roll out a comprehensive national strategy. When the Office of National Drug Control Policy releases its framework, we will launch our "Test Every Drug" campaign — similar in spirit to “Just Say No,” but built for the multi-substance, deadly reality we’re actually facing. SAMHSA has agreed to participate from an educational standpoint once ONDCP’s plan is public.
And while all of this has been unfolding externally, we strengthened internally.
We retained new corporate counsel built for SEC scrutiny, IPO-level compliance expectations, audit preparation, and navigating purported mergers and regulatory complexity. If you’re going to operate at national scale — especially in healthcare and government — governance cannot be an afterthought. It has to be ahead of the curve. (This also applies to Wimkin as the firm represents both companies)
It is. We are.
They will also be issuing K1 statements this coming week.
None of this happened overnight.
Government timelines are slow. Healthcare adoption is deliberate. Federal engagement requires patience and repetition. It takes time for serious work to come to fruition.
But when the groundwork is real, momentum doesn’t trickle in.
It converges.
The first 60 days of 2026 have made that clear.
And February is just getting started.
Thank you.
— Jase
page=1&profile_user_id=247607&year=&month=
Load More
