/rest-api/v3/push/webrtc/startup
Диаграмма.
У нас стейт джоба завязан на агента, поэтому 200 OK вернет только тогда, когда агент без ошибок начнет Push.
Поэтому последовательность должна быть такой:
В остальном, вопросов нет.
/rest-api/v3/rtsp/startup
Диаграмма.
Pulling RTSP stream - т. к. может быть audio+video stream.
Converting RTSP to internal stream
Playing stream - т. к, стрим можно играть не только по WebRTC, а например по RTMP или HLS
/rest-api/v3/transcoder2/set_watermark
Диаграмма - приввести к согласованному виду
/rest-api/v3/transcoder2/startup
Диаграмма:
Transcoding stream to target parameters - длительное действие
Publishing a stream
Playing stream - НЕ playback, НЕ Play, во всех схемах к одной терминологии
Adapts the stream for playback at different qualities:
По диаграмме:
Т. к. стрим может быть любым, например RTMP
2. Republish stream as WebRtc ABR - не верно, т. к. републикации не происходит.
Converting stream to WebRTC ABR
Стрим конвертируется в WebRTC ABR по профилям, поэтому можно добавить текст - в какие профили стрим конвертируется, например:
profiles: 720p, 360p
4. Play WebRTC ABR stream - лучше обозначать процесс
Playing WebRTC ABR stream
Здесь также можно добавить, что играют те же два профиля:
profiles: 720p, 360p
If CDN chain contains transcoder node, stream is converted on that node:
Предлагаю добавить:
Converting stream to WebRTC ABR
Чтобы показать, что конвертация происходит на Edge, в то время как транскодинг происходит на Transcoder
Can request the stream from another node:
Здесь возможно два случая
Соответственно схемы будет две.
Key Revisions from Previous Outline Opening: Now starts with March 2020 crisis moment, not methodological discovery Context Before Method: Institutional context and theory come before explaining data collection Orphan Comments: Moved to Chapter 2 where it makes sense methodologically Evidence Flow: Pre-pandemic baseline consolidated in 1.2.2, referenced elsewhere Narrative Logic: Crisis -> Context -> Theory -> Method -> Preview Implementation Notes Total target: 14,000-15,000 words Each evidence ID appears in ONE primary location Cross-references use section numbers, not repetition Transitions connect sections without redundancy
Move to the very bottom of the page below the works cited and continuously update based on newly explicit directions/protocol
(how CUNY’s digital communities responded to systematic institutional crises, how students constructed educational infrastructure through peer networks, how platform architectures shaped crisis resilience)
WAY too long of a parenthesis. Restructure this sentence so that the examples come after the point.
comment_ljsi5h9
Link to the comment on the site. It should be archived via: Evidence Index
ethnographic supplementation.
Clumsy unclear phrasing. Revise!
call “non-digital-centric” digital ethnography. They trea
rephrase the end of the sentence to connect with the subsequent verb of treating...
Frame research questions emerging from crisis
Remove accordion dropdown and instead make these into a logically argumentative paragraph that expands on one question by asking the other
Reddit’s pseudonymity enables what Proferes (2017) calls “context collapse management.” Users
Incorporate Neussanbaum and boyd in this paragraph as well as an important critical counterpoint that builds toward this point on context collapse management
This temporal mismatch—crisis operating 24/7 while support operates 40 hours weekly—creates the necessity for peer networks analyzed in this chapter and documented ethnographically in Chapter 3.
Remove adjective 'temporal' and revise sentence structure with theoretical support from Jonathan Crary's 24/7, particularly his commentary on the ends of sleep amid the late capitalist state of constant socioeconomic hardship and compounding austerity conditions.
.
Add commentary from Crary's 24/7 here to close out the paragraph
private navigation of institutional barriers transformed into collective public discourse.
Vacuous string of abstractions
“Rate my schedule”: 275 CUNY vs 34 NYU
At least 3 paragraphs on this
two decades ago, the influential environmentalist Herbert Girardet (1999) was still posing the relationship between the two as a potential ‘contradiction in terms’. What happened? Why does everyone think cities can save the planet, and why now?
for - question - sustainable cities - how did the contradiction of sustainability and cities posed by Herbert Girardet in 1999 get resolved?
https://github.com/collectiveidea/delayed_job/issues/1099 had possibly helpful solutions
Duplicate at: https://groups.google.com/g/delayed_job/c/5fsuBCZX1Ak
"Specifically, when one of my classmates stated how he was struggling with the concept and another one of my classmates took the initiative to clarify it, I realized that that individual possibilities vary greatly among students."
This is actively being worked on - for those interested you can follow the progress in https://github.com/snapcore/snapd/pull/10836
Seeing how this has been treated for 4.5 years makes this seem like a pretty dysfunctional project. Please have mercy on your poor users and fix this.
After 5 years there's still no fix. This is so annoying. I'm now getting rid of all snap packages and installing deb variants instead. Finally I'll purge snap and if these weird decisions keep on going I'll also move to another distro. Common Canonical. Seriously?
I'm trying to help in some way by bringing these issues to light so a discussion about them can take place.
Unfortunately, even though this bug/request was opened in 2016, this feature is still not implemented in ruby-install.
If the document is uncontroversial and agreement is reached quickly it might be committed directly with the "accepted" status. Likewise, if the proposal is rejected the status shall be "rejected". When a document is rejected a member of the core team should append a section describing the reasons for rejection.
Add this statement to the newspaper_search.R program library(RMySQL)
I can't figure out where/how to do this.
Tip: Take your time to think about table design and naming since a well designed database will be easier to work with and understand.
Yes! I like this.
Run the CREATE DATABASE command. Click
I got briefly stuck on the first sentence before noticing the second sentence says how. Maybe "Run the CREATE DATABASE command by either clicking on the lightning bolt icon in the upper left, or choosing Query > Execute Current Statement in the menu." Actually, I'm still stuck—the lightning bolt is grayed out/unclickable, as is the menu option. I tried both while the command was highlighted, and while the command was not highlighted. I also saved the file and then tried.
However, there are times when databases are very useful including: Placing the results of an R program on a web site where the data can be interacted with. Handling large amounts of data. Storing the results of long running programs so that a program can continue from where it left off in case it was interrupted.
Nice
R language
I know there's a good way to google questions about R that gets search results actually about the R language... but can't remember what it is. Might be nice to mention that someone in the less, maybe in a tips section?
Using a database also offered the ability to recover from errors when my R program stopped during processing. Since the database stores the most recently processed work, the R program was able to begin from where it left off before it ran into an error. This was very important because I did not want to waste days of processing by starting over from the beginning.
Excellent explanation!
relational database
Brief definition of relational database for folks who don't know exactly what a database is (beyond e.g. "stores stuff")
I wanted to make further improvements to the finding aid by using natural language processing
Could you provide a brief definition of NLP here, so that novices understand why you wanted to use it?
Introduction
I really like how you situate this lesson as a response to a real scholarly problem you ran into! You might consider preceding this with a few skimmable points so that visitors can tell whether the lesson fits their needs or not. E.g. with my lesson, I started with:
The search bar can be used to view them all at any time.
This doesn't read very well. How about "use the search bar to find all annotations with a specific tag"
loaded whenever you return to the document.
We should really mention that this works when the content changes. Its one of our key features.
"loaded whenever you return to the document even if the content changes".