Notices tagged with p2p

Today @ 18:30 in Dublin: Come hear me talk about the Small Web and watch me demonstrate the current state of Kitten, Domain, and Place.

https://meetu.ps/e/Ny9vK/H1WXJ/i

#ireland #dublin #SmallWeb #talk #presentation #web #dev #JavaScript #NodeJS #htmx #WebSockets #StreamingHTML #selfHosting #decentralisation #p2p #cryptography #dubSec #Kitten #Domain #Place #SmallTech

How would peer-to-peer collaboration work in #LibreOffice? Our Design community has been exploring ideas and working on mockups: https://design.blog.documentfoundation.org/2024/07/17/peer-to-peer-collaboration-with-libreoffice/ #foss #opensource #p2p

I went through all the Kitten examples¹ and tutorials² this week to ensure everything is working given Kitten has been evolving rapidly and fixed a number of little issues I encountered.

If you notice any others, please do let me know:
https://codeberg.org/kitten/app/issues

:kitten:💕

¹ https://codeberg.org/kitten/app/src/branch/main/examples
² https://kitten.small-web.org/tutorials

#Kitten #SmallWeb #server #framework #web #dev #HTML #CSS #hypermedia #HTMX #JavaScript #JS #peerToPeer #p2p

The new and improved Settings section for Kitten (Small Web/peer-to-peer web) apps is coming along nicely.

Should be live this week.

#Kitten #SmallWeb #Settings #SmallTech #p2p #peerToPeer #web #dev

A #p2p future for the web is the radical idea that its bad to put all data in a single place owned by 3 companies and rented by a few hundred. The internet wasnt a mistake, the cloud was a mistake. Platforms were a mistake. A mistake where its not only possible but routine for "everyone's health data" to get stolen. https://infosec.exchange/@patrickcmiller/112341111375581551

I need to share my health data with like 3 people that arent me. Why on earth is that data in the same pile as literally everyone else's.

(And remember, Kitten is a server. So you don’t have to download and install a framework every time you start a project ­– no npx this or that or anything. Just start writing your code and run `kitten`.)

https://codeberg.org/kitten/app

#Kitten #SmallWeb #web #dev #server #framework #HTML #CSS #JavaScript #htmx #WebSockets #p2p

Heads up: if you were playing with Kitten¹ on macOS, you might have noticed that some of the commands were exiting with a truncated header.

This has now been fixed and all commands should look and work exactly the same on macOS as they do on Linux.

:kitten: 💕

¹ https://codeberg.org/kitten/app

#Kitten #SmallWeb #macOS #linux #web #dev #javaScript #nodeJS #htmx #WebSockets #p2p

@serapath that's an interesting one as torrents still technically work, and the infustrcurtue is still online, though riddled with ads and SPAM. So while technically this is still functioning, it is socially degraded and pushed into the shadow by the #dotcons like Netflix and Amazon Prime etc.

"* #p2p was the poster child of the era of the #openweb it was caught in the quicksand of legal issues, the shadow that was left was eclipsed by "free to use" #dotcons Now finds it hard to come back due to mobile devices not having an IP address, thus most people not actually able to use p2p reliably."

An example of this, my torrent client is regularly blocked by my mobile internet provider - I live on a boat, and yes I do get round this but most people would stumble when this happens.

Hey fedifolks! I was hoping to get some bikeshedding feedback on a new #FEP we're working on at #DistributedPress.

tl;dr we want #ActivityPub objects to link to #P2P URLs for alternate ways to load them. Right now I'm debating between putting them in `alsoKnownAs` or into the `url` field. e.g. `"alsoKnownAs": ["ipns://staticpub.mauve.moe"]` for @mauve@staticpub.mauve.moe

I worry that field is already in use and that it could cause trouble. Would a new field name be better? Maybe `alternateURL`?

Projects like Spritely and Veilid point to a future of the DWeb beyond blockchain and federation.
https://www.eff.org/deeplinks/2023/12/meet-spritely-and-veilid #dweb #p2p

I can’t believe I last did a proper post about Jami as far back as 2019 last. I mention it a lot, and it was included run a debate today on my Friendica site, but I realised it does deserve a proper feature post of its own.

Jami is a proper peer-to-peer messaging app, much like RetroShare, but Jami is probably a bit easier to use than RetroShare. It has no central servers that can be blocked or denied service. It has clients that can install easily on all operating systems, and all your data is stored locally on the client.

So, as with other P2P apps if you lose your private key or configs, you’ve lost all access to that client identity. There is no central service to reset any password. So, rule 1 is to backup your credentials, or have it also work on a second device.

The other important thing is Jami requires no e-mail or phone number to register with. There is no way for that identity to be linked to you personally. And like with RetroShare, SimpleX, Session, Wire, etc there is also no way any friend or anyone else can find you, unless you tell them how to connect with you. There is no way to search for friends etc. Security and privacy-wise, it is very much on par with apps like SimpleX, RetroShare, Session, etc.

It is fully open source and has E2EE for messaging. On a local network it requires no Internet to connect clients. Across the Internet the application uses distributed hash tables (DHT) to establish communications. This technology eliminates the use of centralized registers (servers) and the retention of personal data. Mass surveillance can not be undertaken by the servers as there is not any.

It has the following features:

• Instant messaging
• Group chats
• Video Conferences
• Audio calls
• Audio and video messages
• Screen sharing
• File sharing
• Extensions for enhanced functionalities
• Ability to use it as an SIP (Session Initiation Protocol) client

So, it is also much more than just a plain messenger app.

The linked article below does not go into its technology, but is focussed more on how to install and use it.

See itsfoss.com/jami/
#Blog, #decentralised, #opensource, #P2P, #privacy, #technology

@xianc78 Well, my point is why can’t a #P2P chat apps use custom blockchains for group chats, with each member of that chat serving as a node in the blockchain?

Wait…how come #P2P group chats don’t work, but the #Blockchain works? Aren’t #blockchain nodes connected through #P2P methods?

@jon @elac This is what I mean by it and what I’m building (a peer-to-peer, personal web). It’s not a trademark so anyone can use it for anything.

https://ar.al/2020/08/07/what-is-the-small-web/

#SmallWeb #p2p #web

@mauve have you looked at #libp2p's gossipsub?

I just started looking at it because MaidSafe are implementing support for it in #SafeNetwork and I'm wondering if it would be possible to implement support for #ActivityPub on top of #gossipsub.

It would be amazing if this potentially widely used library were a way to link Safe and other #p2p networks to the #fediverse

FYI I posted about this on the Safe forum and put some references in the OP directly above: https://safenetforum.org/t/gossipsub-what-dat/38718/2?u=happybeing

@finner The readme clearly needs work (it does) :)

In a nutshell: it’s a system for building and deploying peer-to-peer web applications (small web) that can communicate with each other using end-to-end encryption.

Simple/early example: https://ar.al/2023/02/20/end-to-end-encrypted-kitten-chat/

However, since that’s layered onto the regular web features and uses plain web tech, you can also build old school web apps that don’t necessarily make use of the p2p features.

#SmallWeb #Kitten #p2p #web #dev

@serapath @bengo @evan PS. The *Big Web* is hostile to peer to peer. The Small Web *is* (or at least will be, once it’s a thing) peer to peer.

https://ar.al/2023/02/20/end-to-end-encrypted-kitten-chat/

#SmallWeb #BigWeb #SmallTech #BigTech #peerToPeer #p2p #web

@coolboymew @alex @graf@poa.st @Moon And once more I'm vindicated in my statements that hosting anything #federated or #p2p on the #clearnet as non-corporations is unsafe and made intentionally so too.

(That specific incident feels like old news at this point, but anyway.)

Dang, looks like #Mastodon doesn't handle relative URIs when parsing #ActivityPub / #ActivityStreams data.

For example I can't set the `id` of a post to be a relative URL since it loads it as raw JSON.

https://github.com/mastodon/mastodon/blob/main/app/services/activitypub/fetch_remote_status_service.rb#L37

This makes it harder to publish static data to #p2p

#Piracy #AdBlock #YouTube #Netflix #Invidious #DRM #Torrent #P2P #FileSharing #Ads #Piped #Streaming #StreamingServices