Sea Cucumbers Poop and Breathe Through a Cloaca. Wouldn't that make farting a bit tricky? They can also eject their internal organs to scare off predators: animals.howstuffworks.com/mari…
The soft, cylindrical sea cucumber looks like a vegetable — and in some countries, it's a delicacy because of its nutritional value and health benefits.
Eww, sorry, but it sounds a bit disgusting. Also, they seem to not have a properly developed system. And if they look like cucumbers, I would laugh, and probably, never look at cucumbers the same way, ever, again.
News for Copilot haters / AI haters in general: The Copilot "offer" UI that was added to Github last month can now be disabled. If you go to Settings->Copilot there is now a new "Visibility" setting available to non-Copilot users, in my testing setting it to "disable" removes the Copilot box in the top toolbar and the (fake— clicking it just takes you to a signup page) Copilot "search box" on the front page.
@leo this is what proves that the APK was indeed built from the very same source it claims. Cross-updates are possible when the same signing key was used in those places – which implies that the app must be set up for RB at F-Droid as well, as otherwise F-Droid uses a key they generated (and then, cross-updates are not possible).
Signing ensures that updates are only accepted when the same key was used, where only the owner knows the credentials for.
@leo It's not cross-signing; those entries with identical signatures are signed by the same key (here, the one of the NewPipe team & signed by them, so same APK).
For NewPipe, I'd recommend installing it from their repo, for faster updates (YT breaks its own stuff frequently, in effect breaking the app; their own repo is where the adjusted APK will show up first; F-Droid's repo usually takes 2..5 days longer; IzzyOnDroid just a few hours, so that would be fine as well, depending on your needs).
A comment in an article about prototyping in Rust [1] led me to this ~11 year old article by a programmer who decided to use Java for all non-throwaway programming: teamten.com/lawrence/writings/…
I think java isn't as dominant now as it was when that article was written, but the article's arguments for prioritizing programming in the large resonate with me. But I want my default language to be Rust, because of its added guardrails for safety and correctness.
I made a conscious decision at some point in my early 30s that I would refuse to become set in my ways when it came to programming language and tech stack in general, that I would never stop learning new things and trying to choose the best tool for every job, not just the one I was comfortable with. At that point, my default language had been Python for a bit over a decade, but I was already aware of its limitations for desktop apps, particularly in terms of package size.
I had already paid a price for that limitation in 2007-2008 by rewriting a substantial Python codebase in Lua, only to discover that, at scale, the same fundamental limitation applies; to really optimize total package size, one needs static analysis and fine-grained dead code elimination, which are intractable in dynamic languages like Python or Lua. Not that there was necessarily a better choice in 2008; doing the whole thing in C++ was off the table, and Native Image for Java didn't yet exist.
And by the early 2010s, when I was in my early 30s, the future was supposedly going to be all about native mobile and/or client-heavy web apps, where small size and closeness to the platform are important. For a while I did iOS (and Mac) apps in Lua, using a two-way Lua/ObjC bridge called Wax. But at some point I decided I needed to make the jump to static languages. I wasn't going to become limited as a generalist developer because I was too wedded to Python or dynamic languages in general.
My first major project developed under this new mindset was a client-side web app I did in the first half of 2013. I wrote it in JavaScript, but I used the Google Closure Compiler in advanced mode, with type annotations (in doc comments, ugh), all the optimizations that compiler could do, and the Closure Library. Aside from that library, I ported one third-party dependency to Closure-flavored JS and wrote the rest myself. The final bundle size was ~250K uncompressed. I considered this a triumph.
Of course, I was short-sighted, over-optimizing for one dimension (runtime efficiency). Even while I continued to maintain that application over the next few years, I rarely updated the Closure compiler or library. And, in the decade plus since, the JS community at large has gone in a different direction.
One of my projects in the latter half of 2013 was an Android app written directly in Java, and by late 2014, I was looking at various ways to write cross-platform code in one language and compile it to native code on iOS and JVM/Dalvik bytecode on Android. The top two contenders for me were J2ObjC, another Google internal tool that they had open-sourced, and an obscure proprietary compiler called RemObjects Elements. Remember, I wanted to optimize for small size and closeness to the platform.
In 2015, the biggest project that I shipped that year was a desktop app (some of my blind followers can probably guess which one). I wanted it to have as native a UI as possible, only using web views for document content. As I was trying to choose the best tool for the job and not just the most comfortable one, I was going to use the SWT GUI toolkit for Java, which had good accessibility on both Windows and macOS. I was determined to have a no-compromise UX while sharing code across platforms.
So I figured I'd write the whole app in Java, using a lightweight third-party JVM implementation called Avian, that could even compile JVM bytecode ahead of time to a stand-alone executable. I was finally going to have it all, even in a desktop app: native-feeling UI, small size, and instant startup time, across platforms. Yes, I'd have to write in painfully verbose Java, but it would be so worth it. That was the plan, anyway.
But I couldn't make myself push through it. The first sign of trouble was when I found myself having to either adapt an existing JNI binding for the libcurl HTTP client, or write my own (I don't remember which), so I could have an HTTP client while keeping executable size down. And I knew I was going to have to write bindings for more native stuff. I had already done plenty of that for Lua in 2007-08, and I didn't want to do more JNI glue code. I missed good old Python and ctypes.
I also had some existing Python code, which ran on the server in a previous implementation of the product I was rewriting, but now I wanted to run it on the user's desktop so that functionality could be available offline. And I was just all around more comfortable with Python and its ecosystem than I was with the JVM ecosystem.
So I basically restarted the project, in Python. It felt good to be using Twisted, requests, and other familiar Python libraries again, not to mention my own existing Python code. But I was determined to still use SWT for the UI. So this app was a mongrel; I embedded the Avian JVM via a Python package called pyjnius, and used that just to bring in SWT. Yes, it was a mess. But I managed to deliver the native-feeling UI across Windows and Mac, with minimal platform-specific code.
But that project felt to me like a shameful retreat from the full set of goals I had set for it, goals that, in retrospect, I realize didn't really matter to anyone else, not just users, but the others at my company. Still, I felt that my plan B using Python was a capitulation to the requirement to unblock my productivity and get the thing out quickly. I don't think I stopped to reconsider the priorities that had led me to try doing the whole thing in Java.
BTW, that desktop app went into beta in June 2015, a month or so after I had started over in Python. The Windows package size for the latest version of that app is ~44 MB uncompressed, or ~12 MB compressed with 7-Zip. That's not as bad as an Electron app today, but it was still shameful to me at the time.
Like I said, I hadn't really reconsidered my priorities or pondered what lessons to take from the failure of my original approach to that project. For my big 2016 project, a consumer app spanning desktop, mobile, TV set-top boxes (initially the newly accessible Apple TV), and, we assumed, eventually a client-side web version for Chromebooks, I was going to double down on runtime efficiency (especially small size), closeness to the platforms, and no-compromise native UI.
So I decided to write the cross-platform non-UI code in Java. That would be native to Android, for the Apple platforms I'd use J2ObjC, for Windows I'd use IKVM.NET (a JVM implementation on top of .NET), for the eventual web port (which never happened), I was planning to use Google Web Toolkit or maybe Google's new j2cl if it was ready in time. For the UI, I would use the native language and toolkit of each platform, or maybe SWT again on Windows and Mac.
What I actually did for the UI was reuse a bunch of code from the previous platform-specific versions of this app that I was trying to unify. The previous Android version was pure Java (that was the late 2013 project from earlier in the thread). The rest was compromises on my pure vision: Lua and wax for the iOS, Mac, and Apple TV versions (see earlier), and for Windows, a mongrel of .NET and Windows Forms (I had started on that in 2014) plus some of the Lua code from 2007-08.
I did actually get to reuse some non-UI code across platforms, including the audio player and some code for managing downloaded content and synchronizing the user's playback position with the server. But another compromise, the big one, was this: the Ui was a hybrid between native and server-rendered web views. There was just no other way I was going to ship the damn thing. And a few features remained exclusive to the Windows version (the original).
And still, after the compromises of this 2016 project and the one before, I hadn't learned my lesson: the inevitability of tradeoffs and the importance of picking the right ones. I think I saw the compromises of both projects as simply a failure to be perfectly productive.
I love open source, and I want young people to know there’s a career path outside of #FAANG. Open source can be financially sustainable—it just gets super hard if one of your key goals is making your investors even richer. #Conversations_im is about the same age as #Matrix. I never took VC funding, and I’m doing fine.
WordPress Credit Card Skimmers Evade Detection by Injecting Themselves into Database Tables
Cybersecurity researchers are warning of a new stealthy credit card skimmer campaign that targets #WordPress e-commerce checkout pages by inserting malicious JavaScript code into a database table associated with the content management system (CMS).
Dlouhé roky mám na blogu vyhledávání pomocí Google. Párkrát jsem sice narazil na to, že mi článek, o kterém jsem stoprocentně věděl, že na blogu je, nenašlo, ale nevěnoval jsem tomu větší pozornost. Až teď, při zkoumání proč mi tak strašně poklesla návštěvnost, jsem zjistil šokující pravdu. Google mě cenzuruje!
O pokusech něco s tím udělat bude další článek, zatím ale dělám první opatření a přecházím s vyhledáváním na blogu k DuckDuckGo.
Dlouhé roky tu mám vyhledávání pomocí Google. Párkrát jsem sice narazil na to, že mi článek, o kterém jsem stoprocentně věděl, že na blogu je, nenašl(...)
Tady bych asi nutně nemával slovem cenzura. Google je poslední dobou hodně pedantickej. Máte například všechny ty stránky v nějakém sitemap.xml?
Jinak je rozumnější duckduckgo, ale je třeba vědět, že jen ukazuje výsledky z Bingu (ořezané o různé šmírovací doplňky). Takže pokud chcete odladit výsledky tam, musíte přes bing.com/webmasters .
Jinak doporučím třetí variantu, a tou je searxng.cz od @archos@mastodon.arch-linux.cz to konsoliduje všechny možné známe vyhledávače, včetně googlu, seznamu atd...
Back in December I got a desperate email from this person. A woman who said her Instagram had been hacked and since she found my contact info in the app she mailed me and asked for help.
Hahaha, what a story. It's funny and sad at the same time though. Someone taking the effort to dig and investigate, but resulting in totally incorrect conclusions. That must have been frustrating for both.
True, the distance is too big in these cases. So many people that can browse the web, but still lack the basic understanding of a computer or their operating system. You already tried to simplify things, but they need to take a few more steps first to reach you, to understand it. Not much that you can do, and that is also fine.
@SonnyBonds haha, I would presume a not insignificant number. But a lot of these emails I get because they find my email in the curl license, independently of the domain name in the email.
Someone stole and adapted my online CV many years ago as part of some fraud scheme, and I had at least one deperate Swedish civil servant telephone me trying to get me to admit that I could speak Swedish fluently and that I had somehow scammed her and others...
There could be major computer system failures on January 19, 2038 at exactly 04:14 a.m. and 08 seconds CET. (03:14 UTC)
Some systems are said not to be able to process this time. A counter overflow occurs and the date automatically jumps to December 13, 1901. Similar to the “Millennium Bug”, the extent of the Year-2038-Problem cannot be predicted.
Attention! Il risque d'y avoir des nouveaux arrivants sur Mastodon ces prochains jours.
Donc pendant quelques jours, ont fait semblant d'être des gens normaux, on parle pas de vélo, de Debian, de flux RSS, et de comment programmer sa Rassberry en C+…
Sorry Daniel. The context of me contacting you is the users in the linked discussion are writing something to do with curl. Instead of playing explain things to each other i thought why not ask the original developer of curl.
Since asking you earlier someone from Developer Relations is very angry at me. Just disregard my earlier toot. Sorry.
Tak, 9 měsíců trvalo rušení FB účtu. Z jiných FB účtů kde jsem byl jako přítel sám sebe jsem hlídal že moje data zmizí. Úspěch jen částečný, bohužel, ale vzdávám to. Ale je to krásný pohled ...l WhatsApp také vlastní META ? Pořád hledám "kecálka" i pro rodinu, půlka jede Messenger půlka WhatsApp.
A nezkusil jsi matrix? Na MXchatu máme přemostěno i do jiných sítí. WhatsApp, Telegram, Messenger, Zrovna apliakce Element X myslím vypadá už hodně dobře.
Watch the official music video for "True Colors" by Cyndi LauperListen to Cyndi Lauper: https://CyndiLauper.lnk.to/_listenYDSubscribe to the official Cyndi L...
The Internet Archive has a collection of 460 episodes of the radio series Suspense, and it claims to be a collection of digitally restored episodes. The audio quality is quite good. archive.org/details/SUSPENSE_R…
Each of these shows is NON COPYRIGHTED and is currently in the PUBLIC DOMAIN. This Digitally Restored Collection represents thousands of hours of labor in...
Reading a published internal presentation from Nokia in the after iPhone launch (in 2007).
It says:
"Nokia needs to develop the touch UI to fight back. S60 should be focus. Maemo platform is critical strength due to openness. Nokia needs a Chief UI architect to re-energize Nokia’s UI innovation across platforms and businesses."
I have listened to over one thousand pieces of classical music in the last three months, and I have prepared a special playlist a little out of the ordinary.
😈😈FEELING EVIL, SHOW ME THE FORBIDDEN CLASSICAL😈😈
The reviews are in: "I thought classical music was boring, but this playlist gave me an anxiety disorder." "A disturbing glimpse into the dark heart of guys who write ballets about pretty princesses." "Who knew that a toccata could fall down the stairs?"
Featuring the talents of every Russian composer ever and also a few other guys from Hungary and France
for Lawful Evil people and/or people who want to feel impending doom on the double.The reviews are in: "I thought classical music was boring, but this playli...
BambuLab basically locks down their entire 3D printer ecosystem with this ridiculous cloud authorization system.
You want to print locally via your LAN? Sorry, the cloud needs to authorize your g-code first.
Want to use another slicer to send your job to the printer? Sorry, no.
Would it really still surprise anyone if DRM'd filaments are next on their agenda? Their printers are good, their prices are cheap, but please, stop supporting this company.
@AccessOn Would you consider mentioning the passing of Ed Potter on an upcoming edition of Access On? Before we had podcasts, Ed recorded Playback Magazine which, in many ways, was quite similar to the work that you do with your podcasts today. He provided listings of toll free numbers for ordering merchandise by phone and also provided listener-submitted reviews and demonstrations of products which were available at that time. Ed Potter, in that respect, was a true accessibility champion of his time. While he clearly lived a long and full life, I am still sad to learn of his passing but I'm grateful for his contributions to the blindness community.
David, thanks so much for posting this. I'm really sorry to read about Ed's passing. He was a really nice person and if you ever talked with him on the phone, he could really tell the stories.
@douglas2005 I heard about it from @tinygirl. Had I not read her posts about Ed's passing, I might have missed hearing about it, at least for some time and so I thank her for alerting all of us.
David, thanks so much for alerting us to Ed's passing. We will most certainly acknowledge his considerable contribution in the next episode. If you, or anyone else reading, would like to send in any memories of Ed and Playback magazine, we will gladly receive those contributions and air them in his honor.
If you can dream it we can sing it! Comment your song ideas below!All Links!https://linktr.ee/beatsbyaiSpotifyhttps://open.spotify.com/artist/2VL0G8nTevMkOCc...
For Playback Magazine fans, or fans of Coffee with Ed, I just found out that we lost Ed Potter at the age of 92 this last Tuesday. Obit follows. legacy.com/us/obituaries/legac…
Larry and I singed up for the Playback Pilot newsletter which came out in 1979l. he was testing to see if there was an interest in the audio magazine. We became friends and traded thousands of radio programs. We talked with him a couple of years ago and he was doing well except for a loss of hearing in one of his ears. I'm really sorry to hear this news. He was a long time good friend.
a hovorí to Heretik, to by som sa už asi aj zakopal..
Bente
in reply to Cat 🐈🥗 (D.Burch) • • •