• 5 Posts
  • 142 Comments
Joined 1 year ago
cake
Cake day: August 28th, 2023

help-circle
  • Funny comic.

    On a serious note though - AI is advanced means of production. All of it might not be 100% production ready today, but it’s getting there soon. Our goal must be to seize this means of production (make AI companies publicly owned with a consumer cooperative operational model). Denying its existence only serves the interests of the bourgeoisie, as it makes us unprepared when it actually starts replacing jobs en masse.





  • Please do not use any Chromium forks if you care about privacy and an open web. Cromite uses the Chromium engine, which is by Google.

    “But Chromium is open source, so that means good, no?”: Not always. Developing a browser is very hard and requires a lot of time and resources. Therefore, even when you can fork Chromium in theory, maintaining this separate fork becomes incredibly difficult. Google of course does not allow any privacy centric code to be pushed to the Chromium codebase. It in fact, does the opposite. Look at the ManifestV3 drama for instance. The solution to all of this is using Firefox mobile or forks of it.










  • UraniumBlazer@lemm.eeOPtoLemmy@lemmy.mlHow can we deal with real time notifications
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    11 months ago

    Webpush or UnifiedPush would be the answers, but neither is currently supported by Lemmy.

    I see. I was looking at the Novu project that seems to be working with expo notifications as well. Have you heard of it before? If you have, do you know how it is different from Webpush? I tried researching on this, but didn’t really find any answers.

    please don’t abuse Lemmy’s DMs as a sort of instant messenger

    I’ll tell you what the problem is. I think that a Discord x Reddit platform would be absolutely perfect. Chatroom conversations that can be indexed by search engines + posts would be very cool imo. E2EE can be worked on relatively easily for private messaging (I’ve tried it with no real problems). Chatrooms for communities with different channels can easily be done by creating a special post for every community, where all replied under it are the chat messages (sorted by new). This can make stuff like megathreads much easier and much more accessible.

    Unfortunately, there just are no alternative to make this possible. Matrix is a PITA to implement in react native, and not indexable. To implement XMPP by E2EE-ing it, it too is a PITA for react native. Plus, we would have to deal with separate databases, separate logins, registrations, different MFA, etc.

    This is why I decided to go with Lemmy’s DM thing. I would have to somehow E2EE it, which I would have to do for the alternatives either ways. Which is why I see much potential in working with this.