mastodon - Link to source

Most hashtags are pretty obvious, you just put # in front of a topic. For example if a post is about coffee it might have the tag #Coffee

However, many popular hashtags have difficult-to-guess names, so I've started a list to help people discover them:

➡️ fedi.tips/fun-and-useful-hasht…

Copy-paste a hashtag into the search box in Mastodon if you want to browse or follow it.

If you have suggestions for non-obvious hashtags that should be added to the list, let me know in the replies 🙂

#FediTips


Fun and useful hashtags to follow on Mastodon and the wider Fediverse | Fedi.Tips – An Unofficial Guide to Mastodon and the Fediverse

An unofficial guide to using Mastodon and the Fediverse
fedi.tips
#FediTips #coffee

mastodon - Link to source

If you would like to help financially support the development of a new Wayland compositor for Xfce, you can do so by contributing funds via our #OpenCollective accounts.

For US contributions:
opencollective.com/xfce

For EU contributions:
opencollective.com/xfce-eu

These contributions will help pay for the funding of longtime Xfce core developer Brian Tarricone to create xfwl4, a brand-new Wayland compositor for Xfce.

Thank you for your support!

#Xfce #Wayland #Rust #FOSS #Linux


Xfce - Open Collective

Xfce is a lightweight desktop environment for UNIX-like operating systems. It aims to be fast and low on system resources, while still being visually appealing and user friendly.
opencollective.com
#linux #foss #rust #opencollective #Wayland #xfce

gotosocial - Link to source

From the Slint email list:

Dear all.

I am very sad to inform everyone that our friend Didier died last week.

Early 2015, I asked on the slackware list if brltty could be added in the
installer ; Didier answered promptly that he could do it on
slint. Afterwards, he worked hard so that slint became as accessible as
possible for visually impaired people.

You all know that all these years, he tried and succeeded to answer as
quickly as possible to our issues and questions.

He will be irreplaceable.

friendica - Link to source

@Friendica Support

There is a fork of Mastodon available, called "Glitch Edition", that has some special features implemented. My new instance at social.defocn42.net is running this fork.

I came upon an interesting error when trying to connect to the instance. Adding the user "m1rk0@social.defcon42.net" failed because of an unknown network. Then i tried it the other way around from the Mastodon instance and could follow myself on Friendica. The connection is now mutual and the Mastodon instance is recognized as "glitchsoc".

Are there known issues with glitchsoc and Friendica? It's weird, that the connection can be established only from one side and is working normally afterwards.

@Friendica Support

mastodon - Link to source

Looks like the UK does not have our back:

"Keir Starmer rejected his Canadian counterpart’s call for mid-sized countries to band together in the face of unpredictable global powers — and insisted his “common sense” British approach will do just fine."

Like I said, we'll find out who our friends are.
politico.eu/article/keir-starm…


Starmer to Carney: No new world order please, we’re British

U.K. leader says he’s ‘a British pragmatist applying common sense’ after Canadian counterpart called for mid-sized countries to team up in the era of Trump.
Dan Bloom (POLITICO)

mastodon - Link to source

#CSS `@custom-media` available behind a flag in Firefox Nightly

Lovely syntax, just lovely.
nerdy.dev/custom-media

@custom-media --motionOK (prefers-reduced-motion: no-preference); @media (--motionOK) { transition: transform .3s ease; }

Custom Media · January 23, 2026

@custom-media working behind a flag in Firefox Nightly! @custom-media --motionOK (prefers-reduced-motion: no-preference); @media (--motionOK) { transition: transform .3s ease; } Lovely syntax.
Adam Argyle (nerdy.dev)
#css

mastodon - Link to source
Hahahaha. What if I asked an AI to rewrite the SpeechPlayer repo to work on Linux. Good dear God. I bet it would be a disaster full of bugs. I'm tempted though, just make it a new branch first and go from there. Also building a speech-dispatcher module for you Linux nerds. Really, really don't know how that will go. Now that's vibe coding to the max, I have zero familiarity with Linux argtypes and such when avoiding Windows headers. Like, zilch.
in reply to Matt Campbell

mastodon - Link to source

Tamas G

@matt oooh yeah, but that's even a bigger refactor, moving away from C++ to it, but it's also a less mess for cross-compiling. I also have no idea if there's a different UI toolkit I'd need to use for things like the phoneme tool, as it's written in basic win32 for now, something I had familiarity with from college and high school days, but also like, locks me into C++ for it pretty bad, so a cross-platform UI solution would be needed before it got too many more dialogs and settings. I could have used Python / WX, but then of course you're including all the precompiled Python runtime and can't make it as lean.
@Matt Campbell
in reply to Matt Campbell

mastodon - Link to source

Tamas G

@matt I think I could do the Rust migration in layers. First, get Linux cross-compiled for the frontend and player, maybe editor, + speech dispatcher module that's simple. Then it can be re-written so the SpeechPlayer and Frontend go Rust first, then the other parts. UI development feels like the worst place to start learning how Rust is. Rust has a very different mental model (ownership, borrowing, lifetimes).
@Matt Campbell

mastodon - Link to source
NV Speech Sapi does not have an official distributed release and probably will not until it breaks out of ESpeak's phonemizer. Sorry y'all. But because we link against libespeak, it's technically a big no-no to even have it around. Perhaps that could be an experimental project, to rebuild NVSpeech Sapi with Gruut, but damn, a 700 megabyte SAPI engine? people would cry.
in reply to Cleverson

mastodon - Link to source

Tamas G

@clv1 hmm. this is where the new settings might help you.
Mess with these settings and see if they can help in your YAML:
settings:
# Smooth big formant jumps at boundaries (good for word-initial L+vowel clicks)
trajectoryLimit:
enabled: true
applyTo: [cf2, cf3]
maxHzPerMs:
cf2: 16
cf3: 20
windowMs: 30
applyAcrossWordBoundary: true

# Give /l/ a soft onglide (reduces the “snap” at the start of a word)
liquidDynamics:
enabled: true
lateralOnglide:
f1Delta: -50
f2Delta: 200
durationPct: 0.35

@Cleverson
in reply to Cleverson

mastodon - Link to source

Tamas G

@clv1 hmm. Try to lower: semivowelOffglideScale by a bit to see if that improves it. If it’s inside one word (like beira, loiro, ouro), start with semivowelOffglideScale. A tiny "syllable break" can happen when a semivowel is followed by a vowel, or a liquid/tap/trill, and this setting shortens the semivowel only in that pattern.
If it happens across NVDA “chunks” (label/role/value stitching), then it’s a seam, not a glide problem. In that case flip segmentBoundarySkipVowelToLiquid so the engine doesn’t insert the segment-boundary gap when a chunk ends with a vowel/semivowel and the next begins with a liquid/tap/trill.
And even when timing is right, /r/ can feel like a hard wall unless it has motion, so enabling liquid dynamics (rhotic F3 dip) often makes the landing smoother.
@Cleverson

lemmy - Link to source

Vanadium version 144.0.7559.109.0 released

Changes in version 144.0.7559.109.0:

  • update to Chromium 144.0.7559.109
  • activate Nordic EasyList for Danish, Finnish, Icelandic and Swedish rather than only Norwegian (both variants) and Greenlandic (this change has been included since Vanadium Config version 150)
  • add EasyList Adblock Warning Removal List (this change has been included since Vanadium Config version 151)
  • extend rebranding of Chrome/Chromium to Vanadium

A full list of changes from the previous release (version 144.0.7559.90.0) is available through the Git commit log between the releases.

This update is available to GrapheneOS users via our app repository and will also be bundled into the next OS release. Vanadium isn't yet officially available for users outside GrapheneOS, although we plan to do that eventually. It won't be able to provide the WebView outside GrapheneOS and will have missing hardening and other features.


Comparing 144.0.7559.90.0...144.0.7559.109.0 · GrapheneOS/Vanadium

Privacy and security enhanced releases of Chromium for GrapheneOS. Vanadium provides the WebView and standard user-facing browser on GrapheneOS. It depends on hardening in other GrapheneOS reposito...
GitHub
#grapheneos
in reply to Andrew Nesbitt

mastodon - Link to source

IzzyOnDroid ✅

for forges, you might wish to add @Codeberg (Germany, EU). Not sure where Sourcehut sits (is it NL, @sir ?)

So there ARE alternatives. And as already pointed out in another comment by @jens , Forgejo/Gitea can be self-hosted as well. And at least for Forgejo, Federation is upcoming IIRC, to take another hurdle (separate registrations) from self-hosted installs.

But yeah, that list reads horrible, re "sovereignty" 😢

@Jens Finkhäuser @Codeberg @sir

mastodon - Link to source
Now it's really work time. Off to meetings while I tune phonemes in the background with my tools and AI. Tools are what make the world of difference. If you don't have them, you don't have your foundation to stand on. Tools that can give you data, look at the patterns in different ways, see if they can be stress tested in other contexts, ETC. What would we ever do without darn tools.

mastodon - Link to source
Another phoneme editor fix: If phoneme's fields, like _isSemivowel are not defined for the given phoneme, allow you to add it by choosing it in the list and setting a value for it. This will make adding new state-variables to phonemes easier. Remember: Flags like _isSemiVowel, _isVoiced, _isStop, are for the engine to know how to treat the sound, not for the sound itself to change. These don't influence Klatt params as much as sound timing, and which rules get applied to that phoneme token when it's used.

mastodon - Link to source

It was interesting to read up on the AI assisted code review at lesswrong.com/posts/7aJwgbMEiK…

For context: I'm personally responsible for at least 29 curl CVEs. Out of the recent 6 CVEs mentioned in the blog post I found two. This gives me some perspective, I think.

I do not utilise AI tools in my vulnerability research. I am also fiercely critical of harmful proliferation of AI. This is due to the unsustainable way it is currently pushed, and use of as marketing ploy and gimmick rather than producing measurable benefit to users. This leads to negative impacts on economy, education & learning, not to mention impacts to nature due to wasteful use of energy.

This doesn't mean I am against AI. I have written by own AI tooling (fully local RAG with support for arbitrary number of models running on local nodes, implemented in python). I found the usefulness of such tool to be limited at best. It is somewhat useful in mass analysis of large document bases, but the level of analysis is superficial at best. These AI models are after all just language models, and do not have any true understanding or intelligence.

And here is the gist of it: The current tools are not intelligent. Understanding this limitation is the key of successful deployment and utilisation of AI tools. The tools can be useful in certain tasks, but they do not replace true intelligence.

The AI tooling AISLE are developing certainly is one of the better uses of AI, and definitely surpasses all my personal dabbling around it. It is clear that the tool does find vulnerabilities. The key question is how much hallucinations and false positives it produces: If the tool generates thousands of FPs and the true findings are hidden among them this limits the value and usefulness of the tool (of course it doesn't entirely negate it, many tools produce false positives). In short: The quality of the findings is key, and poor signal-to-noise ratio is highly undesirable.

Either way, I think there is a future for AI tools and they definitely will be helpful in vulnerability research.

I personally will keep exercising my wetware for this work, however.

#cybersecurity #infosec #vulnerabilityresearch #thoughtoftheday

#infosec #cybersecurity #vulnerabilityresearch #thoughtoftheday
This entry was edited (1 day ago)

mastodon - Link to source
I fixed the number "four", and words like "pour" "door" to sound good in Speech Player for US English: the "oh" sound is no longer short, by adding a schwa stop for it.
Also tuned words like "pool" and "tool" to sound less Mid-Atlantic. Some of you were telling me Speech Player sounds a bit like Stewie from Family guy, and you know, I can see it.

mastodon - Link to source

Based on this deranged slop flood out of @mozilla : stateof.mozilla.org/

1) I'm happier about my decision to stop using Firefox.
2) I'm going to stop using @thunderbird .

Which is a shame, because Thunderbird is still the best mail client, and Firefox brought us hope in the IE days.

Thanks for making everything worse @mozilla .

#mozilla #firefox #thunderbird #slop

State of Mozilla 2025

stateof.mozilla.org
#firefox #mozilla #thunderbird #Slop @Mozilla @Thunderbird: Free Your Inbox

mastodon - Link to source

Ktoré potraviny riedia krv a chránia pred trombózou?

▪️Kelp - Prírodné antikoagulanty. Môže znižovať viskozitu krvi.

▪️Cesnak - Obsahuje fytoncídy. Nielenže znižuje viskozitu krvi, ale pomáha aj neutralizovať širokú škálu toxínov. Podporuje kardiovaskulárne zdravie.

▪️Kurkuma - Riedi a čistí krv.

▪️Olivový olej - Vďaka svojim antioxidačným vlastnostiam znižuje aktivitu krvných doštičiek.

▪️Harmanček - Potláča aktivitu krvných doštičiek a zabraňuje zrážaniu krvi.

▪️Horčica - Omega 3 a vitamín B6 znižujú viskozitu krvi, čistia obehový systém a posilňujú cievy.

▪️Mastné ryby - vďaka Omega 3 zlepšujú medzibunkový metabolizmus, čím zabraňujú trombóze.

▪️Zázvor - normalizuje krvný obeh. Znižuje krvný tlak a podporuje normálny prietok krvi. Obsahuje salicylát, prírodný analóg aspirínu.

#zdravie

#zdravie

mastodon - Link to source
Haha. I'm genuinely impressed with this idea, not just because it's simple in the brute force, but that unprompted repeated iteration like that could get AI to write shippable code. Notice I didn't call it "quality" code. I still think it would be a massive main function with nothing modularized, overly-lengthy comments at every section (which in itself isn't bad, but AI adds dashes and other comment formatting that take up space), and little bugs that are not accounted for. Heck, when AI built the phoneme editor (which was my first real "end to end vibe-coded" project), look at how many accessibility fundamentals it missed despite my custom instructions talking about WCAG and making sure it meets it. Clear to me there's also a fundamental "training tuning overrides custom instructions" problem, even though the AI checks to follow them, if any of the context doesn't match or fit, it ignores it. (Perhaps because I was writing a C++ program, it thought, WCAG doesn't apply!)
'Ralph Wiggum' loop prompts Claude to vibe-clone commercial software for $10 an hour
theregister.com/2026/01/27/ral…

'Ralph Wiggum' loop prompts Claude to vibe-clone commercial software for $10 an hour

Feature: Developer behind it is sick with worry he might have changed software development in nasty ways
Simon Sharwood (The Register)

mastodon - Link to source

France is rolling out Visio, a homegrown secure videoconferencing platform, to all government employees by 2027.

The move aims to replace American tools like Teams, Zoom and Webex that currently fragment public administration communications and create security vulnerabilities.

The platform already has 40,000 regular users and is being deployed to 200,000 agents. Major institutions like CNRS are switching over this quarter, with CNRS replacing Zoom for its 34,000 staff and 120,000 affiliated researchers by late March.

Visio runs on French sovereign cloud infrastructure certified by ANSSI, uses AI transcription technology from French startup Pyannote, and will add real-time subtitling from French AI lab Kyutai by summer 2026. Beyond security and digital sovereignty, the switch generates real savings of about 1 million euros per year for every 100,000 users leaving paid license solutions.

Minister David Amiel frames this as essential to protecting sensitive government data and scientific exchanges from exposure to non-European actors while supporting French tech companies.

numerique.gouv.fr/sinformer/es… #France #Greenland #MAGA #DonaldTrump #tarrifs #France #Google #MicrosofTeams

lemmus.org/post/19676136

#Greenland #Minneapolis #ICE

numerique.gouv.fr

numerique.gouv.fr
#google #france #MAGA #ice #donaldtrump #greenland #tarrifs #minneapolis #microsofteams
This entry was edited (1 day ago)
in reply to R. Scott (i47i)

mastodon - Link to source

R. Scott (i47i)

2/3

THE PROVEN TRACK RECORD:

France isn't experimenting—they've been doing this successfully for 20 years. The French Gendarmerie (national police, 100,000+ employees) pioneered this approach:

TIMELINE:
• 2005: Migrated from MS Office to OpenOffice
• 2008: Started Ubuntu desktop deployment (GendBuntu)
• 2014: Majority migration complete
• 2024: 97% of workstations running Linux (103,164 computers!)

FINANCIAL IMPACT:
• €2 million/year in licensing cost savings
• Additional savings from eliminating 4,500 servers
• Total 2004-2008: ~€50 million saved

STRATEGIC INVESTMENT:
In October 2025, France became the FIRST national government to officially partner with the Matrix Foundation—not just using it, but funding its development and participating in strategic decisions. This ensures the protocol evolves to meet European government needs.

So when we say France is "building bundles," they're really packaging, hardening, and supporting mature upstream FOSS (Linux, PostgreSQL, Matrix, etc.) with French hosting, governance, and integration—not reinventing everything from scratch.

GendBuntu: en.wikipedia.org/wiki/GendBunt…

Gendarmerie case study: canonical.com/blog/la-gendarme…

#Matrix
(2/3)


Linux distribution for French police

Contributors to Wikimedia projects (Wikimedia Foundation, Inc.)
#matrix
This entry was edited (1 day ago)
in reply to R. Scott (i47i)

mastodon - Link to source

R. Scott (i47i)

3/3

HOW EASY IS IT TO MOVE FROM MICROSOFT?

TECHNICALLY: Very feasible. Strong FOSS alternatives exist for everything:
Windows → Linux (Ubuntu, Debian, Fedora)

Office → OnlyOffice, LibreOffice

Exchange/Teams → Matrix/Element, Nextcloud

SQL Server → PostgreSQL, MariaDB

Benefits: No per-seat licenses, data sovereignty, transparent security, longer hardware life, no forced obsolescence.

THE REAL CHALLENGE: Organizational, not technical

Legacy Windows-only apps & VBA macros (need rewriting or VMs)

User retraining & change management (people lose muscle memory)

Political will & leadership commitment (critical!)

External partner expectations (.docx, Outlook, Teams)

SUCCESS FACTORS (proven by Lyon & Gendarmerie):
• Strong political backing at highest levels
• Adequate budget & realistic timeline
• Comprehensive training programs
• Willingness to maintain hybrid systems during transition
• Local/regional procurement (Lyon: 100% French contractors)

CURRENT MOMENTUM:
Denmark, Germany (Schleswig-Holstein), Netherlands, Italy, and Slovenia are all pursuing similar digital sovereignty initiatives through FOSS

Bottom line: #France proves that digital sovereignty through open source works at massive scale (103K+ workstations). They're not reinventing wheels—they're making smart use of mature, proven technology with European hosting and governance.

Lyon Register article: theregister.com/2025/06/26/lyo…

#OpenSource #DigitalSovereignty #Linux #FOSS #France #Lyon #PublicSector #Ubuntu #Matrix #GendBuntu #Europe #Microsoft

(3/3)


French city of Lyon ditching Microsoft for open source office and collab tools

: Ingredients of future software salade Lyonnaise will include Linux, PostgreSQL, and OnlyOffice
Simon Sharwood (The Register)
#linux #foss #matrix #opensource #microsoft #france #ubuntu #europe #digitalsovereignty #publicsector #lyon #gendbuntu
This entry was edited (1 day ago)

mastodon - Link to source

Another reason why I wish more appliances still had physical buttons and knobs, aside from the obvious tactile one, is that it's an easy way for you to have a personal default setting.

My countertop dishwasher for example has only touch buttons. They are a pain to trigger, especially with wet hands, and it always starts at the energy- and water-saving programme, so helpfully named "1", which takes about 2 hours. Whereas I prefer the short programme, which takes only 30 minutes, since it's the only programme that doesn't include a drying cycle, and it usually cleans well-enough. I usually prefer to just open the door afterwards, pull the rack out on top of it, and let it air-dry while its contents are still hot. It's programme 3 though, so I'll have to press that programme-select button twice. every... single... time...

Whereas if the programme-select was just a physical knob, I could just leave it on programme 3. I also like to always have it start with a 5-minute steam, which could also just be a physical switch, instead of a non-tactile area I have to press every time. Hell, make it a knob that sets the duration of the steam session.

Even better; instead of mildly different predefined programmes, give me a whole bunch of knobs for pre-wash temperature and duration, main programme temperature and duration, rinse cycle. Put a nice, user-replaceable, LED above each of them that indicates which cycle it's currently in, and one shared countdown timer display, and I'm a happy camper.

#FiXatoRants #appliances #accessibility #a11y #kitchenAppliances #kitchen #DearDesigner #knobhead

#a11y #Accessibility #kitchen #fixatorants #appliances #kitchenappliances #deardesigner #knobhead

mastodon - Link to source
Here's an interesting thought to ponder. Flying is generally regarded as the safest transport method for human transportation. However, the modern jetliner flies at altitudes that under normal circumstances, humans could never survive. It's only thanks to things such as cabin pressurization, that even allows that to work. But I wonder, who was the first person or group of people that decided that it would even be possible to pressurize a cabin and allow humans to fly at much much higher altitudes? How did the idea that flying it altitudes above 30,000 feet would even be possible? Just some random thoughts I had as I enjoy my evening.

mastodon - Link to source
Alright, today I'm open to new names for NV Speech Player. I don't need to ask for permission to rename since it's GPLV2, it's actually a bigger problem if my fork is confused with the official one.
So I intend to break all my links. (I'll update them to the new files in my places on posts.)
SpeechPlayer-2025-V3 will become the "defacto" version, with multilingual support removed. It will be renamed to just SpeechPlayer-2025 after.
This will keep distinction between the two flavors and avoid people from thinking the one I'm forking is like the official NVAccess one.
Name ideas so far that sound not bad:
Pulse Player, Sonant Player, Voxera Player
This entry was edited (1 day ago)
in reply to Nick Giannak III

mastodon - Link to source

Tamas G

@nick hmm. "Official" though means inheriting expectations about support, review, release cadence, and compatibility. A fork lets me move fast, break/reshape things, and make opinionated choices (like big sound-model changes) without people assuming NV Access signed off. If it sits under an NV Access org or looks "official," users may read that as endorsement. That can be uncomfortable for NV Access if they’re not actively resourcing it. We're already changing core synthesis behavior (waveform, packs, tooling). That’s exactly the point where "new project, with credit" is usually healthier than "official continuation."
@Nick Giannak III
in reply to James Scholes

mastodon - Link to source

Tamas G

see I wasn't really either, until I realized that I've now reshaped all three stages of the pipeline. The player (wave generator) itself, the IPA rules engine, and the way we talk to phonemizers (a bit loosened from Espeak's coupling.) If the fork diverged less keeping the "NV" name is OK, but with the trademark thing I didn't even know NVAccess has and this I think I got a bit sold on it.
This entry was edited (1 day ago)
⇧