Unusual to have a new book on a Friday, but here it is. NO time to read today, and in fact I'm really struggling physically at the moment, but I love the series. The Simulacrum, back in June, was electrifying.
@lulu_bear I've done something muscular to my back. Honestly moving my right arm or just walking is crazily painful! NO idea how I did it. Slept awkward? I'm getting old!
Prosím vás, my si s @archos strašně moc vážíme jakékoli vaší podpory, ale pokud bude na výběr, jestli se chovat slušně nebo platit, myslím že mluvím za nás oba, bereme raději tu slušnost a lidské chování. Než podporovat něčí rasistické a homofobní výlevy, to si raději sami odpustíme nějaké kafe a investujeme to do provozu instance a serveru 😇
to já sem zase tudle jednoho týpka okřik, kdyz postoval obrazek lenina agitujícího dělníkům ... ono to bylo v kontextu že prej tagle vypadá když se u nich začne mluvit o politice. Ja mu k tomu napsal že lenin, cheguevara a jim podobní jsou "scum" a poslal mu k tomu obrázek z komixu likvidátor kde kydlí kulometem bolševiky .... no bloknul mě. Ale zpráva byla doručena. Třeba se mu to časem rozleží v hlavě a přestane blbnout. Protože politický zápal se dá vyjádřit i třeba obrázkem Johna Lennona nebo Ghandiho ...
@stepan tahle pivní kultura je společná všem individuím. Chtěl jsem ti koupit pivo, ale,... Pozval bych tě, ale... Přispěl bych, ale když ty píšeš pro/spolupracuješ s... Už jsem dost starej, abych tomu nevěřil a ještě starší, abych se tím trápil. Raději svou hrdost, než cizí peníze za ni
I did this A critical remote code execution vulnerability exists in the varexpand function due to a combination of insecure input handling, unsafe memory operations, and improper execution of user-...
Given that #curl is such a prominent project and you are very present in the media arguing against the quality of LLM generated issue reports, I fear the cohort of misguided "AI" evangelists will make it a sport to "prove you wrong".
why do these people keep doing this? What's their end goal with this? What kind of outcome do they actually expect, which I assume must be radically different from what you did? "Oh hey thanks for reporting this vulnerability, here's your $1000 for finding it?"
@grishka I wish I understood them/people better so that I could answer this rather important question. In this particular case, they are not even looking for a bug-bounty so it can basically just be either malicious DoS-style or ignorance/stupidity.
Welcome Yes, I'm using the latest major release or the current development version. These are the only supported versions. Yes, I've searched similar issues and discussions on GitHub and didn't fin...
Welcome Yes, I'm using the latest major release or the current development version. These are the only supported versions. Yes, I've searched similar issues and discussions on GitHub and didn't fin...
@sunny I'm split between maniacal laugh and utter desperation when reading this, it's like they want to waste as much time as possible from everyone involved.
@kami_kadse Right. In effect, slow-to-respond projects will soon gradually get their issue trackers filled up with AI slop like this. Similar to spiderweb and dust in an abandoned house.
This kind of crap makes me so incredibly angry that I cannot even put it into words.
The shitty bug reports with missing information and problem descriptions along the lines of "it broken, plz fix, kthxbai" we maintainers often get are bad enough as is, as are the entitled assholes. But no, now we get put through a new circle of hell thanks to this LLM bullshit abused by script kiddies and trolls. This crap needs to die in a fire, and yesterday.
@thedoctor @foosel in my case, they are still at a single-digit percent of the total number of issues I deal with during any normal week. Not sure exactly how I would quantify "substantial", but maybe two or three times the current volume.
@thedoctor My project is thankfully also too small to have this as a general issue already, but I'm pretty sure that if things keep going like now that will change soon :/
Welcome Yes, I'm using the latest major release or the current development version. These are the only supported versions. Yes, I've searched similar issues and discussions on GitHub and didn't fin...
✍️🖼 Na tomhle plakátu od ilustrátora Jana Hoška najdete časté návštěvníky krmítek.🐦 Pokud vám určování některých druhů dělá problém, můžete ho použít jako "tahák".😃
Ptačí hodinka je název každoročního sčítání ptaků na krmítkách pro širokou veřejnost, které organizuje Česká společnost ornitologická na začátku ledna.
@archos Nešikovný záběr. Vzadu jsou dvě vany řízků, trhaný hovězí krk, v popředí chorizo a něco k tomu, mimo záběr něco masožravýho, co si už nepamatuju, neboť jsem kontroloval hlavně ty řízečky na severní straně...😅
Hele nebudeme přece svádět, tu králíčí párty s mrkvičkou na fotografy. 😂 Ne já jsem si myslel, že pán vzadu to jistí. Je to malinko rozmazané, ale řízky vidím.
How Learning Tibetan Changed the Way I Think: Translator Estefania Duque shares her journey studying Tibetan, revealing how language shapes the mind, influences perspective, and offers spiritual inspiration. lionsroar.com/learning-tibetan…
"Have you ever wondered what people used to name their dogs back in medieval times?
"Lucky for us, there was this book written back in the 15th century that included over 1,000 names that were considered to be suitable for dogs," Lexi says.
After reading the entire book, she shared some of her favorite names, which included Garlik, Nosewise, Synfull, Salmon, Mustarde, Bryan, and also Nise and Noty, Filthe, Dredefull, and Arguement.
The book, which featured about 1,065 dog names that people deemed appropriate back then, was recently sold into a closed private collection.
The Smithsonian Magazine said Sturdy, Whitefoot, Hardy, Jakke, Bo, Terri, Troy, Nosewise, Amiable, Nameles, Clenche, Bragge, Ringwood and Holdfast were all also popular dog names
A 700-year-old book, recently sold into a closed private collection, revealed the most-popular dog names in the Middle Ages, and some may surprise you.
A Hungarian #translation is now available for #FeatherWiki thanks to the fantastic @erion! They even included translations for all extensions that display text 🤯 Thank you so much!
Find the download on the Downloads page: feather.wiki/?page=downloads And the translated extensions are indicated on the affected extension pages.
If you want to get your language added to Feather Wiki, you can also contribute a translation! Instructions can be found at feather.wiki/?page=translation
Storm Dragon pushed changes to the testing branch of the audiogame-manager project Updated wineserver calls to use the wine determined in variable form. Installers may be broken for now.
Conservatives love to accuse progressive politicians and premiers of being spendthrifts. But as the record clearly shows, they're no better — and often far worse — when it comes to keeping government spending in check #Conservatives #Canada #cdnpolinationalobserver.com/2024/12/0…
My financial advisor once showed me a chart that showed the history of the Canadian national debt. It was overlaid with red and blue sections to show when the Liberals and Conservatives were in power. The national debt always increased under a Conservative government. Always.
Brevísimo hilo de máquinas para cortar queso en #suiza. Estoy maravillado en verdad por la diversidad de #queso, que conlleva la consecuente diversidad de máquinas para cortarlo. Y estas son solamente las que pude ver dentro de una casa normal. No se diga ya en las queserías
@federicomena NO LO HACEN! eso estaba observando. Pensaba que el metro de la #cdmx tomaba como referencia a este, del cuál entiendo que es medio hermano, pero sí me sorprendió ese detallito.
Hey, librsvg question, the svg file mentioned in my comment here: gitlab.com/inkscape/inkscape/-… shows a green semi-circle in librsvg, firefox, safari, etc. But a full green circle in Inkscape.
Part of me can't quite believe that the svg spec asks that symbols be pre-clipped to the page boundaries before being transformed into their use object's location.
Such elements by default clip to the viewport. In your case, I think the symbol's width/height default to auto/100%, and since the referencing <use> does not specify a width/height of its own, it uses the current viewport, i.e. the whole SVG.
I think it's best if symbols actually include a viewBox to set their aspect ratio and coordinate system, and then the <use> actually has a width/height.
iirc a symbol behaves exactly like an svg non-toplevel element except that it allows for refX and refY - hence the clipping around the viewport by default
Our board member @joost_schouppe had the privilege to receive for us the first ever Impact Award at the Geospatial Awards organized by FLAGIS and AM/FM-GIS BeLux, the two main GIS user organizations in Belgium.
"[Joost sees] it as a recognition of how our data and project has become ubiquitous in the Belgian GIS world."
I was very honored to receive the Impact Award in the name of OSM Belgium today! I see it as a recognition of how our data and project has become ubiquitous in…
My friends, It is with great sadness and heavy hearts that we share the news that John Panarese of Mac For the Blind has passed away. For so many of us, John was more than just a trainer or mentor—he was a source of inspiration, a steadfast friend, and a beacon of passion and dedication. To me he was a great friend, my brother from another mother, my mentor, someone i could talk to for advice.
Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webinars across mobile, desktop, and room systems.
What does it take to challenge stereotypes, break barriers, and build a movement that redefines opportunity for professionals with disabilities? For Mike Hess, founder of BIT, it all began with a first-grade eye exam that changed the course of his life.
In VoyageDenver Magazine’s Inspiring Stories series, Mike shares his journey in his own words, offering an honest & heartfelt look at the challenges, triumphs, and lessons that shaped him.
Google’s latest advancement, Gemini 2.0 Flash, is making waves in the tech community, and for good reason. This innovative feature is set to roll out to the
The NYPD and FBI offered up a joint $60,000 reward during the manhunt for UnitedHealthcare CEO’s killer — but it wasn’t immediately clear if anyone would get the cash now an arres…
We're starting a sprint to look at all the issues preventing #ReproducibleBuilds in all the apps we ship. Most of the issues are simple fixes in the upstream code, like unsorted outputs or timestamps included in the build. You can help make the #FreeSoftware #Android ecosystem be more reproducible! See the failures here and help us report them upstream: verification.f-droid.org/faile…
I'd also suggest looking at and linking to @IzzyOnDroid's great documentation for app devs on what to watch for: gitlab.com/IzzyOnDroid/repo/-/…, which is much more helpful than just creating upstream issues to say "broken, please fix" without detailed steps.
(By the way, if someone wants to try building Reproducible Builds themselves, I'd strongly suggest looking at gitlab.com/IzzyOnDroid/repo/-/…, which powers the #IzzyOnDroid #ReproducibleBuild system, covering over 30% of IoDs 1223 apps already)
Indeed. Merely reporting failures upstream is easy. And whilst sometimes fixes can also be quite easy, some expertise is often required to figure out what to do about observed differences.
Good documentation can help a lot here. As is having people with RB expertise, like @IzzyOnDroid, helping developers to debug issues :)
You also need people to develop and maintain the RB tooling and workarounds everything relies on. And to report things like compiler bugs to Google. Which so far has been pretty much just me.
Checklist I am able to reproduce the bug with the latest version given here: CLICK THIS LINK. I made sure that there are no existing issues - open or closed - which I could contribute my informatio...
Yes, there is plenty of low hanging fruit like embedded timestamps or nondeterministic ordering. Many apps are already easily reproducible or require only small fixes.
But the ecosystem is constantly moving: old toolchain and dependency bugs get fixed, but new ones keep popping up.
Reproducible Builds are not just an item on a checklist, something you (ask upstreams to) enable and then you're done. Especially when it's a hard requirement like at F-Droid where new builds no longer being reproducible means users will not be able to get updates.
It's an ongoing process involving not just upstream app developers, but also maintainers of repositories, clients, and rebuilders; those involved in outreach and writing documentation; developers and maintainers of tooling, toolchains, and dependencies. And often requires a lot of collaborative debugging :)
It requires teamwork and an ongoing commitment to investigate and fix new issues when they pop up.
I know you don't like to link to us as you don't want to "endorse" 3rd-party repos – but maybe it's time you forget your grudges, and to accept the expertise you're offered? After all, aren't your RBs using our tools (as our repo still uses yours)? Haven't we adopted from each other in both directions? We have no issues linking to you (the wiki @SylvieLorxu just mentioned does that, for example). Your turn now 😉
@IzzyOnDroid @SylvieLorxu I would be happy to see your repo become #FreeSoftware! As you well know, F-Droid only endorses verifiable free software projects.
It is also great to see all your work on #ReproducibleBuilds. We are continuing to build upon our years of effort there. Our approach is focused on identifying issues and getting things fixed upstream as much as possible. Then devs do not need to use any special tools to achieve reproducible builds.
@S1m now, that's not possible with @fdroidorg anymore; support for this was broken for fdroidserver in January, unfortunately. It's still possible with IzzyOnDroid, though, as we used a different patch (and yes, we have at least 1 app which uses key rotation (Occtax), and our documentation recommends that for key changes). Though we don't need that for RBs, as RB verification runs on a separate track here, so we can "make apps RB" even after they have been listed here for a while. @SylvieLorxu
@IzzyOnDroid @S1m @SylvieLorxu we aim to support signer key rotation. We would greatly appreciate it if those who know about bugs would file them in our issue tracker so that we can track them. Also, we welcome contributions there.
@eighthave @S1m @SylvieLorxu Good to know your stance on this has changed now – back in April, when we warned about breaking support for key rotation (it was still supported before that MR was merged), it was not important: gitlab.com/fdroid/fdroidserver…
Had you accepted our contributions back then, APKs with rotated keys would still work with fdroidserver (as they do at IzzyOnDroid, where those contributions have been implemented).
@IzzyOnDroid @S1m @SylvieLorxu The issue you are pointing to is only for APKs that have APKv1 signatures. That means apps with minSdkVersion less than 24 (Android 6 and older). That is devices that have not had an OS update since 2015. That is maybe a couple of percent of Android users? So I decided my limited time was better spent elsewhere rather than sinking days of work to supporting a small percentage of apps on a tiny percentage of devices. That said, I welcome contributions.
@eighthave @S1m @SylvieLorxu I won't delve into that again, Hans, so let's stop that here please. You've spent 2 weeks of that valuable time on an alternative implementation back then instead of accepting contributions offered to you by experts (not mine, I'm not expert in that area). And sorry, but our time is limited, too, so we cannot sink days into fixing that again for you 😉
You might want to mention that unlike the rebuilders run by e.g. @IzzyOnDroid, which verify APKs built and published by upstreams, in a build environment customised for that, your linked verification server reproduces F-Droid's builds (which may be patched), using F-Droid's build environment. That's kind of important when you're going to report issues upstream.
Na podíl ze zisku mají nárok všichni, od uklízečky po vývojáře. Ze speciálního účtu mohli zaměstnanci vybrat peníze až po pěti letech. Dostali je ale dřív.
'"We want to help people, we don't want to punish people," the premier said at a Queen's Park press conference where he announced an amendment to the Trespass to Property Act that would mean fines of up to $10,000 or up to six months in prison for repeat offenders.' www.thestar.com/politics/pro...
This fixes a minor bug in Catima 2.34.0 where selecting an "invalid" pkpass file (corrupted/not actually pkpass) after choosing to open from Pkpass would cause the app to crash. Now, you just get a little message stating the file could not be read instead.
It's that time of the year again when I reflect on my journey with Android. Back in 2012, I decided to purchase my first Android phone and never looked back.
This is very well done and informative. The only thing that comes to mind for me is that 2024 is the year Eloquence is truly dying. Lots of modern chips are losing the ability to run 32-bit apps at all, so new phones like the S24 and OnePlus 12 are not going to get Eloquence.
This article also led me to the opinion piece on Samsung's Talkback, which brings me to my own saga. I have two Samsung phones running Android 12 and 13, and I've force-removed Samsung Talkback and replaced it with Google's version. Lately, I've been noticing that Talkback crashes in certain apps or webviews, and the crash is bad enough to require a second s'creen reader to fix it. The first time it happened, I had to get very painful video assistance to authorize ADB and fix it. This is the user experience people get if they want to break away from Samsung Talkback now. With two of my phones doing it and at least one other report of the same thing on a modern phone, we are looking at a serious setback to running the latest Talkback. Between this and the incredible software bloat, I'm now actively recommending people avoid Samsung. I'm sure some other phone manufacturor will adopt a similar update policy next year, and Pixels are nothing to sneeze at either.
@simon Absolutely right. We have the same issue on the S24 Ultra, and Google TalkBack consistently crashes while performing certain tasks whereas Samsung TalkBack doesn't. Samsung's accessibility efforts are really faltering.
They are, but I'm not sure whether to blame Google or Samsung for the crashing issue. Either way, it's frustrating, and Samsung could solve this by just bowing out and going back to Google Talkback. If they want to make contributions to it ... well it's open-source, right?
@simon Google tells users that installing Google TalkBack on Samsung phones might generate serious issues, and Samsung is silent on the matter. But as you rightly said, this TalkBack separation should stop on the part of Samsung.
@JamminJerry My guess: This is just an inertia problem. Samsung doesn't really seem interested in making meaningful changes to Talkback anymore, so once in a while someone merges in existing changes and releases an update. Switching to Google's version isn't necessarily a bad idea, it just takes work and system-level changes and they just can't be bothered.
@simon @JamminJerry Nicely put. Samsung apparently has no interest in pursuing accessibility efforts, so they should let go of this ruinous TalkBack separation.
@simon Pixels are great. I don't regret getting mine and switching from Samsung and I never thought I'd do that. Nice just having one TalkBack among other software. I wonder if Samsung'll lose other longtime users with that behavior. They should just give us Google's TalkBack!
"I left the Settings app running" shouldn't be a laptop battery killer.
Anyone interested in significantly lowering power consumption of the #GNOME Settings (control center) app when idling on the WiFi, Bluetooth or Sound panels? My suggestion is to throttle the hell out of it when the window is not in focus: gitlab.gnome.org/GNOME/gnome-c… This is not an unheard of idea, it's been done in the gaming industry (I saw #PathOfExile doing exactly that, when I last played… a long time ago)
Jiří Pavlík
in reply to Michal Špondr • • •