Benjamin_Loison commented on issue Benjamin_Loison/cryptpad#49 2025-08-18 15:22:53 +02:00
Proceed regularly to exports in case of host failure

No button shown to create a new document it seems.

Benjamin_Loison commented on issue Benjamin_Loison/cryptpad#49 2025-08-18 15:22:31 +02:00
Proceed regularly to exports in case of host failure

On another document have:

image.png

Benjamin_Loison commented on issue Benjamin_Loison/cryptpad#49 2025-08-18 15:07:14 +02:00
Proceed regularly to exports in case of host failure

Refreshing the webpage does not help.

Same issue on Chromium.

Benjamin_Loison commented on issue Benjamin_Loison/cryptpad#49 2025-08-18 15:06:01 +02:00
Proceed regularly to exports in case of host failure

https://uptime.cryptpad.org/status/cryptpad does not denote issue since 10 minutes.

Could use own instance otherwise. E2EE is maybe still preferable in such case.

Benjamin_Loison commented on issue Benjamin_Loison/cryptpad#49 2025-08-18 15:04:37 +02:00
Proceed regularly to exports in case of host failure

I confirm that can't write in document in such case.

Note that the second screenshot shows that it is not a problem with the first screenshot document which is the issue it seems, related to #43.

Benjamin_Loison commented on issue Benjamin_Loison/cryptpad#47 2025-08-18 15:03:35 +02:00
*Math* not rendered if being a *Link*

Maybe related to #49.

Benjamin_Loison commented on issue Benjamin_Loison/cryptpad#49 2025-08-18 15:02:01 +02:00
Proceed regularly to exports in case of host failure

Is last known (and history) of document state kept locally anyway in case of full host failure?

Benjamin_Loison opened issue Benjamin_Loison/cryptpad#49 2025-08-18 14:51:00 +02:00
Proceed regularly to exports in case of host failure
Benjamin_Loison commented on issue Benjamin_Loison/cryptpad#43 2025-08-18 01:14:48 +02:00
*This document has accumulated* *of history that may slow down loading time.*

Chromium helps maybe a bit as far as I experience compared to Firefox on my Linux Mint 22.1 CInnamon Framework 13.

Benjamin_Loison commented on issue Benjamin_Loison/codeberg#13 2025-08-13 14:55:39 +02:00
*server error: 500* when add a new issue comment
*Network* request to https://codeberg.org/Benjamin_Loison/cron/issues/25/comments to post comment results in:
<!DOCTYPE html>
<html lang="en-US"
Benjamin_Loison commented on issue Benjamin_Loison/linux#27 2025-08-12 13:37:36 +02:00
Dual boot Windows time inconsistency
sudo ntpd -gq
sudo: ntpd: command not found
sudo apt install -y ntpd
Error: Unable to locate package ntpd
ntpd
bash: ntpd: command…
Benjamin_Loison commented on issue Benjamin_Loison/linux#27 2025-08-12 13:36:50 +02:00
Dual boot Windows time inconsistency
sudo apt install -y ntpdate
Output:
Package ntpdate is not available, but is referred to by another package.
This may mean that the package is…
Benjamin_Loison commented on issue Benjamin_Loison/linux#27 2025-08-12 13:36:38 +02:00
Dual boot Windows time inconsistency
sudo apt install ntp
Output:
Package ntp is not available, but is referred to by another package.
This may mean that the package is missing, has…
Benjamin_Loison commented on issue Benjamin_Loison/linux#27 2025-08-12 13:30:44 +02:00
Dual boot Windows time inconsistency

I have read Wikipedia: Ntpdate (1300646220)

The accuracy and reliability of ntpdate entirely depends on the accuracy…