also lnkr

@chayka43 первое правило бойцовского клуба - не хоститься на ру/су/рф-доменах, и уж тем более не отдавать им свои паспортные данн А, ОЙ

@liaizon
I get the storing and fetching part. The problem is that CSS would target a particular HTML/DOM structure, class names, etc., which differ wildly between clients, and there is also various existing styles in those clients that it might conflict with. How would you actually make use of that?
@computersandblues

@liaizon It sounds very feasible until this part. Even if stored and then pulled by some apps (clients?), how would custom CSS apply to different apps?

@computersandblues

@menelion понял. Ну, в общем, если возникнет вдруг время да желание, где-то после ~4 часов по твоим часам, если у меня не какой-то форсмажор - я бы с интересом ознакомился с неведомыми мне реалиями. Если можно, то для личного пользования записал бы, в противном случае буду фиксировать в блокнот.
А так, сам попозже попробую потыкаться. Ну по крайней мере во что бесплатно дают, а то я чем больше на эту и соседние темы гуглю, чем больше диву даюсь - я по каким-то странным причинам ожидал, что accessability конечно же должно быть бесплатным, а тут, кажется, настиг меня урок номер один))

@menelion опана, а это мы как будто хотим! Если чудом неким есть вариант еще и клавиатурные комбо как-то на экране в реалтайме выводить, то это вообще идеально было бы, на вес золота. Я бы себе в персональные архивы такое записал, да потом, по позерски, с завязанными глазами, попробовал бы таким макаром веб посёрфить, авось жизни бы поучился, если не сдамся в первые же пару минут)
У меня UTC+4 зона да фуллтайм работа, коли время выцепишь, так я всяко за.

@menelion залезаю к ним на https://tweesecake.app/download , а оно мне и говорит - Server Error (500). А как отлегло, так вручает ссылки под винду да мак без последующих комментариев, да всё логин какой-то хочет от меня. Вот и поговорили)) Но это ладно, суть понял.
А по вебу вы как гуляете? Наверняка же как-то гуляете. Я вот недавно, у тебя же скорее всего, видел упоминание JAWS. С браузерами это как-то дружит, или там другое?

@menelion вон оно чё. А что за поделки? Навскидку предположу, что они Mastodon API используют, так тогда мне первым делом надо быть с ним полностью и побуквенно совместимым в первую очередь, а что я там в вебе наклепаю - уже второй приоритет?

@menelion как минимум галочка у меня планируется в настройках, javascript к едрени фени отключить. Бесконечная лента и прочее дофига динамическое соответственно в таком сценарии полетит следом, будет статично как на старых добрых форумах.
Кстати, как по факту ситуация с accessibility обстоит на, например, мастодоне? В медиа они не стесняются себя пяткой в грудь бить, дескать, следим, занимаемся. А что по делу?
Мне, опять же, для любопытства, чтоб было с чем себя сравнить.

@menelion направление ты правильно уловил. На русском, конечно, попроще будет, остальное я тоже могу, но в процессе написания скорее из себя выстрадываю, как бы себя не убеждал в обратном.

Взял перечисленное на заметку. Пробовать клиент пока не надо, там погар, хтонь, разброд и шатание. Но я тогда позову на тестирование, когда посчитаю, что что-то на мой взгляд уже готово и хорошо бы фидбек, а там будем посмотреть. Пока всё глубоко в разработке, а я на ранних порах придерживаюсь важных лично мне подходов - вебклиент должен оставаться насколько это только возможно полнофункционально юзабельным даже с отключенным javascript, а JS, желательно чистый и без фреймворков, идёт уже поверх в качестве осовременивающего quality of life, для всяких гадостей вроде бесконечной ленты и интеракций, избегающих обновления страницы, там, где зажравшийся среднеформатный пользователь уже приучен определённого поведения ожидать, а чистый html ещё не вывозит. На мой наивный взгляд, accessability на такой подход должна хорошо ложиться. Но то наивный. Будем пробовать.

По поводу леваков шибко комментировать не буду. Где-то я с тобой согласен, где-то очень даже нет, но твой жизненный опыт, который может сподмочь сделать пользовательский опыт лучше всем, сейчас мне лично стократно важнее этих дрязг. По крайней мере ровно до того момента, пока ты если вдруг не начнёшь проактивно оскорблять крайне разношёрстных людей, которых я считаю своими друзьями, или вставлять палки в колёса инстансам, что я админю, провоцируя дефедерации с кем бы то ни было - уж очень я люблю, когда кто угодно, а я так тем более, может подписаться на кого угодно, и не люблю за чью-либо свободу слова сгоряча всем инстансом улетать в fediblock, будь он хоть трижды левый. Ну это так, rules of engagement, там уж сам прикидывай)

@menelion new handle, have you got yourself banned or something?
Whatever it is, I might need your advice. I'm making an ActivityPub server with the web client included, and I want to make it accessible as fuck, mega-accessible, the most accessible on the market. I am serious, but since I don't have any (major/officially recognized) disabilities, my experience in that field is extremely limited.
I'm not asking for free labor, but if you can point me in some practical direction that I might miss if I rely on the first few pages of Google or AI consultations, or share the most common avoidable issues that are often overlooked, this would be great.

@wakest Imagine getting this far, thinking this would be an grand, brand new feature, and having no idea that akkoma already supports it. ("ughhh" immediately followed by "wait, that's great")

I didn't have a Matrix room. I thought that it was too early for one, and that discussing the Fediverse software within the Fediverse makes perfect sense and would help proving a point, but I'm not really against the idea tbh, so let's set one up and see how it goes: #plamenu:inex.rocks

@wakest Perhaps should come as no surprise but I'm still working out the details. The amount of space allocated for this type of cache, the duration for which it will be stored, and other details, such as various rate limits and the option to disable this feature entirely, will be configurable by the instance admin via the web admin interface. And yeah, this thing is not Tusky-specific in any way. Most of the MastoAPI clients that are able to play videos should also be able to play livestreams, although since practically none of them was actually designed and tested for this case, some of them might have a bad time. I don't have the means to check them all, so I'll have to rely solely on reports from the hypothetical future community.

@inex

game updates mods automatically DURING GAMEPLAY

the what

@a1ba I think I understand, but I find it kinda hard to even call this waiting. Waiting for what? Waiting kinda implies competition, but they basically gave up on the past generations of VR and handed it over to facebook years ago, while presumably trailblazing in some other, distinctly different direction.
Whether it's actually different enough to create a new kind of interest instead of trying to revive the beaten horse I do not know. Maybe I'm just reading too much into things, and they indeed just fucked up. I'm biased there since the Frame is a product for me and I consider myself an enthusiast enough.

@a1ba Okay, "for enthusiasts" is probably a stretch. I’m willing to give it up, but not to the point of "for the modern consumer", more like something in between. The Quest 3 is a product for the modern consumer. The difference between it and the Frame is enormous, specifically in R&D. Valve won’t be able to make much money off the Frame post-purchase, they don’t have anything noteworthy in terms of (upcoming/actively supported) VR games. This is either a massive fuckup and oversight from the very idea of it, even setting the crisis aside, or an intermediate step aimed at engaging with a community that is willing to put up with some inconveniences in exchange for the freedom to customize and explore unplanned uses.

@a1ba I'm not sure. It seems to me that if it weren't for the ram crisis (and now the issues with the other components as well), Valve hardware might have performed well, or at least met Valve's own expectations.
I don't really see any serious plans to take over the world right here and now in their hardware, latest wave included. These are still experiments and intermediate steps that they're occasionally trying to reality-check and refine into a finished product. This *is* the hardware for enthusiasts, with a glimpse of hope of reaching beyond that audience (steam deck).
Of course, that doesn't make up for the current blunder. I can only hope that it won't cause them to abandon this course of action.

Plamenu comes with extended PeerTube support.
Here's an example of what I mean by "extended": an unmodified Tusky client, connected to a Plamenu instance, is able to play a PeerTube livestream.
Plamenu caches the video stream, so dozens of Plamenu users on the same instance watching the same PeerTube stream put no more load on the source PeerTube instance than a single viewer, and I'm currently looking for a way for the Plamenu to participate in PeerTube's P2P, so we can reduce that even further.

@silverpill Thanks for the heads-up, seems like I accidentally dodged that bullet

@npub1600yr4qg5vcfp7svf6ysj0008tn7aphnu0gjs6lw5hjn74n0laasjx889v@momostr.pink oh, thanks, I'll check it out

@menelion @RareBird15 that's an interesting point, thanks for sharing! I thought it might be useful to share some thoughts kind of "from the other side of the fence", since they're pretty much the exact kind of reaction this blog post addresses. I'm usually not the kind of person who actively criticizes every publication written or assisted by an LLM, but I do partially get where that reaction comes from. Reading this post, which I stumbled upon by chance, was somewhat difficult for me at first, I immediately recognized several generative patterns that, these days, I've almost automatically learned to associate, without really thinking about it, with laziness and/or with people who don't respect their audience and churn out posts and other content in an automated or semi-automated manner. Usually there's no meaningful intention behind it beyond ads, marketing, SEO, engagement, whatever, and sometimes it feels like no human being even bothered to read the thing before publishing it. After seeing enough of that kind of content, and oh boy, there is more than enough of it if you work anywhere close to modern IT, those patterns themselves start triggering the association, regardless of why they're there or how much thought actually went into the text. Reading your post made me notice that reaction in myself pretty clearly.

And there isn't really a transparent, easy way to distinguish legitimate use from abuse. I wish there was. From the outside, thoughtful use of an LLM as an accessibility tool, an editor, or simply something that helps you get your own thoughts into words can end up leaving some of the exact same fingerprints as somebody generating fifty SEO articles they couldn't care less about. The reader doesn't get to see the process behind the text, only the result, and by that point the association may have already kicked in. I myself periodically have huge issues expressing my thoughts, and nowadays I sometimes turn to LLMs for help with that, this reply included. And then I often find myself going back through the result and clearing out the trigger words, rhythms, and patterns specifically so that what I'm actually trying to say isn't immediately discarded as slop. Which is kind of absurd in its own way, the tool can help me express something I was struggling to put into words, but then I have to make sure its involvement isn't the first and only thing people notice.

I absolutely didn't mean to imply that you weren't thinking, or to say anything offensive about the way you use AI, and I apologize if that's how it came across. I was mostly trying to describe my own reaction within the context of the environment I've gotten used to reading things in. I'm genuinely glad that you have tools that help you express yourself and make things more accessible to you, and I'm sorry you've had to deal with people flattening all of that into "just use your brain". At the same time, I wish the current iteration of this technology hadn't arrived at the expense of creators, hadn't damaged trust in written work so badly, and hadn't created so many incentives to automate learning, communication, and creative work for the sake of scale. It did, though, and I don't think those consequences can just be discarded either. That's the tension I'm trying to describe here: the same technology can be an incredibly meaningful accessibility tool for one person and part of a deeply shitty and damaging ecosystem for another, and from the outside those uses are not always easy to tell apart.