question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cleanly represent in-progress livestreams

See original GitHub issue

todo

  • add --has-source and --has-no-source flags to claim_search to select only claims that do/dont have a source
  • make sure that when you publish, the source is not required (maybe add flag to confirm you really intended not to have a source)
  • make sure claim_update can add a source
  • notify @DispatchCommit when this is live on the cluster

what

  • need a clean way to represent a livestream that’s in progress
  • could just be hiding streams that don’t have a source. but ideally the protobuf has a clean way of saying “this is a livestream”
  • if hiding live streams, odysee needs a flag to include live streams in results

why?

  • want to tie comments to a claim
  • want a url that can be shared (at least after stream has been uploaded, but maybe also during the stream)

plan

  • make a claim with no Source and optionally a future release date (if you know)
  • add flag to claim_search to exclude streams without a source. app will start using this anytime it needs to exclude livestreams.
  • after creator goes live, they (or we, for for them) will update this claim with the recorded livestream. this adds a source and takes it from livestream to normal claim.
  • (nice to have) if you want a fixed url, repost the sourceless claim to another url (maybe /live). the repost will redirect to your next livestream claim, and comments will be attached correctly. once you’ve gone live and uploaded that stream, you make a new sourcecless claim and point your fixed repost to this new claim.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
lyoshenkacommented, Feb 16, 2021

Why can’t you use the url from this in-progress claim? Why do you need to repost?

If you want a single fixed url to share. Let’s say I go live every day at 3pm. I want to tell ppl “watch me at @grin/live”. I don’t want a new url every day.

Using the repost method, i can have @grin/live be a repost of that day’s livestream claim. Since Odysee redirects users, they’ll go to the correct claim (with related comments, etc)

Then tomorrow I make a new claim and edit @grin/live to point to that new claim.

0reactions
lyoshenkacommented, Mar 3, 2021

victor should be done with search this week (assuming tonight’s deploy to odysee cluster goes well). we can do this next

Read more comments on GitHub >

github_iconTop Results From Across the Web

Cleanly represent in-progress livestreams issue - PythonTechWorld
need a clean way to represent a livestream that's in progress; could just be hiding streams that don't have a source. but ideally...
Read more >
Chapter 5 Signal Encoding Techniques
One logic state represented by positive voltage the other by negative voltage. Data rate ... Each of two streams in one of two...
Read more >
How to build your own live streaming app with Mux Video
A step-by-step guide on how to build your own live stream application using Mux Video and Glitch.
Read more >
WebTransport - W3C
Let cleanly be a boolean representing whether the HTTP/3 stream associated with the CONNECT request that initiated transport .
Read more >
Summary, part 2 | Feminism is for Everybody
The second part of Radical in Progress' summary of bel hooks' 2000 book 'Feminism is for Everybody.'
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found