All of this user’s content is licensed under CC BY 4.0.
[…] First thing to do is to convert the analogue signal to hdmi. […]
Why? What’s wrong with directly capturing composite? I have yet to come across an HDMI capture card that doesn’t process the signal in some way (eg no upscaling, no deinterlacing). I’m doing this for archival purposes so I want the signal as unadulterated as possible.
[…] Whatever signal you are receiving in obs wont need deinterlacing, unless the capture device is bad at its job. […]
As I mentioned in my post, I have deinterlacing disabled. I don’t want to deinterlace.
2, 5, 20 (which one exactly depends on the temperature and my general level of comfort at that moment)
[Tesseract is] a Photon fork.
TIL that Tesseract is a Photon Fork. Would you know, by chance, at what point in Photon’s development it was forked to form Tesseract, and what the rationale was?
You’re welcome! 😊
IDK if they’re “Fediverse specific”, but I love SSTF’s (@[email protected]) art.
What client are you using?
I use Lemmy UI [1], Tesseract [2], and Thunder [3].
[…] Boost is totally screwing up the references display
Yeah, I’ve heard report of that bug in Boost before [1] [2].
Out of curiosity, what does it look like for you?
It’s not off-topic when the person in question is involved. […]
As stated in the title, the topic is concerning the AI bots that are spamming GitHub repos [1], not anything to do with nutomic. I personally encountered the bot in nutomic’s repo [2], so I simply used it as a generic example. Given this, your comment feels off-topic, imo.
Maybe a joke at the expense of StackOverflow. […]
Yeah, I figured that, but I don’t understand how it’s relevant to the topic of this post.
I’m not sure I understand the relevance of your comment. Could you explain?
[…] Who’s that […]?
I presume they are referring to @[email protected] [1]; nutomic is one of the main Lemmy developers [1.1].
Context? […] what does he have to do with this post?
If they are indeed referring to @[email protected], I presume they are mentioning nutomic because the example GitHub repository that I cited [3] is owned by nutomic [2]; that being said, specifically regarding their claim itself that nutomic is transphobic [4] and is a genocide denier [4], it is entirely off topic, imo.
I will make no comment on the veracity of the claim itself without evidence. I do not wish to speak for nutomic — I will let them speak for themself here should they wish.
Lemmy maintainer
[…] I recently encountered one of these AI bots in Ibis’s GitHub repository.
Eww Nutomic the transphobic genocide denier.
genuinely great answer. […]
Thank you 😊
[…] thanks.
You’re welcome 😊
Personally, I’ve come to despise the “How’re you?” greeting — it feels like it normalizes impersonal interactions and encourages the behavior of masking one’s emotions. When someone asks “How are you?” I want that sentence to actually carry the emotional weight that it verbally masquerades. So, if someone says “How are you?”, I just respond with a generic greeting like “Hi”.
Interesting — I hadn’t considered it that way.
Matrix is […] distributed […].
It is? How so?
My comment wasn’t protesting the use of Signal; it was rather clarifying the misinformation in OP’s post — ie misinformation that Signal is a federated service.
Signal isn’t federated [1][2][3.1]; it’s decentralized [1][2][3.2]. Though, for all practical purposes, I would generally argue that it’s centralized.
Signal relies on centralized servers that are maintained by Signal Messenger. In addition to routing Signal’s messages, the servers also facilitate the discovery of contacts who are also registered Signal users and the automatic exchange of users’ public keys. […]
One of the controversial things we did with Signal early on was to build it as an unfederated service. Nothing about any of the protocols we’ve developed requires centralization; it’s entirely possible to build a federated Signal Protocol-based messenger, but I no longer believe that it is possible to build a competitive federated messenger at all. […] [interoperable protocols] [have] taken us pretty far, but it’s undeniable that once you federate your protocol, it becomes very difficult to make changes. And right now, at the application level, things that stand still don’t fare very well in a world where the ecosystem is moving. […] Early on, I thought we’d federate Signal once its velocity had subsided. Now I realize that things will probably never slow down, and if anything the velocity of the entire landscape seems to be steadily increasing.
An open source infrastructure for a centralized network now provides almost the same level of control as federated protocols, without giving up the ability to adapt. If a centralized provider with an open source infrastructure ever makes horrible changes, those that disagree have the software they need to run their own alternative instead. It may not be as beautiful as federation, but at this point it seems that it will have to do.
I want to capture interlaced — not progressive [2][1]. I don’t want any deinterlacing done by the capture card [3].
References