<table><tr><td style="">rytilahti added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D15338">View Revision</a></tr></table><br /><div><div><p>Thanks for the feedback Simon!</p>
<blockquote style="border-left: 3px solid #8C98B8;
color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/D15338#324374" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">D15338#324374</a>, <a href="https://phabricator.kde.org/p/sredman/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@sredman</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>I really like this as an idea! Even if it only works in the same places as the current UDP broadcast (and my quick testing says it should work more places) it feels way more modern and professional. Of course, we really need support on (at least one of) Android and desktop for using this to initiate a pairing.</p></div>
</blockquote>
<p>One of the reasons I delved into this is the fact that my phone may be sometimes in a separate network, which can thankfully be enabled fairly easily: <a href="https://www.systutorials.com/docs/linux/man/5-avahi-daemon.conf/#lbAH" class="remarkup-link" target="_blank" rel="noreferrer">https://www.systutorials.com/docs/linux/man/5-avahi-daemon.conf/#lbAH</a> :-)</p>
<p>I'll see to implement the pairing initiation inside this PR.</p></div></div><br /><div><strong>INLINE COMMENTS</strong><div><div style="margin: 6px 0 12px 0;"><div style="border: 1px solid #C7CCD9; border-radius: 3px;"><div style="padding: 0; background: #F7F7F7; border-color: #e3e4e8; border-style: solid; border-width: 0 0 1px 0; margin: 0;"><div style="color: #74777d; background: #eff2f4; padding: 6px 8px; overflow: hidden;"><a style="float: right; text-decoration: none;" href="https://phabricator.kde.org/D15338#inline-83077">View Inline</a><span style="color: #4b4d51; font-weight: bold;">sredman</span> wrote in <span style="color: #4b4d51; font-weight: bold;">lanlinkprovider.cpp:115-117</span></div>
<div style="margin: 8px 0; padding: 0 12px; color: #74777D;"><p style="padding: 0; margin: 8px;">Avoiding code reuse is definitely good, but maybe it would make even more sense to have a higher-level helper function, something like "get device identity", which maybe returns some custom "identity" class(/struct) and is used by both this and the createIdentityPacket method? That just feels a little nicer that "ad-hoc" using the identity packet, and is robust to the potential of that packet changing in the future.</p></div></div>
<div style="margin: 8px 0; padding: 0 12px;"><p style="padding: 0; margin: 8px;">Indeed, this was just a PoC to see how easy it would be to add support for this. A simple identity wrapper sounds like a way to go, I'll see what I can do.</p></div></div></div></div></div><br /><div><strong>REPOSITORY</strong><div><div>R224 KDE Connect</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D15338">https://phabricator.kde.org/D15338</a></div></div><br /><div><strong>To: </strong>rytilahti<br /><strong>Cc: </strong>sredman, kdeconnect, dvalencia, rmenezes, julioc, Leptopoda, timothyc, jdvr, yannux, Danial0_0, johnq, Pitel, adeen-s, SemperPeritus, ndavis, daniel.z.tg, jeanv, seebauer, bugzy, MayeulC, menasshock, tctara, apol<br /></div>