Loops

cross-posted from: https://lemmy.world/post/24641422

Kickstarter to expand the apps.

Just messing with the app, looking for fun stuff and I wanted to show one of the videos I found with my sister; but there seemingly no way to get a link? How do I get a link to a specific video to share it somewhere?

Consider creating and sharing video updates about the development progress of Loops and Pixelfed on popular social media platforms like YouTube, Twitch, TikTok, etc.

Rationale:

1. Increased visibility: Platforms like YouTube and TikTok have MASSIVE user bases, providing an opportunity to reach potential new users who may not be familiar with Loops or Pixelfed.

2. Engaging content format: Video content is highly engaging and can effectively showcase new features, UI improvements, and behind-the-scenes development processes.

3. Building community: Regular updates can help foster a sense of community and excitement among existing users, keeping them informed and involved in the project's progress.

4. Inspiration from others: Some developers are already using this approach successfully. For example:

   • Skylight Social (ATProtocol-based app): https://www.tiktok.com/@buildwithtori
   • Neptune (potential TikTok alternative): https://www.tiktok.com/@theneptuneapp

These creators are effectively using TikTok to document their development journey and build interest in their projects.

By adopting a similar strategy, Loops and Pixelfed could:

• Provide regular progress updates to the community
• Showcase new features and improvements
• Offer sneak peeks of upcoming developments
• Share insights into the development process
• Engage with users through comments and feedback

I personally believe that this approach could SIGNIFICANTLY boost awareness of Loops and Pixelfed while keeping the existing community engaged and excited about the project's future.

Loops.video looks promising as replacement for TikTok… just published a test video https://loops.video/v/60Sa-5oVYT

#loops #loopsvideo #loopsbypixelfed #tiktokban #tiktok

From yesterday:

I used https://termly.io/ to generate the Terms of Service and Privacy Policy for Loops so I could ship the TestFlight beta ASAP.

There have been several concerns raised about them, and I want you to know that we will be replacing them with a better, more clearer set of rules and policies.

Please don't assume the worst, I'm trying my best but don't have a team to help me with stuff like this.

I'll make it right.

I've seen some people complain about this and assume bad intent, such as this comment:

Loops.video steals the rights to what you upload just like any other big corporate website

Hopefully this will resolve that, beyond the fact that you'll be able to just run your own copy of the service with whatever TOS you'd like.

https://mastodon.social/@dansup/113837375760817293

Loops will have a very easy onboarding process, allowing you to use your existing Mastodon or Pixelfed account and create a new separate Loops account with your avatar, bio, and even following suggestions.

Working hard to get this shipped ASAP!

Kind of weird to not use Matrix for a federated service like Loops TBH, but maybe it'll help attract interest

The Concept

Neptune (in beta) is attempting a user-controlled algorithm that allows individuals to tailor their content feed based on personal preferences, moods, and desired aesthetics.

This approach gives users more agency over their social media experience and could be a valuable addition to Loops.

Benefits of Implementation

1. Enhanced User Experience: By allowing users to customize their feed, Loops could provide a more personalized and satisfying browsing experience.

2. Reduced Algorithmic Bias: A user-controlled algorithm could help mitigate concerns about opaque content curation and potential bias in traditional algorithmic systems.

3. Creator Empowerment: This feature could level the playing field for creators, focusing on content quality rather than arbitrary metrics like follower counts.

4. Alignment with Pixelfed's Values: A customizable algorithm aligns well with Pixelfed's principles of user control and transparency.

Potential Implementation

• Mood/Vibe Selectors: Allow users to choose from a range of moods or vibes that influence their feed content.
• Content Type Preferences: Let users adjust sliders or toggles for different content categories they want to see more or less of.
• Temporary Adjustments: Enable users to temporarily change their feed's focus without permanently altering their overall preferences.

Additional Considerations

While implementing this feature, it would be important to maintain Pixelfed's commitment to privacy and data protection. The customization process should be transparent and avoid collecting unnecessary user data.

I believe this feature could significantly enhance the Loops experience while staying true to Pixelfed's core values.

I'd be interested to see how the Pixelfed team might adapt and improve upon this concept.

I understand the effort being put into this and the amount of work it takes and I'm appreciative of those efforts. I just wanted to add my 2 cents.

• You can't delete a video once it's uploaded.
• Every user's video is chronologically in order in your feed, so if there's a user who will post 5-6 in a row and you get them all. If you leave the app, it starts over and you only see the videos uploaded most recently over again and again.
• You can add hashtags to a video description, but have to scroll to the next video to see them and you can't click them anyway.
• The search function is useless as far as searching for content.

I don't really understand. The code isn't open-source, the profiles are private by default, and... that's it? A private short video platform?

Found it mildly interesting. I like the optical illusion aspect of it

While the loops project has not been made open source yet, does anyone have an idea how they do it? Videos are data heavy and require lots or bandwidth and storage. Is the data centralized ? Where is it stored? Will we be able to self host an instance at some point?

cross-posted from: https://dubvee.org/post/2439012

This is probably the biggest feature-creep release to date (especially for a point release) lol. Most of the changes are architectural or subtle UI tweaks, so I wanted to include a few new things that would actually be noticeable.

Tesseract now supports Loops video embeds. 🎉

This has been an "ask" for a month or longer (or since Loops went live), and I'm happy to say I finally came up with a way to make this happen (Loops doesn't provide any video embed metadata so I had to get creative 😔)

As for a release date, I'm still running through tests since there were so many architectural changes this time around. If you want to help with this, please consider testing for me via the hosted instance (https://tesseract.dubvee.org/) and submitting bugs via Github or posting in this community with the bug details.

There are a few areas I wanted to touch up this release (search and modlog), but those are just going to have to wait.

Best estimate is next week assuming I don't hit any snags with the Loops integration. Again, testing and submitting buts is extremely helpful as I cannot test every possible scenario.

This feature brought to you by Crown Royal Vanilla flavored whiskey

https://mastodon.social/@dansup/113665304695257743

Kind of surprising how quickly it happened. Here's one example:

https://loops.video/v/4U2D0EEUhx

It's not too much yet, but probably something they'll need to consider. Will probably turn people off of Loops if not moderated or tagged or something

Anyone know if it's on the radar to support better integration with other Fediverse clients such that links to Loops videos can be displayed inline without going to a separate page? I've had a couple of people ask about this when I've posted videos.

Anyone know if there's any public roadmap at all, for that matter? I respect that the dev wants to get stuff right before open sourcing and all that, but it would be nice if there were some document/place I could follow along.

Additionally, it appears that the code for the backend server is intended to be public as well, but just doesn't exist outside of a readme.md document in the main branch.

This is setting off sirens, particularly the lack of a license.