Skip Navigation

User banner
Posts
161
Comments
257
Joined
2 yr. ago

  • You are essentially sharing a file link via MS Teams.

    Instead of keeping the actual file on OneDrive, it is hosted on your own (Nextcloud) server. Sorry but how it leads to privacy issue?

  • Nextcloud[1] is an open source and self-hostable SaaS product.

    Instead of using OneDrive and Google Drive (and similar proprietary solutions), Nextcloud is a better solution from Privacy POV, IMO.

    [1] https://en.wikipedia.org/wiki/Nextcloud

    • Nvidia proprietary driver
    • Docker Engine (Portainer, AdGuardHome, LibReddit, Nitter, Invidious)
    • Install and tweak Firefox setup
    • Steam Client
    • Gnome extensions
    • Gnome Shell Theme and Icon themes
    • Nextcloud Client
  • Here is my understanding of it -

    Currently, TB uses POP3/IMAP protocol to access your Mailbox on Exchange Server.

    Ideally, it should be done via MS EWS Web API [1][2] which TB currently doesn't support, but MS Office Outlook does.

    Given that MS Exchange is heavily used in corporate/company setup, it[3] will put TB on par with Outlook in that regard.

    [1] https://www.techtarget.com/searchwindowsserver/definition/Exchange-Web-Services-EWS

    [2] https://www.envisionup.com/blog/pop3-imap-microsoft-exchange-email-platform-use/

    [3] https://bugzilla.mozilla.org/show_bug.cgi?id=1847846

  • Quality control is important for a project that is going to be supported for long time, and used by many. Slow but steady is a right approach for open source project, IMO.

  • Request: Your IP > Apple (1st) relay node > 3rd party (2nd) relay node > Website

    Response: Your IP < Apple (1st) relay node < 3rd party (2nd) relay node < Website

    Whoever has access to both relay nodes, can easily track you end-to-end.

    As for Apple, they claim the 1st relay node is owned by them, and 2nd relay node is owned by 3rd party. (Source: https://www.apple.com/icloud/docs/iCloud_Private_Relay_Overview_Dec2021.pdf)

    In theory, it should not be a privacy concern because -

    • Website will see the request coming from 2nd relay node's IP.
    • 2nd relay node will see the request is coming from Apple (1st) relay node's IP.
    • So, only Apple knows your IP.
  • The really powerful thing about Facebook ads is in your ability to layer targeting options on top of one another, gradually making your audience more and more specific. An extreme (and hilarious) example of the power of hypertargeting was featured in AdWeek last year, when a marketing pro targeted his roommate with ads so specific the poor guy thought he was being cyberstalked.

    🤮

  • The application will stream the selected monitor if the mutter screencast portal is available. If it is unavailable, a fallback to X11 based frame grabbing will happen. As such, it should work fine in almost all setups.

    Source: https://gitlab.gnome.org/GNOME/gnome-network-displays

  • If your use cases (a.k.a. requirements) are met by your current distro, never switch.

    If you are satisfied with stability, availability of support, quick availability of security patches, never switch.

    This is particularly important when you are using your Linux desktop as your daily driver.

    Most you can do is to check what additional features other distros are offering (rolling release, hardened/zen kernel, x86-64-v2/3 support, file system type, user base, availability of packages, package formats, overall documentation etc.), validate if you really need those features.

    If you are interested or just curious to test those features, install that distro on a VM (QEMU/KVM) to try it out first safely. Use it on VM for a while, make yourself comfortable with it. Once you are satisfied with it, only then switch.