Show previous comments
As I mentioned, I got a short domain for @loops Soon https://l.oops.bio/@dansup will redirect to my Loops profile in the app! @dansup Loops will be limited to Android and iOS, with the exception of video links which will have web previews. I don't have the bandwidth to support web, and this enables us to build much richer experiences like AR Filters! Loops will be a "sleeper" fediverse app, with the default appearance of a single flagship instance You will be able to run your own loops server, and login to the app, but it will be less emphasized The goal is to make @loops as user friendly, without any fediverse knowledge, as possible When the users decide they want to migrate, they can take advantage of full account migration between Loops servers! We're really onto something here...
Show previous comments
Show previous comments
Why not: TestFlight may take another week, so I'm thinking about distributing a @loops Android APK for the initial beta! That would enable me to get it in the hands of beta testers the quickest 🤔 Anonymous poll
Poll
Ship Android Beta ASAP
157
75.8%
Wait for TestFlight
207 people voted. 50
24.2%
Voting ended 25 March at 12:03. I’m considering imposing some limit like Loops get deleted after 1 month or you can only have 20 loops at a time. It would def give it a diff vibe than TikTok and encourage less staged and more in the moment content I think. Thoughts?
Show previous comments
@dansup @dansup I like it. If you were to go with a limit on the number of videos, it would be cool to gain more videos the older your account is. That way spam accounts can max post one video and older accounts are rewarded with more video slots. If you do this though, I would want an option to automatically post the videos to a peertube account. I put a lot of effort into most of my videos so I wouldn't want them to disappear forever. @dansup tbh I don't really like this idea. I feel like it would make adoption harder, as well as cause link rot/archival problems. I made a few other federation optimizations like sharing the private keys for every local user, and an experimental new protocol transport for real time federation between loops servers I'm really pushing the boundaries, again 😎 > sharing the private keys for every local user This sounds weird. Did you mean public keys? @dansup I would prefer you didn't share keys. Http sigs should function as a remote authentication method. Sharing the keys makes it impossible to know that a message is from who it claims to be. That would mean enforcing blocks would require blocking everyone who shares that key.
Show previous comments
@dansup @loops so, the immediately obvious way to do this is to make sure the username isn't in the actor ID or any object IDs. Then, you can set whatever you want as the `preferredUsername`, and changing it won't change the ID for the actor. I think the only problem is that some systems, like Mastodon, favour the Webfinger ID over the actor ID. We're talking about this at the CG: https://github.com/swicg/activitypub-webfinger/issues/10 I spent way to long on the Loops video editor and it's not close to being done Will be delaying the editor so we can focus on getting the beta shipped ASAP In the meantime, we will allow you to select a video from your camera roll (that you can edit with CapCut or whatever) @dansup will you add moving an account? Like, let's say I uploaded few videos to loops using a pixelfed account, and I want to move all my videos, followers, etc, to a mastodon account. I'm currently building out the new loops backend (loopd) Laravel 11 + Sanctum + Valet = supercharged productivity In less than an hour I already have a production backend deployed with auth and a few API endpoints 💪
Show previous comments
Hey Dan, I was wondering if you're familiar with Casey Neistat's failed social network Beme. I was on it at the time, and I always found the emphasis on authenticity hugely inspiring, and I shared far more on it than I ever did on instagram. Not sure what your vision for loops is, but I'm sure it'll be awesome. I just wanted to leave this with you to see if you get anything out of it: TikTok, Instagram reels, VK clips and other similar services work because they have everything anyone has ever posted on there. Millions of minutes of video are uploaded every minute, and all that feeds The Algorithm™, giving it the freedom to choose what it serves to you. How are you going to address the problem of not having enough content in Loops due to its decentralized nature? So when someone starts a new server, where would the content come from? Would you just federate everything to all known network? I am a bit worried about publishing the #loops mobile app source code, specifically the camera logic There are no existing libraries or examples, that I'm aware of, that do what Loops Camera does I'm mostly worried about shady clone apps or other uses that violate our license I think an amicable solution would be to publish the app source, but with a placeholder basic camera while shipping the full camera to App Stores What do you think?
Show previous comments
@dansup How about creating a library with the camera code and a really strong license? Add some features that will make it easily identifyable but can't be removed easily. That way copycats will either be identified quickly or have to put in enough effort to make copying unattractive. @dansup Do you use Open Source libraries in the software you build? Often libraries that did not exist until someone published them. It feels like somewhat against the very spirit of open protocols and collaboration to be considering publishing something like that closed source, pulling the ladder up as it were. @dansup |
@dansup @pixelfed I personally hate Stories. Can you disable them?
@dansup @pixelfed Looking great!
One question though, can you view the stories in f.ex a mastodon app? If yes, how does the story deletion feature work?
@dansup @pixelfed is that a good thing?