Profile avatar
soundsky.bsky.social
⏯️ Open Beta: https://soundsky.cloud/ 🎡 open soundcloud alternative for Music makers built with bsky.social and storing on your account/PDS. Testers/Contributors Wanted! #soundSky #audioSky #musicsharing
76 posts 51 followers 13 following
Regular Contributor
Active Commenter

Soundcloud @soundcloud.dev please make up your mind. Do I have 180 mins or 2 tracks? Uploading to @soundsky.bsky.social instead today.

Uploaded my first track to @soundsky.bsky.social ( #Soundcloud alternative built on @atproto.com :: Looking and sounding great for far! Listen here soundsky.cloud?artist=rende...

We're testing a very experimental custom-lexicon version of soundSky storing data in its own forma and we need some brave testers souls to iron out a few bugs! Please reply or PM if you'd like to waste 10-15 minutes for some authentic #opensource kudos!

Oh? Interessante....

Are you into SoundSky? Join our open source project and help us maintain and extend its functionality. You don't have to be a developer to contribute - Ideas are the real fuel of innovation. PM or PR if interested github.com/soundskycloud/soundsky #opensource #soundsky #soundcloud #contribute #share

uhhh...... this looks..... dope????????????!!!!!! @sansemusic.com @intelectconfig.wtf @creitingameplays.com @calvobianco.com @janebellsucks.com @halfvolume.bsky.social @bandcamp.com

Notifications are ready for testing in #soundSky πŸ‘‡ soundsky.cloud

Album views are ready for testing! Style is still basic, user feedback and requests are highly appreciated πŸ‘‡ try it at soundsky.cloud #soundSky

Goodbye Soundcloud πŸ‘‹ Hello #soundSky ☁️

Sky is the Limit @soundsky.bsky.social 🎢☁️ #soundSky #music #audio #sharing #bsky

#soundSky allows uploads up to the PDS limit (usually 100MB) but larger files are just too hard to load for wavesurfer until we add our own waveforms. To avoid crashing, larger files might fallback to a regular (as in ugly) HTML <audio> player πŸ‘‡ Thanks @daibakusho.bsky.social for the bug report πŸ”₯

#soundSky wants to remain a client-side only browser app without any backend so we need to make compromises and store as much info as possible within our posts. In the latest version we're stashing refs to cover artwork using hidden tags! Is this unholy in #atproto? we'll find out soon...