shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

289
active users

#webrtc

0 posts0 participants0 posts today

FilePizza • Your files, delivered.
Peer-to-peer file transfers in your browser.

Using WebRTC, FilePizza eliminates the initial upload step required by other web-based file sharing services. Because data is never stored in an intermediary server, the transfer is fast, private, and secure.

🍕 file.pizza

file.pizzaFilePizza • Your files, delivered.Peer-to-peer file transfers in your web browser.

I like p2p communication with webRTC better and better. not having a server in between which stores messages, but only sending messages (directly or in the form of a queue) when both peers are online. writing a message queue is my next step in my #KaiOS app #webRTC #KaiOS github.com/strukturart/flop

GitHubGitHub - strukturart/flop: KaiOS p2p messenger appKaiOS p2p messenger app. Contribute to strukturart/flop development by creating an account on GitHub.

An important feature request open for over 9 years has been addressed in Firefox: simulcast support for H264 will be part of #Firefox v136

Big deal for
#WebRTC usage: This is the supposed changelog note from the assignee #AndreasPehrson

Firefox now supports sending multiple simultaneous versions of the same source over WebRTC, so called simulcast, with the H264 video codec. H264 is the second video codec after VP8 to be supported for sending simulcast.
Reasoning: Simulcast is needed by any video conferencing site that want to do large video calls, where peers are connected via a media server rather than directly to each other (peer to peer). H264 is the only other codec to be supported than VP8, and H264 simulcast is supported with hardware codecs on Android.

bugzilla.mozilla.org/show_bug.cgi?id=1210175#c28

🔥🦊 Thanks @mozillaofficial
bugzilla.mozilla.org1210175 - simulcast support for H264RESOLVED (apehrson) in Core - WebRTC: Audio/Video. Last updated 2025-02-20.

After taking a closer look at #XMPP clients for the #linux desktop, there's this frustrating "tie" for finding a favorite.

#Dino, which is likeable for being able to do video and audio calls, only has limited support for multi-user chat (complete with fancy moderation tools). These audio and video calls it can do are AMD64-only at this time.

#Gajim, which is likeable for being able to do multi-user chat well (with great moderation tools), alas, can't do audio and video calls to the other XMPP clients (like, say, #Conversations, as they use a newer #WebRTC-based method now).

So there's this strange situation where one is tempted to use both at the same time.

My takeaway is that #Conversations for #Android is the only xmpp client that I would possibly and carefully recommend to family and friends at this time, as it can cover all of the above. (#Monal on #iOS/#MacOS only has "partial" support for Multi-user chat, BTW.)

Yes I'm aware of the existence of Snikket, Quicksy, and Prav. No need to chime in on those.

Replied to Kevin Karhan :verified:

@kkarhan

thanks for the reply! far from being discouraged, i appriciate your engagement. i will try to be reasonably brief in my reponse to your points and give a general update on progress and objective.

> scout out existing solutions

i have seem similar #webapp implementation, i think so far for "that kind" of chat app, the chat app is able to demonstrate similar basic functionality. for a wider adoption, the user interface needs to be more appealing, but i think its important to have a working proof-of-concept first. the project is specifically aiming to be a #javascript #localFirst #webapp.

a couple notable similar implementation to mine are:
- github.com/cryptocat/cryptocat
- github.com/jeremyckahn/chitcha
(im sure there are many more, but i think my approach is yet different and unique to the ones i've come across.)

> DO NOT DIY ENCRYPTION!

this is indeed a reccomended practice i have seen several times. here is a previsous reddit post on the matter: reddit.com/r/cryptography/comm ... tldr; the underlying implementation provided by the browser is the best way to go. i have implemented the #encryption using the #webcrypto #api. i aim to not use a library for this.

i generally try to word things in a way that users can provide feedback on features. the app is still in a very early stage, but has a reasonable amount of features. im generally open to requests and questions.

> minimum viable product

what you see as the chat app is also the #minimum #viable #product. i think its sufficiently demonstrates the basic functionality of a chat app. i think the next step is to make the app more stable and user friendly.

those other apps youve mentions ive come across before. what sets my approach apart is that mine it's purely a webapp. with what id like to describe as #p2p #authentication over #webrtc, im able to remove reliance on a backend for #authenticate #data #connections. in some cases, bypass the internet (wifi/hotspot). while there are several ways to #selfhost, in this approach of a #javascript implementation, im able to store large amounts of data in the browser so things like images and #encryptionKeys can be #selfhosted" in the browser. while this form has nuanced limitations, it also has interesting implications to security and privacy.

there are many nice features from the different apps you mentioned and i think i have some unique features too. the bottle neck in this project is that i dont put in enough time to the app.

> feel free to slowly ibtegrate them.

this is basically already my approach to get the app to where it is now.

thanks for the luck, take care and i hope you stay tuned for updates.

GitHubGitHub - cryptocat/cryptocat: Secure chat software for your computer.Secure chat software for your computer. Contribute to cryptocat/cryptocat development by creating an account on GitHub.

Did I create the ultimate tool to watch anime with friends?
:blobcatuwu:

xtream is a website where you can "upload" any video and watch among other people, without loss of quality.

Files are actually transferred privately via a P2P connection, without going through my server.

Each user can choose their preferred audio and subtitle language. Without installing programs or extensions.

🧵

#P2P#FOSS#Rust
Replied in thread

#KaiOS #webRTC #leaflet I've made progress on my webRTC chat app for KaiOS. I've created a map component that allows the user to share their location and live location. In the next step I'll enable the sharing of audio messages. I'm still thinking about how I'm going to solve this so that it remains easy to use.

github.com/strukturart/flop

GitHubGitHub - strukturart/flop: KaiOS p2p messenger appKaiOS p2p messenger app. Contribute to strukturart/flop development by creating an account on GitHub.