this post was submitted on 18 Apr 2024
21 points (100.0% liked)

Privacy Guides

16813 readers
7 users here now

In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.

This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.


You can subscribe to this community from any Kbin or Lemmy instance:

Learn more...


Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!

Want to get involved? The website is open-source on GitHub, and your help would be appreciated!


This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.


Moderation Rules:

  1. We prefer posting about open-source software whenever possible.
  2. This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
  3. No soliciting engagement: Don't ask for upvotes, follows, etc.
  4. Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
  5. Be civil, no violence, hate speech. Assume people here are posting in good faith.
  6. Don't repost topics which have already been covered here.
  7. News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
  8. Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
  9. No help vampires: This is not a tech support subreddit, don't abuse our community's willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
  10. No misinformation: Extraordinary claims must be matched with evidence.
  11. Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
  12. General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.

Additional Resources:

founded 1 year ago
MODERATORS
 

Hello, I'm the developer behind Materialious. Perhaps you came across my post a few weeks back regarding the launch of my Material design frontend for Invidious.

I'm reaching out to gauge interest in expanding Materialious to serve as a unified interface for TikTok (Via Proxitok), Twitch (Via SafeTwitch), YouTube (Via Invidious), and potentially even search (Via SearxNG).

I'd love to hear your ideas and thoughts on this!

you are viewing a single comment's thread
view the rest of the comments
[–] Scolding0513@sh.itjust.works 1 points 7 months ago (5 children)

I agree with Mora. it's a really bad idea to make this in a whole different project. it splits up communities, creates confusion, and reduces anonymity sets.

Why not work with the invidious team and get your theme added to the project, and maybe contribute the other changes you may have made?

god knows invidious needs a way better UI/UX anyway

[–] Ward@lemmy.nz 1 points 7 months ago* (last edited 7 months ago) (1 children)

Isn't just a theme, is a completely different application built on top of Invidious' API. What works completely differently to Invidious' current UI. A LOT of things are handled different then how Invidious handles it on their frontend. Replacing Invidious current interface with Materialious isn't a good idea, because its quite a bit bigger & requires JS compared to Invidious' current UI.

Calling Materialious a theme would be like calling clipious a theme.

[–] Scolding0513@sh.itjust.works 1 points 6 months ago (1 children)

yeah but clipious just connects to existing invidious instances, so it's just a frontend to invidious. you are making your own frontend and backend both

[–] Ward@lemmy.nz 1 points 6 months ago (1 children)

Materialious does currently just use Invidious' API. If extending it requires a custom backend it will be a completely different project (what will still be using Invidious)

[–] Scolding0513@sh.itjust.works 1 points 6 months ago (1 children)

does it connect by default to already-existing invidious instances? guess im confused now

[–] Ward@lemmy.nz 1 points 6 months ago

It requires the Invidious instance to have the correct COR values for Materialious, but yes connects to a existing instance.

load more comments (3 replies)