There's a bug with showing peer status in 0.2.19. Even hours after the buddy has gone offline he is still shown as online. State changes once you change your own state or try to send a message to the contact.
The first sent message is not quitted with the "message will be sent once the contact come back online" message, following ones are.
Feature requests:
when someone adds you, you should get a notification and the other contact should not be added or my own state shown to him before he was admitted by me.
and more generally an option for blocking all users that you have not added manually yourself would also be nice
another user writes:
« I haven't used these features personally, and at the moment they seem greyed out for me, but I'm seeing under Settings->Security a container captioned "General" with two options that to me sound similar to what you're asking:
A couple of days ago some random guy added my nick. I suppose he found me over seedless search. We exchanged a couple of messages, everything was well. Then my I2P-Messenger went offline. Now I turn it back on. I see that item displayed as "Receiving" in my user list. Is it because I didn't explicitly add that user as well? But the problem here is that as long as this item stayed in my user list, seedless search returned 0 results. As long as I deleted this item, seedless search started to work properly and return results.
[…]
I run seedless search. It finds me as well. I try to add myself to my user list. I2P-Messenger is segfaulting. Here is the gdb backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x0806dd0f in CUser::setI2PStreamID (this=0x0, ID=-1) at src/User.cpp:115
115 src/User.cpp: No such file or directory.
in src/User.cpp
(gdb) bt
#0 0x0806dd0f in CUser::setI2PStreamID (this=0x0, ID=-1) at src/User.cpp:115
#1 0x08075810 in CProtocol::slotInputUnknown (this=0x823f7c8, ID=-1, Data=...)
at src/Protocol.cpp:364
#2 0x080cf17c in CProtocol::qt_metacall (this=0x823f7c8, _c=
QMetaObject::InvokeMetaMethod, _id=1, _a=0xbfffe854)
at moc/moc_Protocol.cpp:79
#3 0xb72d426a in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/qt/lib/libQtCore.so.4
#4 0xb72e2885 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/qt/lib/libQtCore.so.4
#5 0x080d2335 in CI2PStream::signDataRecived (this=0x8244f08, _t1=-1, _t2=...)
at moc/moc_I2PStream.cpp:123
#6 0x080b1be3 in CI2PStream::slotReadFromSocket (this=0x8244f08)
at src/I2PStream.cpp:260
#7 0x080d2244 in CI2PStream::qt_metacall (this=0x8244f08, _c=
QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfffea2c)
at moc/moc_I2PStream.cpp:95
#8 0xb72d426a in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/qt/lib/libQtCore.so.4
#9 0xb72e2885 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/qt/lib/libQtCore.so.4
#10 0xb7331f17 in QIODevice::readyRead() () from /usr/lib/qt/lib/libQtCore.so.4
#11 0xb7488552 in ?? () from /usr/lib/qt/lib/libQtNetwork.so.4
---Type <return> to continue, or q <return> to quit---
#12 0xb7475e2b in ?? () from /usr/lib/qt/lib/libQtNetwork.so.4
#13 0xb74771f3 in ?? () from /usr/lib/qt/lib/libQtNetwork.so.4
#14 0xb764fd0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
from /usr/lib/qt/lib/libQtGui.so.4
#15 0xb765695e in QApplication::notify(QObject*, QEvent*) ()
from /usr/lib/qt/lib/libQtGui.so.4
#16 0xb72cf06b in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
from /usr/lib/qt/lib/libQtCore.so.4
#17 0xb72fae8a in ?? () from /usr/lib/qt/lib/libQtCore.so.4
#18 0xb6dee0f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0xb6df1990 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0xb6df1ac3 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0xb72faab5 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/qt/lib/libQtCore.so.4
#22 0xb770cd55 in ?? () from /usr/lib/qt/lib/libQtGui.so.4
#23 0xb72cd689 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/qt/lib/libQtCore.so.4
#24 0xb72cdada in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/qt/lib/libQtCore.so.4
#25 0xb72d1c6f in QCoreApplication::exec() ()
from /usr/lib/qt/lib/libQtCore.so.4
#26 0xb764fda7 in QApplication::exec() () from /usr/lib/qt/lib/libQtGui.so.4
#27 0x08053f99 in main (argc=1, argv=0xbffff254) at src/Main.cpp:35
I start I2P-messenger again. As soon as I change the status to Online, it segfaults again. The backtrace looks similar:
Program received signal SIGSEGV, Segmentation fault.
0x0806dd0f in CUser::setI2PStreamID (this=0x0, ID=-1) at src/User.cpp:115
115 src/User.cpp: No such file or directory.
in src/User.cpp
(gdb) bt
#0 0x0806dd0f in CUser::setI2PStreamID (this=0x0, ID=-1) at src/User.cpp:115
#1 0x08075810 in CProtocol::slotInputUnknown (this=0x823f7c8, ID=-1, Data=...)
at src/Protocol.cpp:364
#2 0x080cf17c in CProtocol::qt_metacall (this=0x823f7c8, _c=
QMetaObject::InvokeMetaMethod, _id=1, _a=0xbfffe854)
at moc/moc_Protocol.cpp:79
#3 0xb72d426a in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/qt/lib/libQtCore.so.4
#4 0xb72e2885 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/qt/lib/libQtCore.so.4
#5 0x080d2335 in CI2PStream::signDataRecived (this=0x8244590, _t1=-1, _t2=...)
at moc/moc_I2PStream.cpp:123
#6 0x080b1be3 in CI2PStream::slotReadFromSocket (this=0x8244590)
at src/I2PStream.cpp:260
#7 0x080d2244 in CI2PStream::qt_metacall (this=0x8244590, _c=
QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfffea2c)
at moc/moc_I2PStream.cpp:95
#8 0xb72d426a in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/qt/lib/libQtCore.so.4
#9 0xb72e2885 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/qt/lib/libQtCore.so.4
#10 0xb7331f17 in QIODevice::readyRead() () from /usr/lib/qt/lib/libQtCore.so.4
#11 0xb7488552 in ?? () from /usr/lib/qt/lib/libQtNetwork.so.4
---Type <return> to continue, or q <return> to quit---
#12 0xb7475e2b in ?? () from /usr/lib/qt/lib/libQtNetwork.so.4
#13 0xb74771f3 in ?? () from /usr/lib/qt/lib/libQtNetwork.so.4
#14 0xb764fd0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
from /usr/lib/qt/lib/libQtGui.so.4
#15 0xb765695e in QApplication::notify(QObject*, QEvent*) ()
from /usr/lib/qt/lib/libQtGui.so.4
#16 0xb72cf06b in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
from /usr/lib/qt/lib/libQtCore.so.4
#17 0xb72fae8a in ?? () from /usr/lib/qt/lib/libQtCore.so.4
#18 0xb6dee0f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0xb6df1990 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0xb6df1ac3 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0xb72faab5 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/qt/lib/libQtCore.so.4
#22 0xb770cd55 in ?? () from /usr/lib/qt/lib/libQtGui.so.4
#23 0xb72cd689 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/qt/lib/libQtCore.so.4
#24 0xb72cdada in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/qt/lib/libQtCore.so.4
#25 0xb72d1c6f in QCoreApplication::exec() ()
from /usr/lib/qt/lib/libQtCore.so.4
#26 0xb764fda7 in QApplication::exec() () from /usr/lib/qt/lib/libQtGui.so.4
#27 0x08053f99 in main (argc=1, argv=0xbffff254) at src/Main.cpp:35
There is a record related to my nick in users.config. As soon as I remove it by manually editing the file, I2P-Messenger stops segfaulting.»
//from http://forum.i2p/viewtopic.php?p=31157#31157
"currently it does not have a password, no resumeable file transfers, no offline messages (since there's no server), and otr would be nice too. also indenting the chat messages" //from http://forum.i2p/viewtopic.php?p=52704#52704
mixxy writes:
There's a bug with showing peer status in 0.2.19. Even hours after the buddy has gone offline he is still shown as online. State changes once you change your own state or try to send a message to the contact.
The first sent message is not quitted with the "message will be sent once the contact come back online" message, following ones are.
Feature requests:
when someone adds you, you should get a notification and the other contact should not be added or my own state shown to him before he was admitted by me.
and more generally an option for blocking all users that you have not added manually yourself would also be nice
//from http://forum.i2p/viewtopic.php?p=30868#30868
another user writes: « I haven't used these features personally, and at the moment they seem greyed out for me, but I'm seeing under Settings->Security a container captioned "General" with two options that to me sound similar to what you're asking:
"Block all unknown Users" "Request Authorization"
//from http://forum.i2p/viewtopic.php?p=30898#30898
«regarding 0.2.19 beta version (running on linux)
[…]
I start I2P-messenger again. As soon as I change the status to Online, it segfaults again. The backtrace looks similar:
There is a record related to my nick in users.config. As soon as I remove it by manually editing the file, I2P-Messenger stops segfaulting.» //from http://forum.i2p/viewtopic.php?p=31157#31157
"currently it does not have a password, no resumeable file transfers, no offline messages (since there's no server), and otr would be nice too. also indenting the chat messages" //from http://forum.i2p/viewtopic.php?p=52704#52704