It's not GNOME, it's not KDE, it's not the new Vanilla OS DE, it's new, uses <100M of memory, is accessible (for real) and uses GTK4 (but not libadwaita).
#Linux #Windows #OpenSource #FOSS
It's not GNOME, it's not KDE, it's not the new Vanilla OS DE, it's new, uses <100M of memory, is accessible (for real) and uses GTK4 (but not libadwaita).
#Linux #Windows #OpenSource #FOSS
RE: fosstodon.org/@arcanechat/1159…
there is no backups for arcanechat.me no user data is kept in backups not even if it is already encrypted data, if the server is wipped all data is gone, but here is the twist, you will barely notice! your account will be magically restored as soon as you connect, and all your data is safely stored in your devices, in your pockets, not in some cloud a.k.a "someone else's computer"
as a #chatmail relay operator this gives peace of mind you don't get with other selfhosted chat solutions
ArcaneChat reshared this.
RE: mindly.social/@Tamasg/11593603…
I concur; YAML is more readable; you chose right.
Test your damn backup scripts.
Don't just assume everything is working. Unplug servers and test it then. How will you know it's broken?
If you aren't testing your backups, you don't have backups.
I am currently using Airpods Pro 2 as hearing aids, with everything cranked as much as it can be cranked. It's probably not the best thing for my particular condition, but it works, mostly, until I can do something better, which is not now.
I have a clock in this room, which chimes every hour through a speaker.
Something about that sound freaks them out a little, and, when I also have screen reader speech or something else going at the same time, I get an almost ghost vocoder effect, where certain frequencies get modulated by the chiming clock.
It makes it almost sound like the clock is speaking, or ghost aspects of it are, anyway.
It's a bit weird.
I don't hate YAML entirely. What bugs me about it are:
* either my IDE defaults to two spaces, or that's the expected indent, because I can't use my normal tabs with it
* I still don't know when to put a hyphen before something
* I can't skip sections by using jump to matching symbol commands
* to me, it feels more fragile and harder to lint
I'm getting used to it, because Gitlab runners, Docker Compose, and other tools demand it. But I still don't really like it. JMO.
Jonathan reshared this.
So apparently my personal combination of social security disability, retirement savings, and “desire to own a house” makes me too complex a client for your run-of-the-mill financial advisor. Striking out with all the household name firms.
Fedi friends, especially #PDX area #disabled pals: can anyone throw me a referral here?
Bitwarden Premium and Families plans now have new capabilities to account for a modern cyber landscape needing to anticipate threats before they happen and allowing users to proactively safeguard their digital assets.Bitwarden
reshared this
ArcaneChat reshared this.
Signal head Meredith Whittaker has responded to concerns about the encrypted messaging app’s use of Amazon Web Services, saying “there isn’t really another choice.”Emma Roth (The Verge)
The so-called “Magnificent Seven” have gone from stock-market leaders to stock-market laggards. But amid the most persistent bout of underperformance …MarketWatch - Christine Ji
Wieso wird im Rahmen der #DiDay Bewegung eigentlich ständig @signalapp empfohlen? Wo laufen denn die Server von denen? Laut Internet auch in den USA auf Amazon, Google und Co…
Oder habe ich etwas übersehen?
UPDATE: Weil mein Post offensichtlich von Fans als Kritik an Signal verstanden wird: meine Frage war, ob ich etwas übersehen habe im Sinn von „Signal Server sind nicht nur bei US-Anbietern gehostet“. Ich hätte gerne Digitale Souveränität mit Signal, nicht einem x-ten anderen System.
Meine Kritik richtet sich an diejenigen, die von digitaler Souveränität reden, und dann doch wieder etwas empfehlen, was dem Cloud Act oder der Kontrolle Trumps (Kill Switch) unterliegt.
#data #privacy #digitalesouveranitat #di_day #Diday #messenger #unplugTrump #fcktrump
RE: mastodon.social/@freedomscient…
This was excellent. Liz and Rachel do a great job.
"Subject: Offer to Purchase The cURL project"
😂
I don't even think it used the docs lol. For the record, if you're curious: // Prism state
#ifdef USE_PRISM
static PrismContext* g_prismCtx = nullptr;
static PrismBackend* g_prismBackend = nullptr;
#endif
Then, // Screen reader output - uses async message to avoid blocking UI
#ifdef USE_PRISM
static std::string g_pendingSpeech;
static bool g_speechInterrupt = true;
void DoSpeak() {
if (g_prismBackend && !g_pendingSpeech.empty()) {
prism_backend_output(g_prismBackend, g_pendingSpeech.c_str(), g_speechInterrupt);
g_pendingSpeech.clear();
}
}
void Speak(const char* text, bool interrupt = true) {
if (g_prismBackend && g_hwnd) {
g_pendingSpeech = text;
g_speechInterrupt = interrupt;
PostMessage(g_hwnd, WM_SPEAK, 0, 0);
}
}
void Speak(const std::string& text, bool interrupt = true) {
Speak(text.c_str(), interrupt);
}
#else
void DoSpeak() {}
void Speak(const char*, bool = true) {}
void Speak(const std::string&, bool = true) {}
#endif
and in the init funcs: // Initialize Prism for screen reader support
#ifdef USE_PRISM
bool InitPrism(HWND hwnd) {
PrismConfig cfg = prism_config_init();
cfg.hwnd = hwnd;
g_prismCtx = prism_init(&cfg);
if (!g_prismCtx) {
return false;
}
g_prismBackend = prism_registry_acquire_best(g_prismCtx);
if (!g_prismBackend) {
return false;
}
PrismError err = prism_backend_initialize(g_prismBackend);
if (err != PRISM_OK) {
return false;
}
return true;
}
// Shutdown Prism
void FreePrism() {
if (g_prismBackend) {
prism_backend_free(g_prismBackend);
g_prismBackend = nullptr;
}
if (g_prismCtx) {
prism_shutdown(g_prismCtx);
g_prismCtx = nullptr;
}
}
#else
bool InitPrism(HWND) { return false; }
void FreePrism() {}
#endif
Notifies listeners of an event.learn.microsoft.com
@x0 @Bri And to make this even more confusing, you're not really using executable code from NVDA, you're just implementing their interface. And the copyright situation of interfaces is even more unclear, especially with all the different countries involved.
The easiest thing to do would probably be to do a git blame on the ACF file and get an explicit okay from everybody involved in its implementation. There can't be that many of these people.
Sensitive content
“Europe is a regulatory morass that is built on bureaucracy, and the layering and layering of rules that constrain economic activity.”
Scott Bessant, US Treasury Secretary
To which Europeans say:
Flint, Michigan
East Palestine, Ohio
Uniontown, Alabama
These places are global bywords for the poisoning of people and nature when you have no regulatory oversight of business and you prioritise ‘economic activity’ at all costs over health and safety.
Marcial 🇨🇷🇻🇪
in reply to mirkobrombin • • •mirkobrombin
in reply to Marcial 🇨🇷🇻🇪 • • •@moshimotsu I was just tired of bloated desktops, I wanted something modern that stays under 200MB. It’s built natively for Wayland using labwc under the hood to avoid reinventing the wheel, with no plans for Xorg support. I love the GNOME workflow but I’m fed up with the libadwaita-only direction and the feeling that any modification is an impurity. This is also a good playground, where I can do anything without being forced into someone else's design guidelines.
Oh and I love experimenting 🫠
TheEvilSkeleton 🇮🇳 🏳️⚧️
in reply to mirkobrombin • • •GNOME Shell doesn't use libadwaita...?
@moshimotsu
mirkobrombin
in reply to TheEvilSkeleton 🇮🇳 🏳️⚧️ • • •TheEvilSkeleton 🇮🇳 🏳️⚧️
in reply to mirkobrombin • • •yes, what about it? That's still not a libadwaita-only direction given that the shell doesn't even use libadwaita
@moshimotsu
mirkobrombin
in reply to TheEvilSkeleton 🇮🇳 🏳️⚧️ • • •TheEvilSkeleton 🇮🇳 🏳️⚧️
in reply to mirkobrombin • • •I'm not sure what you mean by GNOME OS "just existing", especially considering I use GNOME OS on my tablet and desktop nowadays and see plenty of reasons why it should exist (laptop is on Silverblue, but I plan to switch to GNOME OS some day)
I guess I'll wait to hear your detailed take on GNOME OS once you write the blog post ;). I've had a lot of issues with Vanilla OS with how outdated GNOME is, but also the unclear direction with how containers are pushed and the tooling around them, which were some of the reasons why I went straight to GNOME OS from Silverblue
@moshimotsu
Marcial 🇨🇷🇻🇪
in reply to TheEvilSkeleton 🇮🇳 🏳️⚧️ • • •@TheEvilSkeleton Maybe @mirkobrombin and I are misattributing GNOME’s vision for its ecosystem to its vision for the shell.
Naturally the shell can’t be going LibAdwaita-only, as (looking from the outside in) I would figure many shell elements, like widgets/the dock/etc, are just using GTK4—not to mention non-LibAdwaita apps still run on it. The ecosystem is what seems to be going LibAdwaita-only, both in GNOME shell, and elsewhere. I figure?
TheEvilSkeleton 🇮🇳 🏳️⚧️
in reply to Marcial 🇨🇷🇻🇪 • • •@moshimotsu ah, that clarifies it, thanks :)
Just a small correction: Shell does not use GTK; it uses another toolkit called "Shell Toolkit" - see gnome.pages.gitlab.gnome.org/g…
@mirkobrombin