From b12356575a08ff3e885d90c571180a19bc13c296 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mike=20Schw=C3=B6rer?= Date: Sun, 25 Nov 2018 18:11:42 +0100 Subject: [PATCH] Description text correction --- web/api_more.php | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/web/api_more.php b/web/api_more.php index 3d5d385..b0c428f 100644 --- a/web/api_more.php +++ b/web/api_more.php @@ -204,7 +204,7 @@ if (file_exists('/var/www/openwebanalytics/owa_php.php')) You can modify the displayed timestamp of a message by sending the timestamp parameter. The format must be a valid UNIX timestamp (elapsed seconds since 1970-01-01 GMT)

- But the custom timestamp must be within 48 hoours of the current time. This parameter is only intended to supply a more precise value in case the message sending was delayed + The custom timestamp must be within 48 hours of the current time. This parameter is only intended to supply a more precise value in case the message sending was delayed. 

curl                                          \
     --data "user_id={userid}"                 \
@@ -212,9 +212,6 @@ if (file_exists('/var/www/openwebanalytics/owa_php.php'))
     --data "title={message_title}"            \
     --data "timestamp={unix_timestamp}"       \
     https://scn.blackforestbytes.com/send.php
-

- Be aware that the server only saves send messages for a short amount of time. Because of that you can only use this to prevent duplicates in a short time-frame, older messages with the same ID are probably already deleted and the message will be send again. -

Bash script example