zem / qtc-net Goto Github PK

a 0
b 1
d 2
e 3
f 4
h 5
i 6
m 7
n 8
r 9
s A
t B
u C
v D

c E0
f E1
g E2
j E3
k E4
l E5
o E6
p E7
q E8
w E9
x EA
y EB
z EC
! ED
_ EE
space EF

0 F0
1 F1
2 F2
3 F3
4 F4
5 F5
6 F6
7 F7
8 F8
9 F9
. FA
, FB
/ FC
? FD
'-' FE
utf8 FF

in the case if the VX-8 handheld does not receive the Ack

because those worked fine in the past

Therefore - in the filename really is - ad of / can be masqueraded to . or + or , or :

If you are a publisher and you receive a telegram assigned to you,
webfrontend should show a button. "answer", that opens up a send telegram dialog while it automatically publishes the qsp message.

we may have a chance to know then how the message gots delivered (aprs, packet, dxcluster, psk31, cw) and also wo has delivered.

Before first login in the main window.
Schould show all the last activity, messages, trusts, aliases etc.

i am on it, right now it does nothing.....

• should output some sort of yaml only
• should dirname ad basename file and path to be easy to use

OK here the idea:

"the signed content contains "type", "call" and the alphabetically sorted fields
of the message, packed together like they would be in the data file."

A client reduces the quality of a timestamp. Figure out what the hell you are doing with the call and voilla you may get qtc messages from various sources with the same checksum.

For example: If a message appears in a realtime network like APRS, you may consider building some sort of hour specific checksum which means that you can't send a message two times within one hour even if all the publishers do not know each other.

I have to think about this.....

to see where you are in simply add the Text of the value instead of the clickable button

To help people writing their own message formats like photo, Mail, television, voice

calls in messages should provide a link, to the Callsigns message list
that should be done with some js to export all the form data

9.7.2014 16:01 LT

Iternal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at [email protected] to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.
Apache/2.4.9 (Debian) Server at www.qtc-net.org Port 443

I want to see some discussion threads attached to the message. if possible.

Provide a GUI Proxy for HTTP requests to callbooks.

If a Log software asks for a call the URL is redirected to this proxy, the proxy finds out which callsign is questioned and so it does a qtc-net lookup with the right data, that is brought on screen.

so far there are three docs:

1. The Message Types in the Network as well as a "Filesystem" structure to sort all the messages away.
2. The Messages binary format (*.qtc)
3. An interface to access messages via http and to publish messages via http

Those 3 documents should be reviewed, and extended to RFC Drafts, so that other developers can use them in their own implementations.

without a hash of course

number: 7u publisher: oe1sya
from: oe1sya to: oe1src date: 2014-05-15 10:29:09 UTC
telegram: ok. wenn die qsp bei new und einer neuen abfrage nicht mehr aufscheinen ist es indirekt erfuellt. waer ggf nett qsp infos bei msg zu sehen. und eines verwirrt. die seite merkt sich die ansicht. zb all kommt wieder statt immer new. so wars bei erstversuch nicht sofort zu sehen dass new blank wird.

this means that users may send their qrg and it is visible for 1 hour in the network.

the has_qsp should work differently

as seen in the logs:

[Mon Apr 21 18:35:18.018880 2014] [cgi:error] [pid 13584] [client 89.144.237.160:4419] End of script output before headers: qtc-web.cgi, referer: https://www.qtc-net.org/
[Mon Apr 21 18:35:21.957006 2014] [cgi:error] [pid 15908] [client 89.144.237.160:4420] AH01215: No such run mode 'show_messages' at /home/zem/devel/qtc-net/src/cgi-bin/qtc-web.cgi line 18., referer: https://www.qtc-net.org/
[Mon Apr 21 18:35:21.958195 2014] [cgi:error] [pid 15908] [client 89.144.237.160:4420] End of script output before headers: qtc-web.cgi, referer: https://www.qtc-net.org/
[Mon Apr 21 20:59:54.336390 2014] [cgi:error] [pid 13584] [client 81.217.173.94:34008] AH01215: $VAR1 = bless( {, referer: https://www.qtc-net.org/
[Mon Apr 21 20:59:54.336462 2014] [cgi:error] [pid 13584] [client 81.217.173.94:34008] AH01215: 'selfsigned_to_delete' => [],, referer: https://www.qtc-net.org/
[Mon Apr 21 20:59:54.336490 2014] [cgi:error] [pid 13584] [client 81.217.173.94:34008] AH01215: 'call' => 'oe3yos',, referer: https://www.qtc-net.org/
[Mon Apr 21 20:59:54.336533 2014] [cgi:error] [pid 13584] [client 81.217.173.94:34008] AH01215: 'keyhash' => {},, referer: https://www.qtc-net.org/
[Mon Apr 21 20:59:54.336558 2014] [cgi:error] [pid 13584] [client 81.217.173.94:34008] AH01215: 'keys' => [],, referer: https://www.qtc-net.org/
[Mon Apr 21 20:59:54.336581 2014] [cgi:error] [pid 13584] [client 81.217.173.94:34008] AH01215: 'tree' => {},, referer: https://www.qtc-net.org/
[Mon Apr 21 20:59:54.336617 2014] [cgi:error] [pid 13584] [client 81.217.173.94:34008] AH01215: 'root' => '/var/spool/qtc/messages', referer: https://www.qtc-net.org/
[Mon Apr 21 20:59:54.336643 2014] [cgi:error] [pid 13584] [client 81.217.173.94:34008] AH01215: }, 'qtc::keyring' );, referer: https://www.qtc-net.org/
[Mon Apr 21 20:59:54.336698 2014] [cgi:error] [pid 13584] [client 81.217.173.94:34008] AH01215: Error executing run mode 'change_trust': Uuuuuuups there are no keys there for oe3yos, referer: https://www.qtc-net.org/
[Mon Apr 21 20:59:54.336740 2014] [cgi:error] [pid 13584] [client 81.217.173.94:34008] AH01215: at /home/zem/devel/qtc-net/src/cgi-bin/qtc-web.cgi line 18., referer: https://www.qtc-net.org/
[Mon Apr 21 20:59:54.337822 2014] [cgi:error] [pid 13584] [client 81.217.173.94:34008] End of script output before headers: qtc-web.cgi, referer: https://www.qtc-net.org/
[Mon Apr 21 21:00:02.971034 2014] [cgi:error] [pid 14266] [client 81.217.173.94:47265] AH01215: $VAR1 = bless( {, referer: https://www.qtc-net.org/
[Mon Apr 21 21:00:02.971103 2014] [cgi:error] [pid 14266] [client 81.217.173.94:47265] AH01215: 'selfsigned_to_delete' => [],, referer: https://www.qtc-net.org/
[Mon Apr 21 21:00:02.971127 2014] [cgi:error] [pid 14266] [client 81.217.173.94:47265] AH01215: 'keys' => [],, referer: https://www.qtc-net.org/
[Mon Apr 21 21:00:02.971152 2014] [cgi:error] [pid 14266] [client 81.217.173.94:47265] AH01215: 'keyhash' => {},, referer: https://www.qtc-net.org/
[Mon Apr 21 21:00:02.971178 2014] [cgi:error] [pid 14266] [client 81.217.173.94:47265] AH01215: 'call' => 'oe3yos',, referer: https://www.qtc-net.org/
[Mon Apr 21 21:00:02.971215 2014] [cgi:error] [pid 14266] [client 81.217.173.94:47265] AH01215: 'root' => '/var/spool/qtc/messages',, referer: https://www.qtc-net.org/
[Mon Apr 21 21:00:02.971238 2014] [cgi:error] [pid 14266] [client 81.217.173.94:47265] AH01215: 'tree' => {}, referer: https://www.qtc-net.org/
[Mon Apr 21 21:00:02.971265 2014] [cgi:error] [pid 14266] [client 81.217.173.94:47265] AH01215: }, 'qtc::keyring' );, referer: https://www.qtc-net.org/
[Mon Apr 21 21:00:02.971320 2014] [cgi:error] [pid 14266] [client 81.217.173.94:47265] AH01215: Error executing run mode 'change_trust': Uuuuuuups there are no keys there for oe3yos, referer: https://www.qtc-net.org/
[Mon Apr 21 21:00:02.971361 2014] [cgi:error] [pid 14266] [client 81.217.173.94:47265] AH01215: at /home/zem/devel/qtc-net/src/cgi-bin/qtc-web.cgi line 18., referer: https://www.qtc-net.org/
[Mon Apr 21 21:00:02.972536 2014] [cgi:error] [pid 14266] [client 81.217.173.94:47265] End of script output before headers: qtc-web.cgi, referer: https://www.qtc-net.org/

all the librarys should be documented with POD so other developers can use them within their code

we definately need those.....

the problem that:

sub foo {
return "bar", "baf", "bat";
}

sub bar {
while ($=shift) { print "parm: $\n"; }
}

bar(foo());

is printing bar, baf and bat leads to some important scope checks that many programmers are not aware of when getting data from the outside world, the problem was mentioned in a speech on 31C3 Congress and may be fixed by certain (foo())[0] whenever needed in the code.

The Change Trust should depend on the fact hat there is a key for the User to sign. The Apperance of an operator message is not a good qualification to make that button visible.

just in case that the other gate will fail .....

if a message appears twice with only a different time, this should be detected ans the message should be thrown to bad automatically. The Newest one counts.

if not, you may transmit clear text messages over radio links and just republish them with your key at the target. maybe you make a publishers chain.... Think about it.....

that should not happen.....

APRS Testmessage from OE1SRC-1 to OE1SRC-1 is going to be accepted from aprs but shouldn't

it is a good idea that users can reject their telegrams

for blogs to be sure that it doesn't get boring

Webapp should provide an own development interface. with the basic function (sending and receiving telegrams)

The advantage is that developers may have a much simpler interface, which means they can also user other languages as perl without redeveloping everything.

to let people know how they should istall all the networks components

Write a message archiving code ...........................

actually this is an enhancement of the qtc::signature lib

to get a reduced amount of telegram messages.

See other bug messages should not appear in new if send to yourself, or from one alias to another alias.

This also makes it possible to look at all messages like a timeline. (we now may have something similar to Twitter without the drawbacks)

Source Code is available and written in perl:

http://www.dxcluster.org/download/

so it should be easy. :)