You would need an interacting charting library that works with a keyboard and that is readable by a screen reader.
525 karma · joined November 24, 2021
You would need an interacting charting library that works with a keyboard and that is readable by a screen reader.
As such I think it's not a good idea for a document that should have a large audience.
Practical example: there exists an MCP server for Jira. Connect that MCP server to e.g. Claude and then you can write prompts like this:
"Produce a release notes document for project XYZ based on the Epics associated to version 1.2.3"
or
"Export to CSV all tickets with worklog related to project XYZ and version 1.2.3. Make sure the CSV includes these columns ....."
Especially the second example totally removes the need for the CSV export functionality in Jira. Now imagine a scenario in which your favourite AI is connected via MCP to different services. You can mix and match information from all of them.
Alibaba for example is making MCP servers for all of its user-facing services (alibaba mail, cloud drive, etc etc)
A chat UI powered by the appropriate MCP servers can provide a lot of value to regular end users and make it possible for people to use their own data easily in ways that earlier would require dedicated software solutions (exports, reports). People could use software for use cases that the original authors didn't even imagine.
Given the many smartwatches on the market which can do so much more, are lightweight and some of them with acceptable battery life (Garmin, Suunto, Amazfit), a smartring is of very little interest to me. But I often struggle to understand why certain products fascinate people, so I may be totally wrong and I wish the makers best of luck.
Now if you practice mountainbike you may ride your bike 1 to 5 times a week. Let's say you only ride once a week for 4 hours: 125 / 4 = 31, you would need to service your fork every 31 weeks. Add some few more rides and you have to service the fork twice a year.
Each service easily costs $150 if done by a bike shop. If you do it yourself (plenty of tutorials on youtube), you need expensive special tools, oil, special grease and spare o-rings and seals easily costs 30-40$ for every service. And you have to properly dispose the old oil.
[0] https://tech.ridefox.com/bike/owners-manuals/2979/fork--2025...
If you understood the paradigm, you could write branches in Ant files simply using properties and guards on properties ("unless"). Using IF in Ant was basically admission of not having understood Ant.
This said, I used Ant for a very limited amount of time.
Yes, the document contains highly significant factual findings by the Court regarding how Google deprioritized organic search results in favor of advertising. The most significant findings: The Court documents that the positioning of Google's AI features (AI Overviews, WebAnswers) on the search results page reduced users' interactions with organic web results - deliberately.
Relevant text:
"Some evidence suggests that placement of features like AI Overviews on the SERP has reduced user interactions with organic web results (i.e., the traditional "10 blue links")."
And:
"Placement of features like AI Overviews on the SERP has reduced user interactions with organic web results where Google's WebAnswers appears on the SERP"
Important note: these are not "admissions" in the sense of Google voluntarily confessing, but rather factual findings by the Court based on evidence presented during the trial - which is legally even more binding.
In reality, the phone had 24 GB of free space out of 64 GB total. I simply uninstalled the fake cleaner and the annoying notifications disappeared.
How such an app could reach the Play Store is beyond me. I can only imagine how many people that app must have deceived and how much money its creators likely made. I'm fairly certain the advertisement targets older people specifically—those most likely to be tricked.
For better or worse, I'm pretty sure that such an app would never land into the Apple App Store.
As an iPhone user, I find it frustrating that deploying my own app on my own device requires either reinstalling it every 7 days or paying $100 annually. Android doesn't have this limitation, which makes it simpler and more convenient for personal use.
However, when it comes to publishing apps to the store, I take a different view. In my opinion, stricter oversight is beneficial. To draw an analogy: NPM registry has experienced several supply chain attacks because anyone can easily publish a library. The Maven Central registry for Java libraries, by contrast, requires developers to own the DNS domain used as a namespace for their library. This additional requirement, along with a few extra security checks, has been largely effective in preventing—or at least significantly reducing—the supply chain attacks seen in the NPM ecosystem.
Given the growing threat of such attacks, we need to find ways to mitigate them. I hope that Google's new approach is motivated by security concerns rather than purely economic reasons.
When Docker Desktop changed licensing I tried to switch to Podman and it was a disaster, Podman was brand new and despite many blog posts that claimed it was the perfect replacement it did not work for me, and I have very simple requirements. So I ended up using Rancher Desktop instead, which was also very unstable but better.
Fast forward 1 year, Rancher was pretty good and Podman still did not work reliably on my mac.
Fast forward another year or so and I switched to colima.
I tried podman last time about one year ago and I still had issues on my old mac. So far colima has been good enough for my needs although at least two times a brew update broke colima and I had to reinstall from scratch.
In this way you exclude up-front the documents that the current user cannot see.
Of course, this requires you to update the vector metadata any time the permissions change at the document level (e.g. a given document originally visible only to HR is now also visibile to executives -> you need to add the principal executives to the metadata of the vector resulting from the document in your vector database)
Folllows sample output for "brew info mc"
==> midnight-commander: stable 4.8.33 (bottled), HEAD
Terminal-based visual file manager
https://www.midnight-commander.org/
Conflicts with:
minio-mc (because both install an `mc` binary)
Installed
/usr/local/Cellar/midnight-commander/4.8.33 (357 files, 7.8MB) \*
Poured from bottle using the formulae.brew.sh API on 2025-02-03 at 09:30:23
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/m/midnight-commander.rb
License: GPL-3.0-or-later
==> Dependencies
Build: pkgconf
Required: glib , libssh2 , openssl@3 , s-lang , diffutils , gettext
==> Options
--HEAD
Install HEAD version
==> Analytics
install: 3,043 (30 days), 10,456 (90 days), 65,490 (365 days)
install-on-request: 3,043 (30 days), 10,451 (90 days), 65,472 (365 days)
build-error: 0 (30 days)Otherwise as a user you end up clicking on the info icon to go to the app home page for every app before installing.
If that is not possible, a direct link to the app home page would save a click and would be highly appreciated.
As usual there is no silver bullet, so it's just a tool and like any other tool you need to use it wisely, when it makes sense.
However as many others pointed out, there is no way to ensure that the donated amount is used specifically to fund Firefox.
This said, 65XX on an early Commodore computers was extremely rewarding to use because there was no memory protection and you could write code altering video memory, mess with sprites, fonts, borders, interrupts, write self modifying code etc etc. 68000 assembly on Amiga was more safe and controlled.
Years ago I worked in a building on the side of a long straight road. The road ended with a blind curve to the right and 100m before the blind curve there was a pedestrian crossing.
Even though all drivers knew they would need to brake for the blind curve (it was visible and there were signs) the majority of them used to drive very fast and basically did not let people cross the road, only to push very hard on the brakes 10 meters beyond the pedestrian crossing.
The system was very good, stable, snappy. The main issue was the lack of software. Microsoft made deals with all hardware vendors and whenever people bought a personal computer they would find Windows pre-installed. At that time most of the people did not know what an operating system was, they just thought of a PC as an appliance, and most believed that Windows was the only option, that PC=Windows. Plus, computer and software were quite expensive, so why buy another operating system when your new PC comes with Windows for free. There are articles over the internet that claim that Microsoft, to kill OS/2, made deals with PC makers (HP, Compaq etc.) giving them OEM Windows licenses for free as long as they did not offer OS/2 as an alternative purchase choice to the end users, which basically meant 99% of people did not even know OS/2 existed. You would then find OS/2 in airports, banks, public transport etc. (all big organizations who were IBM customers) but it was not known by regular users.
This said the main weakness of OS/2 was the SIQ [1], single-input-queue. The user interface had a single queue for dispatching UI events, and due to a poor design, a single badly written UI program that got stuck while processing a call from the event loop, would freeze the whole OS/2 user interface. This was improved in later releases but never completely solved, even though admittedly in the last years of OS/2 this type of issues became quite rare.
[1] https://www.os2world.com/wiki/index.php/Databook_for_OS/2_%E...
This said, I believe that what made a big difference in look and feel when Windows 95 was released was the introduction of TrueType fonts that had much better rendering. OS/2 was using PostScript fonts, and introduced support for TrueType much later... If I remember correctly thanks to the open source efforts of the FreeType project.