still no joy after this, this is what dweb serve terminal is showing:
DEBUG serve with ports HttpRequest : GET /dweb-open/v/friends
DEBUG /dweb-open/v/friends
DEBUG parse_versioned_path_params_with_as_name() v/friends
1:v 2: friends r:
version:None as_name: anonymous, address_or_name: friends remote_path:
DEBUG History::from_history_address(a447871043968be2be1628584026cad30b824009a30eab43db3ee6dd8c0990051c27160cc8d1662da763d57c41c091f6)
>>TRYING pointer_get(b04d00aaa4011fe75106f9490e62f40e6f6c1b254585a3601055b772fd97c1ccec6a4352f20376e7d0e1be946dda41b7) unlimited times:
DEBUG pointer counter: 62, head address: abd81d872a9e6cee6efde6f0d2d2f722dcc764005caca71c3e7a6117a1036a7c1732bd9d38be3ff14a42708bd63aa3c7
>>SUCCESS!
DEBUG INSPECT pointer_counter: 62
DEBUG INSPECT pointer_target : abd81d872a9e6cee6efde6f0d2d2f722dcc764005caca71c3e7a6117a1036a7c1732bd9d38be3ff14a42708bd63aa3c7
DEBUG Unable to create directory version because from_history_address() failed - Failed to get pointer target entry - failed to get graph entry - Record could not be found.
DEBUG make_error_response_page() - message: Unable to create directory version because from_history_address() failed - Failed to get pointer target entry - failed to get graph entry - Record could not be found.. Address: friends
DEBUG serve with ports HttpResponse: 502 Bad Gateway (Bad Gateway)
The message format still needs some deeper thought (citations, answers, gifs, reactions,…) i plan on heavily borrowing from the telegram message format but for now it’s just a random utf-8 encoded json that came out of a mood that i send over to the other side xD…
… And ofc you would need the handshake data too… So establishing a friendship (-> sending friendship request and answering it; encrypted with suitable key), then the handshake scratchpads would need to be created and written (encrypted with partners public key) to initiate the webRTC channel …
I’m not 100% sure what you’re up to but depending on the precise idea it could end being a bit complex with the current implementation xD …
…i guess i did create smokesigns links that can be used by other apps, but then friends started using stuff (like encrypted friendship requests, encrypted handshakes and a pretty random message format xD… )…
… I guess i need to move and bundle the encryption stuff into the smokesigns links; then telling you to use that package and having a clearly specified interface would be significantly easier
Sorry for now no eta for that - I think I may look into group chats/blogs (no webrtc - only network data based comms/scratchchat like communication) next - that should be pretty straightforward with what I have already.
… I know mobile is important and it’s clearly the plan… But since it’s early days and somehow I’m confused what maidsafes plan looks like I’d like to see were we’re heading next before I put in that much effort…
oh it’s just that while maidsafe sais they’ve a small team they shared that roadmap full of stuff that is absolutely unknown if and when it will make it to production … which caused a lot of confusion with me and made me question if they see the same reality in front of them that I do …
as we now have a network that works (at least afaik) imho the priorities now should be:
community building
YouTube videos for devs and tinkerers (those are the most forgiving ones with early glitches in the tech and willing to invest time even if it’s not proven tech)
→ what can I do now with this exciting new tech
(listening to Jim is nice and he’s a good chap and tells the story in a nice way … but If I want to create something I want to see “how to build a Christmas lighting control in 3 minutes via autonomi”, “how to make a digital picture frame for my grandma in 2h (rpi, monitor, autonomy, python)”, …)
extensive tutorials for python/nodejs
presentations in fablabs/makerspaces/conferences/…
community events (?)
…
API work / bug fixing → making it easy and enjoyable for devs
… as I’ve seen from dirvine in discord this morning 2. is on the agenda … not sure how it’s possible my nr.1 doesn’t seem to be focus now … as good as the network looks right now … without people there is no future imho …
… at this point in time I don’t care about fees, native token or token value … I think the issue is that our community is shrinking instead of expanding (and the team seems to think that working on tech would resolve all issues … while I would think that it doesn’t change anything if there is no community work … and while I personally did benefit from the IF program I think the token could have been spent significantly more effective on community building instead …) and I don’t see attempts to change this …
…sorry for the off topic wall of text here … and that’s obviously just my own impression and I’m neither community nor marketing expert … but that’s why I would like to see a bit how it evolves and how and in which areas we improve …