post.hillenius.net is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
OK #Firefox users, this is a special request. I'm looking for someone with a high-end Raptor Lake machine that is experiencing instability in Firefox (or anything else for the matter). The best candidate is a CPU from the 13900* SKUs. K or not doesn't matter as long as it's one with the 8P+16E cores.
We have a potential workaround for one of the most common bugs of this CPU, but we need a broken machine to test it.
My point is that Mozilla is part of a far wider problem. The FOSS ecosystem is being exhausted by a combination of permissive licensing, dependence on centralized proprietary platforms, and corporate capture — Mozilla being a textbook case of the latter.
(MPL's weak copyleft is not GPL: corporations can build proprietary products on top without giving anything back)
Matter of principle: you say "help improving the software you use yourself, despite the company behind it"; I say "I refuse to help this Google-brained company, even at the expense of the quality of my daily browser".
#Firefox 151 Is Now Available for Download, This Is What’s New https://9to5linux.com/firefox-151-is-now-available-for-download-this-is-whats-new
Can anyone using #Linux use browser for #MicrosoftTeams calls with video?
I don't have a microslop account but am asked to join calls with a browser.
Audio works fine but I can't see anyone and they can't see me; despite my video working in preview before starting call.
Same here with #Firefox #ESR on #Debian stable. I don't have an account at MS. When I join an MS-Teams session, I can't see others and esp. not their presentation. I typically just ask everyone to change to #BBB, when possible. #BigBlueButton works relatively well.
Why flatpak? I just "sudo apt install chromium" from #Debian main 😉
https://tracker.debian.org/pkg/chromium
I'm mostly on #firefox, though, or even on #eww, when possible. #Chromium is the last resort.
#UnplugBigTech Tipp 14: Datenschutzfreundlicher Browser
Verabschiede dich von Google Chrome und wechsle zu einem Browser, der mehr Wert auf deine Privatsphäre legt, wie Firefox, LibreWolf oder Brave. Die blockieren/erschweren Tracking und bieten zusätzliche Funktionen, die verhindern, dass deine Surfgewohnheiten gesammelt und ausgewertet werden. Einen umfangreichen Vergleich mit Tabelle findet ihr am Ende vom ersten Teil der großen Browser-Serie. 👇
https://www.kuketz-blog.de/sichere-und-datenschutzfreundliche-browser-meine-empfehlungen-teil-1/
#Browserwechsel #Firefox #Brave #privacy #NoGoogle #NoTracking
423 Sicherheitslücken in einem Monat – darunter manche, die seit über 15 Jahren im Firefox-Code schlummerten. Das sollte nicht als KI-Erfolgsgeschichte gefeiert werden, sondern als Warnung: Wie viele davon wurden in dieser Zeit aktiv ausgenutzt, ohne dass es jemand bemerkt hat?
Und wer entscheidet, welche Organisationen Zugriff auf solche Werkzeuge bekommen? Anthropic. Ein privates Unternehmen legt fest, wer Software absichern darf und wer nicht. Das ist kein Sicherheitsgewinn – das ist eine neue Abhängigkeit.
/kuk
@yoasif You're absolutely right of course, but it's a matter of principle: I refuse to help at all a company that has lost its (open-source in spirit) way a long time ago...
Configuring the Firefox app has become pretty crazy: its privacy-related options -- just like its commercial clutter -- are all over the place, very much like Google does with its original Android system, hoping that you either give up or forget to turn off the occasional switch.
Is #demozzila a thing yet?
https://www.firefox.com/en-US/firefox/150.0/releasenotes/
#Firefox has cool new stuff!
I've also raised a bug with Firefox. Android has a specific permission which will allow the browser to access the *full* location metadata of a photo.
https://bugzilla.mozilla.org/show_bug.cgi?id=2029620
Not sure if it is worth raising bugs for Chrome and Samsung as well. Can't easily test them. If someone else wants to - please go ahead!