docs: update safari compatibility in readme.txt

[malalacharm]

Summary by CodeRabbit

• Documentation
  • Clarified Safari image optimization and WebP support messaging across documentation.
  • Updated browser compatibility guidance with modern browser recommendations.
  • Adjusted dashboard statistics description labeling.
  • Updated changelog entries for feature descriptions.

[coderabbitai]

Warning

Review limit reached

@bfintal, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 58 minutes and 58 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c7f7f008-3b65-4d4f-ad01-9d1d65796f8b

📥 Commits

Reviewing files that changed from the base of the PR and between 21d325d and 38b8ef1.

📒 Files selected for processing (1)

• readme.txt

📝 Walkthrough

Walkthrough

Five text-only edits in readme.txt: three locations describing Safari/WebP browser compatibility are reworded to consistently state Safari uploads as JPG without WebP conversion; a statistics-dashboard bullet is shortened; and a 1.0.0 changelog entry is adjusted.

Changes

readme.txt Documentation Updates

Layer / File(s)	Summary
Safari/WebP compatibility messaging readme.txt	Updates the opening note (line 31), technical-details Browser Compatibility bullet (line 114), and FAQ answer (line 149) to consistently describe Safari as JPG-only with no WebP conversion support.
Statistics bullet and changelog text readme.txt	Shortens the statistics-dashboard bullet text at line 201 and adjusts the 1.0.0 "Privacy-first approach" changelog entry at line 318.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 A hop through the docs, a tweak here and there,
Safari uploads as JPG — now stated with care!
WebP conversion? Not this browser's game,
The stats bullet shortened, the changelog the same.
Five lines reworded, the warren set right,
🌟 Small fixes by day make the readme shine bright!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main changes: updating Safari compatibility messaging in readme.txt across multiple sections.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/readme

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@readme.txt`:
- Line 201: Fix the statistics dashboard bullet point that currently reads
"Number of optimized" by addressing two issues: first, remove the extra space
before "optimized" (there is a double space), and second, restore clarity by
including the missing context "media files" in the phrase. The corrected text
should read "Number of media files optimized" or similar phrasing that clearly
identifies what is being optimized.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1cdb22ca-f8e1-4dd1-8dda-d21ef7373bdb

📥 Commits

Reviewing files that changed from the base of the PR and between 19b4a68 and 21d325d.

📒 Files selected for processing (1)

• readme.txt

[github-actions]

🤖 Pull request artifacts

file	commit
pr63-cimo-63-merge.zip	38b8ef1