Skip to content

Add Accrescent Blog post#115

Merged
SailReal merged 3 commits into
developfrom
feature/blog-post-accrescent
Jan 24, 2025
Merged

Add Accrescent Blog post#115
SailReal merged 3 commits into
developfrom
feature/blog-post-accrescent

Conversation

@SailReal

Copy link
Copy Markdown
Member

No description provided.

Comment thread content/blog/2025-01-24-android-accrescent.en.md Outdated
SailReal and others added 2 commits January 24, 2025 08:57
Co-authored-by: Kerstin <kerstin.steiner@skymatic.de>
Co-authored-by: Kerstin <kerstin.steiner@skymatic.de>
@SailReal SailReal requested a review from CuriousPurah January 24, 2025 08:21
@SailReal SailReal marked this pull request as ready for review January 24, 2025 08:22
@coderabbitai

coderabbitai Bot commented Jan 24, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

The pull request introduces two new markdown files in the blog content directory: 2025-01-24-android-accrescent.de.md and 2025-01-24-android-accrescent.en.md. These files are German and English language versions of an announcement regarding Cryptomator's availability on the Accrescent app store. Both files contain metadata such as title, slug, date, and tags, and provide a comprehensive overview of Accrescent's security features and distribution strategy. The documents highlight Accrescent's unique characteristics, including no user account requirements, signed repository metadata, app signing key pinning, and minimum version enforcement. The announcement aims to inform users about the new distribution channel while emphasizing Cryptomator's commitment to security and transparency across different platforms.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
content/blog/2025-01-24-android-accrescent.de.md (1)

9-33: Consider style improvements in German text.

While the content is accurate, consider these optional style improvements:

  • Replace "Darüber hinaus" with alternatives like "Außerdem" or "Zusätzlich"
  • Replace "zum Beispiel" with alternatives like "beispielsweise" or "etwa"

Note: Keep "GrapheneOS" as is, since it's a proper noun.

🧰 Tools
🪛 LanguageTool

[misspelling] ~14-~14: Hier liegt möglicherweise ein Tippfehler vor.
Context: ...est/android/setup/#google-play-store), [APK Store](https://docs.cryptomator.org/en/latest...

(DE_MULTITOKEN_SPELLING_TWO)


[style] ~19-~19: Der Ausdruck ‚darüber hinaus‘ kommt sehr häufig vor. Möchten Sie ihn durch eine Alternative ersetzen, um Ihren Text individueller zu machen?
Context: ...ichere Wahl für Android-Nutzer bleibt. Darüber hinaus ist Accrescent der vorinstallierte App-...

(DARUEBER_HINAUS_STYLE)


[style] ~20-~20: Möchten Sie die modernere Schreibweise „GrafeneOS“ verwenden?
Context: ...tore auf einigen Android-Varianten wie [GrapheneOS](https://en.wikipedia.org/wiki/Graphene...

(F_ANSTATT_PH)


[style] ~26-~26: Der Ausdruck ‚zum Beispiel‘ kommt sehr häufig vor. Möchten Sie ihn durch eine Alternative ersetzen, um Ihren Text individueller zu machen?
Context: ...gen und -präferenzen gerecht zu werden. Zum Beispiel schätzen wir das [reproduzierbare Build](https://en....

(ZUM_BEISPIEL_STYLE)


[misspelling] ~30-~30: Hier liegt möglicherweise ein Tippfehler vor.
Context: ...stimmt. Ob du dich für Google Play, den APK Store, F-Droid oder Accrescent entscheidest –...

(DE_MULTITOKEN_SPELLING_TWO)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5a5dd7a and a803d85.

📒 Files selected for processing (2)
  • content/blog/2025-01-24-android-accrescent.de.md (1 hunks)
  • content/blog/2025-01-24-android-accrescent.en.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
content/blog/2025-01-24-android-accrescent.en.md

[grammar] ~29-~29: Did you mean to use the verb ‘assure’ here?
Context: ...ur reach to privacy-conscious users and ensuring a secure distribution channel that alig...

(ENSURE_ASSURE)

content/blog/2025-01-24-android-accrescent.de.md

[misspelling] ~14-~14: Hier liegt möglicherweise ein Tippfehler vor.
Context: ...est/android/setup/#google-play-store), [APK Store](https://docs.cryptomator.org/en/latest...

(DE_MULTITOKEN_SPELLING_TWO)


[style] ~19-~19: Der Ausdruck ‚darüber hinaus‘ kommt sehr häufig vor. Möchten Sie ihn durch eine Alternative ersetzen, um Ihren Text individueller zu machen?
Context: ...ichere Wahl für Android-Nutzer bleibt. Darüber hinaus ist Accrescent der vorinstallierte App-...

(DARUEBER_HINAUS_STYLE)


[style] ~20-~20: Möchten Sie die modernere Schreibweise „GrafeneOS“ verwenden?
Context: ...tore auf einigen Android-Varianten wie [GrapheneOS](https://en.wikipedia.org/wiki/Graphene...

(F_ANSTATT_PH)


[style] ~26-~26: Der Ausdruck ‚zum Beispiel‘ kommt sehr häufig vor. Möchten Sie ihn durch eine Alternative ersetzen, um Ihren Text individueller zu machen?
Context: ...gen und -präferenzen gerecht zu werden. Zum Beispiel schätzen wir das [reproduzierbare Build](https://en....

(ZUM_BEISPIEL_STYLE)


[misspelling] ~30-~30: Hier liegt möglicherweise ein Tippfehler vor.
Context: ...stimmt. Ob du dich für Google Play, den APK Store, F-Droid oder Accrescent entscheidest –...

(DE_MULTITOKEN_SPELLING_TWO)

🔇 Additional comments (7)
content/blog/2025-01-24-android-accrescent.en.md (5)

1-8: LGTM! Metadata is well-structured and accurate.

The metadata section contains all necessary fields with appropriate values.


15-20: LGTM! Clear explanation of Accrescent's benefits.

The section effectively communicates the key features and advantages of Accrescent.


21-26: LGTM! Comprehensive explanation of security practices.

The section effectively explains the security benefits and reproducible build concept.


27-31: LGTM! Strong conclusion that reinforces key messages.

The conclusion effectively summarizes the announcement and reinforces user choice.

🧰 Tools
🪛 LanguageTool

[grammar] ~29-~29: Did you mean to use the verb ‘assure’ here?
Context: ...ur reach to privacy-conscious users and ensuring a secure distribution channel that alig...

(ENSURE_ASSURE)


11-14: Verify documentation links.

The links to documentation pages need to be verified to ensure they are accessible and point to the correct sections.

✅ Verification successful

All documentation links are accessible and valid

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that all documentation links are accessible
# Note: Using curl with -L to follow redirects and -s for silent mode

echo "Checking documentation links..."
links=(
  "https://accrescent.app/app/org.cryptomator"
  "https://docs.cryptomator.org/en/latest/android/setup/#google-play-store"
  "https://docs.cryptomator.org/en/latest/android/setup/#apk-store"
  "https://docs.cryptomator.org/en/latest/android/setup/#cryptomator-f-droid-repository"
  "https://docs.cryptomator.org/en/latest/android/setup/#main-f-droid-repository"
)

for link in "${links[@]}"; do
  status=$(curl -L -s -o /dev/null -w "%{http_code}" "$link")
  echo "Link: $link - Status: $status"
done

Length of output: 2135

content/blog/2025-01-24-android-accrescent.de.md (2)

1-8: LGTM! German metadata is consistent with English version.

The metadata section maintains consistency while providing accurate German translations.


30-30: LGTM! Appropriate use of gender-inclusive language.

The use of "Nutzer:innen" follows modern German inclusive writing practices.

🧰 Tools
🪛 LanguageTool

[misspelling] ~30-~30: Hier liegt möglicherweise ein Tippfehler vor.
Context: ...stimmt. Ob du dich für Google Play, den APK Store, F-Droid oder Accrescent entscheidest –...

(DE_MULTITOKEN_SPELLING_TWO)

@SailReal SailReal merged commit bb8df4b into develop Jan 24, 2025
@SailReal SailReal deleted the feature/blog-post-accrescent branch January 24, 2025 08:34
@coderabbitai coderabbitai Bot mentioned this pull request Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants