120

I need to step away from my PC – for a moment – because, although I have so much to write, the statements made in this video touch me too deeply and are too closely aligned to my own views and too close to the fundamental reasons underlying my own depression and disillusionment and burn-out.

Watch it.

Seriously. Watch it. If you are well briefed on the A.I. bubble and A.I. Hell, just skip to:

  • ~ 34 minutes to miss the demonstration of the tedious issue.[^1]
  • ~ 38 minutes to reach the philosophical statements
  • ~ 39 minutes to hear about deception – the universal "tell" of A.I. scammers
  • ~ 41 minutes if you're prepared for tears: to lament what we've lost, what we so nearly had, what humanity is losing, what is being stolen from artists ¬

(I need some space.)

[^1]: I assure you this video is not about content farms, SEO or the death of search but one might be mistaken for thinking that, in the first half. Don't. It is worth your patience.

[-] schleudersturz@beehaw.org 1 points 2 weeks ago

Zed is very interesting. I know it.

Very recently, I found a fork of Zed that gutted the AI Assistant integration and Telemetry. I forked that, myself, and took it further: gutting automatic updates, paid feature-gating, downloading of executable binaries and runtimes like Node.js (for extensions that don't compile to WASI), integration with their online services, voice-calling, screen sharing, etc.

My branch ended up down 140 000 lines[^1] of code and up less than 300! It was educational and the outcome was absolutely brilliant, to be fair. In all honesty, forking it and engaging in this experiment took less than 24 hours even though I restarted three times, with different levels of "stringency" in my quest.

[^1]: No word of a lie! The upstream repo is well over 20k commits and over 100 MB in volume. Zed is not a nice, small, simple code-base: it is VAST and a huge percentage of that is simply uninteresting to me.

This experiment was very realisable. Forking Zed and hacking on it was quite possible – the same cannot be said for just "forking Electron" or "forking VS Code" or even getting up to speed on those projects to the point of being able to fix the underlying issues (like this OP) and submit merge-requests to those projects. They have a degree of inscrutability that I absolutely could overcome but would not, unless I was paid to at my usual rates. (I have two decades of professional development experience.)

I shelved the effort – for the time being – for a few reasons I don't particularly want to extenuate, today, but I shall continue to follow Zed very closely and I truly, deeply hope that there is a future in which I see hope (and, thus, motivation) in maintaining a ready-to-go, batteries-included, AI-free, telemetry-free, cloud-free fork.

Part of maintaining a fork would include sending merge-requests upstream even though I should hardly expect that my fork would be viewed favourably by the Zed business. But, from what I can tell, Zed seem to act true to the open-source principles – unlike many other corporate owners of open-source projects – and I see no reason (yet) to believe they would play unfairly.

[-] schleudersturz@beehaw.org 14 points 2 weeks ago* (last edited 2 weeks ago)

I don't see it as a "lol" matter.

The Electron project made an extremely stupid decision. Individual people who are left to wrangle with the fall-out and manage the PR have nothing but my utmost sympathy, as do all the down-stream projects (Signal, Discord, VSCodium…) who have to do the same. Even the developers of xdg-desktop-portal are facing unnecessary backlash because of this. Their release schedule and time-line for when org.freedesktop.portal.FileChooser v. 4 could be reliably expected to exist in the wild was surely not kept in secret!

[-] schleudersturz@beehaw.org 15 points 2 weeks ago

This doesn't only affect Flatpak apps. The xdg-desktop-portal mechanism is used by many things. Even "gtk native" applications like Firefox use it when running on a correctly configured KDE environment and one of the nuances of this issue is that those applications – today – continue to work perfectly. Electron is not part of their stack.

I have flatpak on my desktop just for Steam and even flatpak'd steam still seems to work, correctly.

[-] schleudersturz@beehaw.org 21 points 2 weeks ago

It's a good question for the package maintainers.

In their defence: it isn't a direct dependency, it isn't advertised, and it is likely that the distro package maintainers just don't know about it – Electron hardly announce that they chose to depend on something that they know isn't released, anywhere, yet, and won't be for months.

[-] schleudersturz@beehaw.org 25 points 2 weeks ago

To lighten the mood, here's a screenshot of one of the lowest points I achieved while hacking away, trying to resolve the issue: comedic relief screenshot What even is going on, there?

  • pixelated menu
  • "Cancel" button at the top left??
  • "Open" button at the top right??
  • clearly Adwaita but not actually Adwaita as configured – the VSCodium window (behind) shows how Adwaita is actually configured on my system and that's how all native gtk applications actually draw.
172
submitted 2 weeks ago* (last edited 2 weeks ago) by schleudersturz@beehaw.org to c/foss@beehaw.org

I spent the morning trying to work out why all the Electron applications on my desktop (vscodium, the Signal client …) were once-a-fuc•ing-gain showing me clunky, foreign file-open and file-save dialogues (presumably from gtk) instead of correctly showing KDE's dialogues via the very-cursed XDG-desktop-portal mechanism.

I'm on Gentoo. Had I, perhaps, broken something?

Nope. It's just yet another regression up-stream, in Electron:

Once again, despite knowing that nobody has support for something because that thing has not been released as stable at all, yet, the whole Electron stack follows the belief that it's perfectly OK to release a change that depends on that thing and, without it, breaks every KDE user's desktop integration.

Then they blame it on xdg-desktop-portal not having released, yet. And won't roll the change back because December is their "quiet month" – neither will they fix it nor make a work-around, seemingly.

Anyway. Writing this post has served to exhaust my ire. One day, we'll see the back of Electron for good – I can only hope!

Let it also serve as a PSA: don't bother trying to work out if you've accidentally broken something on your Linux desktop – particularly if you're on Gentoo, Arch, Slackware or other hacker-friendly distribution. It's not you. It's not your system. It's just fuc•ing Electron – again!

[-] schleudersturz@beehaw.org 2 points 3 weeks ago

I found this through other means[^1] and appreciated it. It introduced new ideas to me while also describing a lot of things that resonate with me, personally, in words that I wouldn't have strung together, myself.

[^1]: Unbelievably, 'twas the YT Algorithm. Is it because I block ads? Perhaps YT has truly given up all hope of brain-washing me and just fallen back on giving me more of what I want[^2] like a parent tired of a child's nagging? Is this some kind of gas-lighting initiative? Are Alphabet actually not that evil?

[^2]: Kinda wish the creator didn't have to skirt around "acceptable content" policies to survive YT, though. While watching it, I felt their frustration at needing to self-censor coming through and it did threaten to frustrate their argument.

In summary, the argument it makes is that "inclusivity" in games is performative at best and, nearly always, just a token gesture that looks good on the tin and gets praised by the mainstream press but is always implemented in a way that is aimed squarely at cis-het. male players.

One of the strongest examples used to support this is how female player-characters are usually intended to be characters that the player observes, like a voyeur, in the second-person, and player-characters which are intended for the player to identify with and project themselves into are invariably cis-het. males. Lara Croft vs Geralt.

I'm intending to watch it through, again, soon and it might not stand up to the scrutiny of a second, more critical viewing but I certainly found it thought-provoking on round 1.

I'd love to hear other opinions on the video's arguments, though.

[-] schleudersturz@beehaw.org 2 points 3 weeks ago* (last edited 3 weeks ago)

puritan

Ooh. Good. "Victorian" also comes to mind, now.

EDIT: I rather like "victorian" because it's secular and more recent and has the right connotations suggesting how contrived the very concept of "proper" sexuality is – and how absurd. I fear that "puritan" might get bogged down in concepts of religious phobia and zeal which are certainly appropriate but could be a distraction – it's adding trees to distract from the wood.

21

Is there an emoji[^1] that is recognised to mean any genitalia, sexual organ, erogenous zone or the like in a wildcard or reader's-choice kind of way?

[^1]: It doesn't necessarily have to be a fruit or a vegetable or flower or anything particular. The question can be interpreted more generally.

We all know about brinjals, peaches and certain blossom emoji but I'm looking for a single emoji, likely a little suggestive, that people in the LGBTQ+, non-binary, sexually freed and queer community interpret as meaning their parts – whatever those happen to be, whether expressed or observed at birth or chosen, freely, in life – and welcomes their own free will to choose what that means, for them.

Although I have recently chosen new levels of acceptance of the ways in which I deviate from the "traditional"[^trad] gender binary I remain, alas, uneducated in how others talk and communicate about their sexuality and so I find myself scared to express my own sexuality for fear of perpetuating the very indoctrination from which I feel I escape, unwillingly and likely unconsciously. Yet I have Thoughts to share and so I seek, now, to learn how to communicate sympathetically – symbiotically – on these topics.

Help me.

[^trad]: Even here, I know that "traditional" is actually only a descriptor for very recent human history. I actually don't know if it is right to use this descriptor and I wonder. Are there better terms for 20th century cis-het. binary strictures, sexual suppression, prudishness and culture-wars?

[-] schleudersturz@beehaw.org 4 points 3 weeks ago

We won't.

It might look likely through the lens that is appropriate for the rest of the "democratic" world but that lens is not reliable for Germany. In the rest of the "democratic" world, the extreme fascists are hidden much like a dirty secret and so any noise from them that slips through is hugely amplified because it signals the existence of a much larger and more significant fascist movement. In Germany, the extreme right are in clear sight and much more of their noise gets through and the lens that amplifies that noise makes it seem that they might win.

That same democracy will ensure that they do not. In Germany, we can see them for what they are and their seats in parliament represent a more accurate measure of their support base. That support base is tragically large and significant but not enough to give them more than seats in parliament: they do not have a majority and would only form a majority through a coalition with other parties and, here, the transparency is a disadvantage: other parties who stand to be part of the next coalition won't join with the AfD.

Our democracy is not a two-party system. They will not win by jerrymandering or by playing the game. They cannot even sneak power by having a better candidate for key seats because individual seats are won through "first votes" while winning a majority in parliament would require them to take a majority of "second votes" – the system would put those "better" candidates in their seats while correcting the share of seats, overall.

The reason that they are given any space at all is also to their detriment: in Germany, there is exactly one way a political party can be blocked and that is if they contravene the constitution: Die Würde des Menschen ist unantastbar, usw.

This is why we tolerate their presence and one sees the noise they make: they haven't – yet – violated that consequentially, and so they cannot be blocked. Blocking the AfD would be great – I'm all for it, in isolation – but it would compromise something about German democracy and the cure would be worse than the disease because it would only silence their noise: the movement would proceed apace and their movement is, itself, a symptom of a greater problem: there are people who are ill served by the status-quo and the AfD seem to be an "alternative."

If the AfD ever did gain power, however, they simply could not do what they insinuate because that would tear it and the constitutional court would smash them. This is also true if they form part of a coalition: that coalition could not execute on the plans they hint at.

Now, "unantastbar" is a fantastic German word that cannot readily be translated to a single English one but one aspect of it implies immeasurability. The AfD could never pass legislation that discriminated against LGBTQ+ people because that would necessarily divide "people" into two groups and apply a comparator between them and that cannot be done if people's worth is immeasurable. The constitutional court knows this, as do the defence teams who have surely prepared this argument for the day when it becomes necessary.

Germany is by no means perfect and even German democracy is flawed in some ways but, largely, Germany is a good place to live. There are many archaic laws that persist – the gendered language and gendered baby name things count among a legacy of problems – but, largely, these are being progressively overturned. (Albeit slowly.)

Sometimes, we make a few steps forward and then a few (hopefully fewer) backwards but, largely, I think Germany is on the right track.

[-] schleudersturz@beehaw.org 3 points 3 weeks ago

Ok. I've been trying out WriteFreely and, yeah, here: https://personaljournal.ca/schleudersturz/it-is-more-important-to-flaunt-our-humanity-today-than-it-ever-was-before

How does it look?

  • I really like the simplicity of it.
  • I do not like how hard it was to discover a seemingly appropriate host.
  • I never worked out how drafts were supposed to work and this post was just published without drafting or without any way to preview it or test whether it came out with the right formatting.
  • At least one taxonomy would be good: single-level categories, at a minimum.

Maybe some of the features I want are actually there and I'll find them, eventually.

12

What is the Fediverse analogue of blogs? Specifically, which facet of the Fediverse provides the features that blogging used to provide:

  • long-form posts (without character limits)
  • embedded images and other media
  • perma-links and RSS / Atom feeds and other features so that content remains linkable into the future
  • commenting and engagement and associated moderation features
  • re-blogging and sharing
  • community: blogs self-organising into interest areas, pollinate other blogs, link to each other, direct their readers towards each other, etc.

And, most importantly, the ability to create, grow and nurture a following or audience?

I'm on Mastodon and on Lemmy and, in my opinion, neither of those quite hit the mark.

  • Masto is too close to bird-site: character limits (nearly always), shoddy threads, and the fact that one is invariably just firing toots into a torrential onslaught of public toots unless one actually already has a following. Hash-tags and other topic-related features seem ill used, throughout, so discoverability is pretty low unless you already have a platform. Engaging with others in replies earns a lot of boosts and favourites but zero followers no matter how well your reply-toots are received.

  • Lemmy is too close to anotheR site. It's great for being a refuge from that and replacement for that but really not a blogging platform.

I'm happy with both of the above for what they do. I really like the discourse in Masto's reply threads, actually, but it seems useless for actually building a following for one's self. I'm rather new to Lemmy but I like what I'm finding, so far.

[-] schleudersturz@beehaw.org 1 points 4 weeks ago

I did know about the association with PenPot but hadn't actually looked at that because that's not what I'm seeking, presently. But, I did, now, and they are the same people and I also find it very reassuring to see this as No 1 in their FAQ, too:

Penpot FAQ item 1: self-hosting

Penpot is Open Source, and self-hosting Penpot will be free forever.

There are many recommendations in this thread – Wow! Thanks, Lemmy – but I think I shall begin with trialling Taiga, first, and report back on my findings.

[-] schleudersturz@beehaw.org 1 points 4 weeks ago* (last edited 4 weeks ago)

I'm fairly certain that the original authors recommended using another generator – like split-mix-64 – to extrapolate low-entropy seeds to the required state width. Using high-resolution time as a seed is common practice throughout software development and I think they were envisioning split-mix-64 to be adequate to get decent seed entropy from a linearly increasing timestamp. I'm certain it would be adequate to widen 32-bit seeds to the required width.

If my memory is correct, the reasoning was that split-mix-64 – although not as robust a PRNG as the XO*SHIRO family – is trivial to compute and reaches a reasonable level of entropy without needing many iterations.

It looks like[^1] the state width is 256-bits, anyway – not 64 bits.

[^1]: I've lost my references and don't have time to go digging through archives right at the moment but I pulled up my Rust library that implements my PRNGs (which is a port of a C++ re-implementation that exploited learnings from implementing a C# library to replace Microsoft's original, slow .NET PRNG, which was based on the research paper's reference implementation, and ran in production for years and years...)

[-] schleudersturz@beehaw.org 1 points 4 weeks ago

I'm thinking to try Taiga, next, but not today. Their pricing page doesn't seem to indicate that self-hosted instances will be limited and there are other overtly positive signs on their site, too.

Self-hosting is an option they openly promote on the landing page. If you use ctrl+f to search for self-host, you immediately find a link to documentation on how to do that.

Has anyone any experience of Taiga? Horror stories? (Save me time!) Or good recommendations are also welcome.

33

In preparation for the new year, I've been looking for a "better" way to manage what I'm "doing" and looking for a better task-board / ticket manager / project management solution to replace my current unholy and very-cursed mess involving paper notes on a whiteboard (magnets FTW), issues in Gitea (self-hosted) and a whole bunch of .md files in a git repository.

I tried out self-hosting Leantime in my development Docker environment. That was a waste of effort. It's crowded chock-full of "premium" links that just take you to the paid plugin store. I fully expect artificial limits and nerfs to be enforced, too, if one doesn't pay. (Their "pricing" page even alludes to this, stating that "self-hosted" includes the same as their cloud's "free" tier. That would be 150 tasks. That's borderline useless!)

Why ever would I self-host that? Even if I did, how could I trust it to remain free for the features I need, if it paywalls features in the self-hosted scenario? If I self-host it, I'd also want to be free to hack on it and potentially push merge-requests to an open-source project – why would I ever do that for a paywalled app I don't get paid to work on?

My Docker dev. environment runs off a tmpfs so the daemon got stopped, umount /var/tmp/docker, and that shall be the last I ever see of Leantime. Good riddance.

The search continues. I'm open to suggestions of what's worth trying, though. Lemmy, what would YOU actually trust?

view more: next ›

schleudersturz

joined 1 month ago