Notices by Yukkuri (iamtakingiteasy@eientei.org)
-
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Monday, 13-Oct-2025 03:22:46 JST 
Yukkuri
@lina -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Friday, 03-Oct-2025 01:59:40 JST
Yukkuri
@Inginsub ⑪ Hasan -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Thursday, 02-Oct-2025 04:42:29 JST
Yukkuri
@phnt @snacks @mia Ironically jsonb was faster than mongodb's initial bson implementation by orders of magnitude. They have since rewrote it in last ~5 years, but still not being able to atomically migrate data and having to rely on application to even approximate it makes mongo nearly unusable in production, not to mention having very unpleasant syntax for projections and aggregations. -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Wednesday, 01-Oct-2025 14:02:48 JST
Yukkuri
@lina @menherahair @MK2boogaloo mors -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Tuesday, 30-Sep-2025 20:35:51 JST
Yukkuri
@phnt @i @w0rm @prettygood Here; also pushed commit inverting known activity types to the exclude_type filter, so an index would be used during post deletes.
https://eientei.org/objects/fafbe44b-51a9-469e-a9cc-95a4d877693c -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Monday, 29-Sep-2025 23:14:16 JST
Yukkuri
@mint Grift is strong with this one https://codeberg.org/Remnant/FBI/issues/13 -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Sunday, 28-Sep-2025 03:30:41 JST
Yukkuri
@dorkvalized @lina @menherahair @BleachChan Image/bulletin boards are as far removed from the chat medium as the mail protocols, and as you lump IMs next to them, you are not exactly inspiring confidence in your experience of the group chat medium proper. Try IRC, even 14.4bps dialup connection in non-ideal conditions is still sufficient to stream more than two 512K lines per second. A single group chat of a dozen active participants could steadily generate 1mps with higher bursts just from several conversations running simultaneously. Given 24-50 lines of backlog, that leaves an average of 10 seconds to remain within the conversation and 30-60 seconds to stay at least on the same screen. Now that you have idea of the constraints, you could do very simple exercise by providing a sufficient context for "блядь" that beyond any doubt limits it's role to an interjection, you'll quickly find that for naturally constructed brief responses three is always a room for interpretation and sufficient context is prohibitive to provide under given constraints. Now, without an adequate first-hand experience you may not have the confidence that devocation would fare any better, but there are always public logs - at least ru54 and some of the rusnet have surviving archives, examples of devoiced version used as anything but an interjection would not be in excess of single digit or even fractional percentage of all uses. Incidentally, those also provide ample evidence of it's wide use before first zoomers became capable of speech, if you for a moment stop selectively pretending not understanding how inheritance works. As for your pet theories on genesis, devoiced version eventually replacing or swapping places with voiced version, neither seem plausible - latter two would require a proper plural form, which devoiced variant is lacking, and the former fails to account for chat medium being nearly ideographic in nature - vocalization is not a part of nor a consideration for it, terms are adopted on the basis of their conciseness and brevity before anything else, which is exactly where mainline language still concerned with pronunciation would end up lacking. Not even radio jargon and telegraph were fully free of audible component, but even there you could observe many similar language optimizations in them as well. And regarding reference to a culture - you brought up the fuckru spelling peculiarities, but if you are unaware of their past community, it's a reversible transformation of proper grammatical form, rather than trivial "writing as you hear it". -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Saturday, 27-Sep-2025 02:55:09 JST
Yukkuri
@eric @lain @splitshockvirus -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Saturday, 27-Sep-2025 01:50:30 JST
Yukkuri
@MK2boogaloo Gaped. -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Friday, 26-Sep-2025 13:40:22 JST
Yukkuri
@dorkvalized @lina @menherahair @BleachChan By the same logic you could say zoomer speech was also formed throughout late 1800s and early 1900s, which is dishonest at best. If you haven't seen wide use of "блять", I must suspect you haven't truly frequented IRC, web chats or IMs -- particularly the group chats -- at the time. Thing is, when new communication medium of short, urgently exchanged messages between multiple simultaneous parties appeared, it made inefficiencies of language tailored without such considerations in mind exceedingly apparent, not even the immediately preceding usenet/fidonet mediums were all that functionally different from age-old correspondence as to impose any changes on the language aside from vocabulary, few abbreviations and codepage/keyboard layout interactions. What makes you associate chat-speak with zoomers is that they're uniformly immersed in this new medium, while past generations had sporadic immersion of select percentages of population at best, but it was for gen x and millennials to bring language into shape it never was really tried against before, we were among those involuntary word-smiths, if you will. In the end, I think you well summarised the sentiment of "wanting to yell, but in reality only mumbling to himself", but for some reason you're yet to accept this as a new reality, or to fully recognise the implications of it. Perhaps it's the appetite for language purism or mere elitism implied by it, but language that cannot be concise when it needs to be is even worse than a language that cannot be ambiguous when it needs to be, as it fails at one thing languages exist to do: communicate, and communicating different set of concepts invariably requires different encodings, whether by bloat of context or by syntax itself. Unlike a stylistic choice whether to invoke particular details to the image in mind, or a choice whether to self-identify as a particular culture, "блять"/"блядь" distinction does it's job best at whether to communicate particular connotations that may or may not be applicable within the previously established context, particularly in written mediums, but most prominently in urgent written mediums, where you could not feasibly spend prohibitive amount of time and storage space detailing all necessary fine particularities, or having to deal with the likely confusion. It serves a clear purpose and cannot be substituted under existing constraints.
The case of "носок" - "носков" existing at the same time in modern language by the way is the one of many echoes of dualis in the Old Church Slavonic - the concept of socks coming in pairs is important enough that we still choose to communicate it from time to time. A great deal of grammatical exceptions of modern Russian could be well understood if you but start with Old Church Slavonic, in it's full range of grammatical times, numbers and declensions, but as you would be lost in seemingly arbitrary modern grammar rules without knowing their roots, you would be equally lost treating every new problem as a nail when all you ever had was a hammer of soviet standardisation. -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Friday, 26-Sep-2025 05:08:49 JST
Yukkuri
@dorkvalized @lina @menherahair @BleachChan At least ~5 years ago they were adamant of "блять" being just an incorrect spelling, which is understandable given their reliance on [printable] sources. Either way, it predates zoomers by great margin, being in wide use throughout the late 90s and 00s at very least. Which is probably indicative that past generations never had to deal with internet chats - you can't do away with spelling distinction without providing at least a sentence worth of context. -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Friday, 26-Sep-2025 04:32:09 JST
Yukkuri
@dorkvalized @lina @menherahair @BleachChan Regardless of what wikifaggots tend to think, "блять" works well as a distilled curse without ambiguity of whether you imply someone is a whore and deserving a full stop unlike "бля". -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Friday, 26-Sep-2025 01:24:29 JST
Yukkuri
@lina -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Monday, 22-Sep-2025 00:46:39 JST
Yukkuri
@PurpCat @lina @MK2boogaloo @veinglory CSS 3D transformations can be fun https://public.eientei.org/bachko.html ; too bad it requires custom styles that would be difficult to contain without shadow-dom'ing each status. -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Monday, 22-Sep-2025 00:38:15 JST
Yukkuri
@lina @veinglory @MK2boogaloo Eientei FE/BE has preserved the original class filtering behavior under a setting, so some fun is allowed. But only for similarly supporting instances that don't scrub class on img tags. -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Saturday, 20-Sep-2025 06:51:53 JST
Yukkuri
@pantherastare @lina @MK2boogaloo @SuperSnekFriend @bleedingphoenix A shame it misses on how poast logo is essentially an israeli cancer clinic's. -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Saturday, 20-Sep-2025 05:34:30 JST
Yukkuri
@lina cc: @umamusumebu -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Friday, 19-Sep-2025 05:24:35 JST
Yukkuri
@lina @Loki -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Sunday, 14-Sep-2025 21:46:01 JST
Yukkuri
@p One caveat though: indexes actually defined in terms of operators, `select * from table where network_sub(a, b);` won't use an index for that operator class while `select * from table where a << b` would. But you can work-around that by making your own inlinable function (https://wiki.postgresql.org/wiki/Inlining_of_SQL_functions ; generally `langauge sql` with `immutable parallel safe` is enough) that in turn does `select a << b` and that would start using indexes supporting that operator class. -
Embed this notice
Yukkuri (iamtakingiteasy@eientei.org)'s status on Sunday, 14-Sep-2025 21:33:18 JST
Yukkuri
@p All postgres operators are implemented by functions, check `\do+ <<` in psql. For example, for inet operands it's called network_sub.
All GNU social JP content and data are available under the