bnpl markets got exposed by john oliver a few months ago and the result of blue collar america learning that deregulated 2008/style lending was back was not good.
Fedi needs a way to reply but intentionally break the thread and start a new one. I think that would be valuable. It's not even a protocol thing, it's just something the UIs need to implement.
I just tried this out with one of my custom soundscapes and it worked perfectly. Thank you so much for this! I like the new app, but I was missing some of the soundscapes I created on desktop. No more! Now all my sounds are with me on mobile. :)
The conventional wisdom says that if you want to sell software the Mac is the best platform because Mac users would be willing to pay a premium for a well-designed application. Linux would be the worst platform because most Linux would rather tolerate a poorly designed free application than pay for a well designed app.
Is this true?
I use Linux and I have paid for applications. (63%, 12 votes)
I use Linux and I would pay for a “good” app. (21%, 4 votes)
I use Linux and I would never pay for an app. (15%, 3 votes)
I strongly encourage people to pay for open source and donate to projects who you rely on
I paid the $100+ for the fake Immich license and they've said in a blog post that this has been a very successful fundraising method. Last I checked they didn't give more details though.
NVDA is working on building magnification into its screen reader, plus support for Microsoft Natural Voices is coming too. Read more about their plans from their roadmap here: nvaccess.org/post/nvda-roadmap…
Watching the Ken Burns doc on the American Revolution and now I'm scared of the Hessians. Looking under the bed for Hessians. Looking out at sea with my spyglass for Hessians. They could be anywhere.
You know what? I'm not getting into a fight about how big a deal the React vuln is. The footprint is bigger than you think because the correlation is difficult to ascertain, but Next.js alone is a monster.
And this is in an ecosystem that is not particularly used to this kind of vulnerability.
@pertho somehow, I suspect. It's my best guess but nothing else changed here except rebooting for a 14.3-RELEASE to 15.0-RELEASE upgrade. And by the time I was going to login to the firewall and check the arp table it started working.
@Tubsta @pertho A good guess as well. If I can reproduce the problem I'll be comparing the interface options from a before and after working state in case something changed by itself (which would be crazy but who knows!)
Je vais lancer un Substack intitulé « les cyclistes mangent les pauvres 'ti bébés sans défense » et ça va juste être composé de screenshots des incroyables commentaires venimeux écrits par les montréalais.es contre le vélo dans les groupes/pages communautaires sur FB.
@hub nan nan t'inquiètes pas si j'allais vraiment le faire ça serait évidemment un truc avec ghost mais les normies savent plus comment dire « infolettre » ni « blog » LOL
A short tale from way back when I worked at Apple: My team had a lot of lunchtime meetings and they usually got pizza to feed us lunch while we worked. There were two of us on the team who were vegetarian, so they'd order six or eight pizzas for the team and all of them would have meat except for the one meatless pizza they had for just the two of us. But everyone likes vegetarian pizza, so people would get in line, take what looked good which included the veggie pizza, and by the time I got to the veggie pizza it would be gone and I'd have no lunch (and the other vegetarian had the same problem, of course). They tried to get the non-vegetarian people to stop eating the veggie pizza, then tried to hide it so only we veggies could get it, but nothing worked. So I suggested they order four kinds of vegetarian pizzas and a couple pizzas with meat, and that worked out great and there was much rejoicing.
This is a post about gatekeeping disability accommodations.
I think it will be fine, but there's not much to gain because it's not like doing patches to a RELEASE with freebsd-update is slow or very frequent at all. It's really only the major/minor upgrades which are slow, and by the time the next one is ready (15.1-RELEASE) I'm sure pkgbase will be very stable. So just wait a bit
upgrading from 14.3-RELEASE pkgbase is a pain though, you'll want to see the release notes on what to do (manually fetch the 15.0 bootstrap package to get the correct keys+repos, then fake the ABI env to install the packages)
The following bug fix is now in the latest version of Slack for iOS.
• Apple VoiceOver was not able to select buttons anywhere in Slack outside of threads. Like your favorite cardigan, buttons and threads will, at times, be in need of repair. Here's a cozy thought: This bug has been all sewn up and tied off. apps.apple.com/us/app/slack/id…
@30p87 I hesitated briefly to leave all my existing followers and community there, but the downfall made it inevitable and I have really found "home" on Mastodon since. Fewer followers maybe, but with more and better engagement, fewer nazis and all around just a good feeling of being on the right team.
@RandomDamage tagged VLAN is what I proposed originally so the first problem you have to solve is making the NIC emit tagged frames 😏 which is much harder than clever solutions to make TCP connections or something
@RandomDamage ooooh can that be done with something in /sys? is that all the tooling does? that would be fascinating, I'll have to spend some time looking into that
@RandomDamage yeah I don't know why I've always assumed they were something more special than that. Perhaps a long long time ago they were, like 2.4 and early 2.6 kernels
I've seen a few people put content warnings on their "looking for work" posts.
I recommend you DON'T do this. Not everyone who comes across your post will bother to expand it. Worse, content warnings prevent your post from appearing in Trending lists, limiting your reach.
I'm not sure what purpose a CW would even serve here—if someone finds the fact that you're looking for work offensive or traumatizing, that's a them problem, not a you problem.
NVDA has the addition of magnification on their roadmap. I feel like that should be a separate project. Still under NV Access, still sharing some of the code base, and made to work with NVDA, but separate. I don't need and can't use magnification, so I don't love the idea of the download getting bigger to house those features and the startup slowing down as NVDA does visual things that are of no use to me. Am I wrong? No really, I'm asking. nvaccess.org/post/nvda-roadmap…
it made me a bit sad that font support for multiline displays was mentioned as long-term, not even a medium goal. Feels a bit disconnected to me for that reason. If you're going to improve multiline support in "short-term" you're not going to add the font info as a medium-term goal? Gosh oh gosh. Honestly NVDA's Braille support has always been a reason to jump JAWS for me, so if this becomes info JAWS can deliver to me on multiline they can expect me to jump ship more often if not entirely to JAWS. Sad but true.
I dobt it adds a significant size on downloads. I think this will benefit much more than a separate product, namely because the interceptiom between screen reader users and heavy magnifier users is big.
Separate product means new sbraneing, new infra, new release cycle.. for what? To compete with windows magnifier? An integrated approach like Supernova is where the oportunity exists.
Thanks for the thoughts on this, everyone. I didn't realize how many people use both a screen reader and magnification. To me, the two camps have always been separate, with a few people in both. I guess I was wrong there.
I think my concern is that NV Access may lack the staff to maintain/improve NVDA *and* make a magnifier. I also don't want this to be the start of NVDA getting bloated like Jaws is. NVDA is small, simpler, and keeps a lot out of core.
After I left Ai Squared/VFO, I used Windows Magnifier with NVDA full-time. There have been add-ons in the past that make that a little bit easier. But it definitely could use a bit more on board. It has been tough with magnification, still has some bumps at times to get around. Full disclosure, I serve on the windows low vision community panel. So, this is a conversation that does come up from time to time. And splitting off into a separate branch is absolutely positively in no way thinkable bad idea. Well I'm not thrilled with how LP Das/magic/Zoom text was incorporated into jaws, having a single repository that brings things in with modules is much better than doing separates. That was unthinkable 10 years ago, it's common place now
Dodgy take IMO man. Think of how many low vis and losing vis folks this could help. How often are you on a connection where it'll make more than a couple of seconds difference?
@prism Why make newcomers jump through extra hoops to get an add-on when having it in core would only mean a few extra seconds of download and one extra option on the start screen? I'm having a hard time believing anyone's really going to be inconvenienced by that, and am also kinda miffed at such loud reluctance to help more people with more use cases.
@Scott @prism Yeah I see why some might think it shouldn't be included by default, but there's a very easy solution for this. Have a prompt at the start of screen, asking if you need magnification, if so, download whatever relevant modules are needed and go from there. Does not have to be complicated, and everyone gets what they want. Personally I don't really have much of a problem with it being built-in as long as screen reader performance is still good.
Also didn't fully grasp how bad the magnification situation on windows is right now, I've never used it in my life so didn't have a reason to look into it much. Kinda like sighted people learning about screen readers for the first time lol.
@ZBennoui @Scott @prism I didn't realize how bad things are, either. I'm coming around to magnification being included, though I still feel it would make more sense as an add-on or second program meant to work closely with NVDA, something that NVDA can automatically install if desired. My main concern is still bloat and scope creep.
@Scott @prism Ok I know this isn't as related, but as a totally blind guy I've sometimes wondered what magnification software actually does? Like what does it mean to change the size of text? IDK if anyone here can explain but just putting it out there.
@ZBennoui @Scott @prism Think of it like changing how easy it is to feel the lines on tactile graphics. Have you ever felt an image with thin lines, all close together and jumbled? It was hard to track the lines, the image didn't make sense, and it was easy to lose track of what was going on because the lines were too thin or faint. Now give that same tactile image proper lines and more room to breathe. It's much easier to feel.
@ZBennoui @Scott @prism It also gives ability to allow for different forms of low vision. Do you do best with dark text on light background, or the reverse? It allows the user to focus on the part of the screen where the action is, maybe magnify it more or change other attributes. People with normal vision make adjustments automatically, but in that continuum where vision is deteriorating, until the point where it isn't helpful any more, magnification software fills in. this from a totally blind guy.
If so, help us keep up the momentum by sharing with your friends, especially those outside of the typical contributor community. Let’s end the year strong!
Me: I'd like to connect to another account Plaid: Great, which one, and provide credentials Me: Here ya go Plaid: Looks good, they sent an OTP, please provide it Me: Here ya go Plaid: Something went wrong. Try again? Me: Sure Plaid: Great, which account, and provide credentials Me: Here ya go Plaid: Looks good, they sent an OTP, please provide it Me: Here ya go (2nd OTP) Plaid: Something went wrong. Try again? Me: No Plaid: Are you sure you want to cancel and lose your progress?
worst part is that Plaid just breaks your bank's ToS if they never integrated (sounds like they didn't) by scraping their website and logging in with your stored credentials you just gave them.
oh and then they also harvest all of your bank balances/activity/transactions to analyze, just like Zelle does
Aaaaand this would be why I refuse to have a firearm in Suburbia (former), or Hippy Ville (Santa Cruz, current), or in the middle of a big fucking city like San Francisco for "Self Protection".
We shoot sheet rock walls to find out how many walls it takes to stop a typical home defense round. We do these tests on our private, closed gun range. Don't...
@feld I hung some sheetrock recently, and did some insulation so I'mma Guestimate (yes Auto, Guestimate is a word) ...
I'm thinking the hollow points might have flared with some Owens Corning Pink. Would have made zero difference with FMJ/Ball.
Now 2" insulation *Board* would be roughly a 5/8" drywall board-ish, so I'd take 30-35% off of any penetration from a pistol. *Perhaps* 15-20% from shotgun pellets. High energy rifle round, 10-15%?!? May be?
On the occasion of SimpleX and Session getting cryptocoin-donations/funding ... we won't hide that most delta contributors are pretty skeptical of cryptocoin-circles. Exhibit 1: #Webxdc apps - mini apps that anyone can whip up -- and the declared motto still on the webxdc.org web page since inception mid 2022:
No logins, no coins, no platforms ...
and this year, January 23rd, we added "no billionaires" to the growing list of things deserving a "no" :)
How can we evolve and deploy web apps without allowing developers or operators to become a “billionaire in the middle”? There are many ways to try to address this challenge and some involve the tec...
I'm not sure what point this post is making. Delta Chat also accepts bitcoin donations. A bitcoin address is provided on the Delta Chat donation page. Is that a bad thing?
@alandes receiving donations via BTC does not have to do with the chatmail operations (servers and clients) which don't require any chain-coin to operate. Moreover, webxdc was designed as a decentralized web system in difference to "web3" which was typically tied into chain-coin things.
Well, the initial process isn't very user friendly. It's based on web tools for hosting services (it's more like ordering a hosting service than subscribing to a cloud service), not really something designed to be for end users. But once the service is set up, managing the instance is easy.
hi everybody, for those who have read the dungeon crawler Carl series. What do people think of it. I am kind of thinking about getting it. Next time I subscribe to Audible.
MinIO is a high-performance, S3 compatible object store, open sourced under GNU AGPLv3 license. - update README.md maintenance mode · minio/minio@27742d4
Really there's no Split Braille add-on for NVDA? I swear there was one I saw, but it's not in the store, nowhere to be found. Hmm. Braille Extender doesn't appear to do it, unless it's not in the feature list. Loved it in JAWS on a single-line display, now that I'm using 24-by-4, it would be even more useful in things like tables and sometimes I'd use it with my GitHub PR window in one part and my VSCode copy in the other. Just, all round useful, wish I had it for NVDA.
@Jage yeah, and I think the code for the add-on is getting integrated s an official driver inside NVDA 2026.1. iOS already had the support, JAWS also needs a config file to make the multiline work and displaying text across two displays. FS is supposed to address that in their next update. github.com/tactile-eng/cadendu…
Cool. It makes sense for all of this multiline code to converge instead of there being separate drivers for Cadence, Dot, not sure what Monarch or Codex has, did I miss one?
@Jage wonder if Grafiti can do multiline Braille or just graphics? That was about the only other one I had some interest in, but it kind of evaporated after seeing my partner's Orbit display have random faults in connecting and then they lost a key while traveling home. Gosh. Cadence feels a bit more promising with the keys large rectangular rubberized plastic, overall workmanship is just so solid, it just needs more consistent SR support and it'll get there. I know all of these use the HID protocol, and there's a standard HID Braille that Cadence exposes, so JAWS had a driver for it even with 2025, just no multiline. Feels like any new display that comes to the market will be HID, and if there's one advantage it's that it's not a uniquely different API for each display but can be uniformly understood as long as both display and SR speak it.
@Jage I saw a prototype of the second-gen Graphiti at CSUN a few years ago, and it could definitely do both. No idea what the selling hardware looks like.
@sclower OK to be fair I hadn't bothered to look at one more recently. Were the dots still larger than normal, or did it just do braille on a bottom status line?
@Jage @sclower I'm really confused by their page because they say, "2400 Independently Refreshable Pins in a 60 x 40 array" - great (same as DotPad). But: " 40 TrueBraille™ cells offering Orbit’s signage-quality braille and cursor routing keys" so does that mean that unlike DotPad it cannot do mixed Braille and graphics or Braille on the multiline? I am not sure. It's weird they call them out separately like that though, unless it also can do both. I believe the DotPad has a 20-cell separate display like this too, but that you can still do regular Braille on its 300-cell graphics side? Not 100% clear on this either I guess.
feld
in reply to feld • • •