Notices by (dorkvalized@fsebugoutzone.org)
-
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Monday, 29-Sep-2025 19:45:59 JST
@p @MK2boogaloo @e4
> 1667 notifications in one day
> 400 per day on average
c065 - p016-1.png -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Monday, 29-Sep-2025 04:34:18 JST
@menherahair node node
mpv-shot21903.jpg -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Friday, 26-Sep-2025 10:10:02 JST
@iamtakingiteasy @BleachChan @lina @menherahair > Either way, it predates zoomers by great margin, being in wide use throughout the late 90s and 00s at very least.
Late 90s and 00s is exactly the time when zoomers’ speech was being shaped. Also I don’t know what “wide use” do you speak of, I haven’t seen it on the internet yet in the early 2010s. It started to appear often since about 2016–2018. That’s when those born in the mid-to-late 90s emerged on the plains of the internet.
Observing written material is important, – and especially in this case – because how a person chooses to write something, reflects his considerations on how it should be correct to convey the thought. Implying that a person can put at least some sense into speech, and any deviation passed against the written norm is conscious and intentional. Provided, again, that the person in question has an understanding of the norm, at least for the case which concerns the word, whose form deviates. Hope you’re bored already.
In the case with the word “блять” the observation of the written form is important, because in the speech (*yawns*) the distinction cannot be discerned often, due to the characteristic devoicing of the consonant at the end of word in the spoken Russian. You cannot insist, that a word existed, when only its pronunciation was around, and nobody made a distinction. It is when the ‘-ть’ suffix began to appear at the end of the written word, that people started to see a distinction. Perceiving the devoicing as a norm has been growing together with zoomers and made into a separate concept (in fact, cleaving a part of the existing concept) and to a word by them. (Still here? You will regret reading further, I promise.) I refuse to recognise this word, because its basis is in mishearing an actual word. Everyone insisting that it should be a real word is the same to me, as a person insisting we should have “кросавчег”, “[Нина] але-Гавна” и “зобыл”. It is not hard to realise the difference between the volatile spoken variants of real words, changed for a stylistic effect, words that appear and die within a couple decades, –and the rock-solid actual words that are comprising the language and serving as the source for the following generations of variants to come. There’s no real reason for this crafted word to be, because it doesn’t introduce neither a new sense, nor a specific tone or clarity. Niggers not using words and avoiding punctuation is no new thing. Bunin said, that the word “лҍс” loses all of its resin-y aroma together with rescinding the ‘ҍ’, and while I’ll be among the first to advocate for getting “лҍс” back as a stylistic alternative (the reason for which Bunin provided in that very expression of his), it would obviously be wrong, if we allowed it as an ⧸equal alternative to the standard word⧸, as in case with “[нет] носков — [нет] носок”. Because people would hardly pick the alternative, because they would be thinking of a picturesque image of a pinery they remember, along what Bunin has implied. No, the word would be picked because people are just always hungry for something new, they are like magpies collecting any trash, as long as it’s shiny or has a fancy shape. Should we then take the trash home, because some people do it, and accommodate space for it in our living rooms? Normal people take the trash out. The word “лҍс” was an example of a word, that might work. With a limited use, employed consciously, cleverly and when it’d be fitting, this could be an enrichment. The word “блять”, however, has no qualities like that. It’s but a misheard word, that some think to make into an alternative variant of an existing word, and why? simply because they ⧸got accustomed to thinking of it as a correct one⧸ – instead of straightening their awry perception of their native tongue. Mutations are not always good, and people, beginning with V. I. Dal and ending with K. G. Paustovsky wrote about it at length. It required generations of word smiths to bring the Russian language to a coherent shape, to enrich it, and to finally structurise it, making it more orderly – in part, by deprecating some dialect spellings and former norms (and no, I’m not speaking of the 1918 reform, though it is, indeed, a part of the reformation that took place between Lomonosov and Rosental). Even if we forget about everything above, the word “блять” does not even serve the job well – it is supposedly ⧸the⧸ word to be used for an exclamation, an interjection (and an obscene one at that), as opposite to the sense of referring to a ‘promiscuous woman’. Now how does it work for this purpose? If we use “блять” in a sentence like “Да ну, блять…” it kinda works. But if we put it as an interjection, “Блять!” then the spelling contradicts the purpose: an exclamation is pronounced with added loudness, which makes even a devoiced consonant at the end (if the person pronounces it so) sound louder, more like a voiced one. And the spelling via ‘-ть’ conveys the opposite, a hushed tone. To whoever mouth this word is to be put, he would sound like a schizophrenic: wanting to yell, but in reality only mumbling to himself.
With this I think that my point is explained in enough detail. Burning with anticipation to see a top-class intellectual discussion rn fr fr
oh look it’s this thread again helen.png
1377627892001.png -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Friday, 26-Sep-2025 05:08:51 JST
@iamtakingiteasy @BleachChan @lina @menherahair
> Regardless of what wikifaggots tend to think, "блять" works well
Wikifaggots think just like you. One of them, one of them, haha.
> without ambiguity
Words, morphemes and punctuation served past generations well enough. -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Friday, 26-Sep-2025 04:11:41 JST
@lina @BleachChan @menherahair Stay a cretin, I don’t insist. -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Friday, 26-Sep-2025 04:09:51 JST
@lina @BleachChan @menherahair Just say “блять” again.
1455376695638.jpg -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Friday, 26-Sep-2025 04:09:49 JST
@lina @BleachChan @menherahair Uncretinify yourself and re-read menhera’s post.
soviet_moe.jpg -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Friday, 26-Sep-2025 03:50:17 JST
@lina @BleachChan @menherahair
[HorribleSubs] Seitokai Yakuindomo S2 - 10 [720p]_0009.jpg -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Friday, 26-Sep-2025 03:50:16 JST
@lina @BleachChan @menherahair Also “блять” isn’t a word, it’s a zoomerspeak. -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Friday, 26-Sep-2025 03:31:36 JST
@menherahair @lina @BleachChan
> not sssssuuka
That’s too much for just hitting a toe. “Da yob…!” will suffice.
[Mezashite] Sakura Trick - 02 [BDRip 1920x1080 x264 FLAC] [5397E46F] 00:07:55.224.jpg -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Friday, 19-Sep-2025 21:40:40 JST
Yet another “Chinese gacha vs Japanese gacha”
[Beatrice-Raws] ReLIFE Kanketsu-hen (OVA) 01 [BDRip 1920x1080 x264 FLAC] 00:10:59.659–00:11:10.420.webm -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Monday, 08-Sep-2025 03:22:30 JST
@p @Jdogg247 @RedTechEngineer @lainbot Without seeing the actual command, the log and the machine, I can only suppose, that
- either the computer has low RAM and no swap;
- or maybe you’re running this on a cloud server, that doesn’t like high CPU/RAM usage;
- perhaps ffmpeg is too old / too fresh (current stable branch is 6.1.x);
- maybe some additions tucked in to the command (or something altered) cause ffmpeg do something else.
[Shisukon] Mikakunin de Shinkoukei - 04 [BD][1080p-FLAC][4B585B58]_00:06:38.230-1.jpg -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Sunday, 07-Sep-2025 06:08:13 JST
@p @Jdogg247 @RedTechEngineer @lainbot Bro, you’ve already picked -filter_complex. Damn use it.
$ ffmpeg -i blah.mkv -filter_complex '[0:V] palettegen=stats_mode=diff [plt]; [0:V] fps=12,scale=-2:2160 [in]; [in][plt] paletteuse=dither=none [out]' -map '[out]' huge_fucking_.gif
pictish witch by centurii-chan.cr.png -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Sunday, 07-Sep-2025 06:08:11 JST
@p @Jdogg247 @RedTechEngineer @lainbot Who knew, that my little mischief would go unnoticed.
P.S. Please pay attention to
> scale=-2:2160
and
> huge_fucking_.gif
I can confirm, that it works on my machine, if you put sensible numbers to “scale”:
$ ffmpeg -ss 0 -to 3 -i 'don’t turn your head.webm' -filter_complex '[0:V] palettegen=stats_mode=diff [plt]; [0:V] fps=12,scale=-2:480 [in]; [in][plt] paletteuse=dither=none [out]' -map '[out]' -y 'don’t turn your head.gif'
kyoko.gif
don’t turn your head.zip -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Saturday, 06-Sep-2025 14:59:52 JST
@pantherastare @GoonPatrol @Jdogg247 @RedTechEngineer @lainbot @mint @p
yada-yada.png
one of us! one of us!.gif -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Friday, 05-Sep-2025 17:07:24 JST
@Nudhul @mushroom_soup @Owl @f0x @p @parker
Claymore - c072 (v13) - p092 [Digital] [VIZ Media].3.cr.png -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Friday, 05-Sep-2025 17:07:04 JST
@mushroom_soup @parker @f0x @p @Owl @Nudhul No… But those are related. Tangentially.
[Chihiro]_Kono_Subarashii_Sekai_ni_Shukufuku_wo!_-_04_[Blu-ray_1080p_Hi10P_FLAC][FFD88021] 00:01:33.135.jpg -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Friday, 05-Sep-2025 17:06:19 JST
@p @Jdogg247 @RedTechEngineer @lainbot
> Not a matter of complexity; a matter of interface.
If I had to be specific, I’d say “specifics of use”. Anyway, if software opens a new horizon or a new way to do something, it will probably have its UI honed for the purpose, which users may or may not understand, that is, why it is made so (Z-brush comes to mind) – but it doesn’t mean, that the UI is bad or wrong. FFmpeg’s command line UI is nearly ideal for the task. It doesn’t have to be a script. The command is like an instruction, not an algorithm (like with branching and loops). It should be streamlined and, to a significant degree, it is.
> Imagine a version off awk that
Awk is a different thing. A line of text is a line of text that is loaded as it is. Raw. And it isn’t a crumbling stuff like a video file, some anime episode in MKV or in VOB container. It doesn’t have “sub-lines” woven into it, that you need to find and untangle first. The parts of letters aren’t crumbling into primal elements like strokes, stems, semi-ovals and serifs, and you don’t have to reconstruct them from that for the output. A video stream ⧸is⧸ such a crumbling matter. Though it’s possible to work with a stream like awk works on words (with certain limitations, still), if you convert the format and use an encoders, it’s like making awk to become TeX+fontconfig+cairo and redraw the text. TL;DR awk is nothing like ffmpeg, pulling one’s skin onto the other isn’t going to be fruitful.
> It's a bad interface; it's probably easier to write a little program that exposes a libffmpeg binding to Tcl or Lua.
Perhaps, you should try to implement an alternative to the standard UI, take everything into account at the same scale and see for yourself, why the current way was found to be the most simple.
> Oh, no, I use ffmpeg all the damn time, I love it.
> I love it.
suspicious.jpg
> I just think the interface is bad.
Here we go again…
> I just don't like that they used position-dependent flags instead of a language.
This makes working with multiple inputs easier. Imagine that awk has several stdin’s and has to differentiate which commands to run on which input. (On top of handling inputs and output(s) separately, because they’re different kinds of stuff.) I would agree, that handling several inputs is not a task, that an ordinary ffmpeg may be doing often, but it happens not that seldom either. (And by “ordinary” we have to imply someone at least slightly qualified because normalfags will just use somebody’s wrapper a-la handbrake.)
> I have plenty of notes, yes.
Then I don’t understand, what even irritates you. If you use it as often as you say, you should have some automation scripts and code for quick copypaste for unordinary cases. Memorising which options are for he input and which for the output should have been long ingrained and cause to trouble, no?
> Speaking of awk, all of my notes for ffmpeg live on a personal wiki written in awk.
Sugoi.
> Ha, the offer is appreciated, but it's not that I can't use it, it's that it's clunky to use.
The terminal case of “I don’t like it, period”. I can understand that. Okay, then I won’t be nagging you further.
1579414049.png -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Friday, 05-Sep-2025 16:08:26 JST
@mushroom_soup @Nudhul @Owl @f0x @p @parker Well, @p claims that he knows ffmpeg well enough, and the evolution can’t really make someone love a certain thing with a guaranteable result due to the way of evolution being mysterious (read: cursed, recursive, overlapping, E=mc² type of crap…) so the evolution has to go.
1436507096.png -
Embed this notice
(dorkvalized@fsebugoutzone.org)'s status on Friday, 05-Sep-2025 16:03:08 JST
@mushroom_soup @p @parker @f0x @Owl @Nudhul The evolution turns @p into @p who knows ffmpeg. Slo-owly.
02158ad74149324ee641fe7de54de5f1272eda566ccbdcef4de06c6a49e9a29e.png