• 5 Posts
  • 19 Comments
Joined 5 months ago
cake
Cake day: June 13th, 2024

help-circle
  • My app is different because the auth is handled between peers. So it could only every be people you shared your ID with. Security is important for me on this project. Its more important than the app being popular. https://www.reddit.com/r/CyberSecurityAdvice/comments/1ev5kqn/is_this_a_secure_messaging_app/

    People should not connect to strangers on this app because of the potential risks of IP exposure… But between people you trust or between your own devices, it should work as expected for testing.

    As for allowing links with expiration, you basically have that already with what looks like the login/logout functionality. There is no actual registration, it’s just a UI for creating and deleting crypto random ID profiles.

    Lemmy and the fediverse is a good idea. The federation makes it so I can see Lemmy posts on mastodon. Etc… id like to draw a parallel in my app with the chat-view and the inteagram-view


  • I don’t think this kind of app could be an alternative to instagram because of it only being P2P with only people you know.

    The app is using webRTC which exposes IP addresses, so you wouldn’t want something like a global feed on this.

    Immich sounds interesting. I’d like to make time to check it out.



  • P2P allows for a fairly unexplored infrastructure for content moderation. In this app, the feed of images would only be from people you connect to. For people to connect to you, you have to share a crypto random id.

    As a webapp you can clear the site data by logging out. Basically, people cannot randomly connect to you and share things you don’t like.

    I won’t be adding anything like a global feed. Only content that you shared or received.

    This doesn’t remove the risk of people sending you things you don’t like so I’m all ears for an approach to that. I didn’t make much progress on the following. If there are any hard features you think would help, let me know. I’d like to make some time to create a “block contact” but it’ll take time and consideration to do it properly (so I don’t expect it soon). Things like logging out and being able to backup your profile might be enough, but not as user-friendly as it could be.

    https://www.reddit.com/r/darknetplan/comments/16qw24o/on_my_decentralized_chat_app_i_want_some_kind_of/






  • positive_intentions@lemmy.mlOPtoOpen Source@lemmy.mlP2P Framework
    link
    fedilink
    English
    arrow-up
    1
    ·
    5 months ago

    Thanks. I’ve come across tox before. It’s a good implementation. The aim of my project is not to compete, but more to demonstrate a different approach to P2P technology.

    A key detail in mine is that it’s made to work in a typical web browser. While things like chat functionality can be demonstrated in our app. The app is capable to do things like shared xr spaces and shared filesystems… Unfortunately those features are still in need of refinement before they become appealing to users, but it works for a proof-of-concept.




  • Sorry. It’s quite buggy.

    • Its best to start off by clearing all site data from the browser settings.
    • Do not have multiple tabs of the app on the same device.
    • It doesnt hurt to refresh to page.

    What you’re describing might be related to there being 2 tabs of the app running. This results in both reacting to the new-connection-event, but ultimately resulting in a data conflict.

    Plugins shouldn’t be an issue. For stronger security, i have CSP headers to try to prevent browser plugins reading data.

    If nothing works then the egg is squarely on my face and my buggy app is too buggy.