home.social

#dataownership — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #dataownership, aggregated by home.social.

fetched live
  1. Twenty-two import sources. The social network roster is closed.

    Bluesky, Facebook, Instagram, Mastodon, Pixelfed, Threads, Twitter/X — plus every blog platform worth naming, and one more kind for the ones that don't exist any more.

    Yes, it's a blog engine. You can also point it at everything you ever wrote on somebody else's website.

    #blogsh #IndieWeb #SelfHosted #DataOwnership

  2. Twenty-two import sources. The social network roster is closed.

    Bluesky, Facebook, Instagram, Mastodon, Pixelfed, Threads, Twitter/X — plus every blog platform worth naming, and one more kind for the ones that don't exist any more.

    Yes, it's a blog engine. You can also point it at everything you ever wrote on somebody else's website.

    #blogsh #IndieWeb #SelfHosted #DataOwnership

  3. Twenty-two import sources. The social network roster is closed.

    Bluesky, Facebook, Instagram, Mastodon, Pixelfed, Threads, Twitter/X — plus every blog platform worth naming, and one more kind for the ones that don't exist any more.

    Yes, it's a blog engine. You can also point it at everything you ever wrote on somebody else's website.

    #blogsh #IndieWeb #SelfHosted #DataOwnership

  4. Twenty-two import sources. The social network roster is closed.

    Bluesky, Facebook, Instagram, Mastodon, Pixelfed, Threads, Twitter/X — plus every blog platform worth naming, and one more kind for the ones that don't exist any more.

    Yes, it's a blog engine. You can also point it at everything you ever wrote on somebody else's website.

    #blogsh #IndieWeb #SelfHosted #DataOwnership

  5. Twenty-two import sources. The social network roster is closed.

    Bluesky, Facebook, Instagram, Mastodon, Pixelfed, Threads, Twitter/X — plus every blog platform worth naming, and one more kind for the ones that don't exist any more.

    Yes, it's a blog engine. You can also point it at everything you ever wrote on somebody else's website.

    #blogsh #IndieWeb #SelfHosted #DataOwnership

  6. 95 % of the posts in my Facebook export were not written on Facebook.

    They were mirrored in from Twitter, Posterous, the whole crosspost era. The importer recognises them and skips them, with a count — the platforms they actually came from have their own exports, and those carry the originals.

    Ask for the export. From all of them.

    #blogsh #DataOwnership #SelfHosted

  7. 95 % of the posts in my Facebook export were not written on Facebook.

    They were mirrored in from Twitter, Posterous, the whole crosspost era. The importer recognises them and skips them, with a count — the platforms they actually came from have their own exports, and those carry the originals.

    Ask for the export. From all of them.

    #blogsh #DataOwnership #SelfHosted

  8. 3 hours to v1.0. 🚀

    The part I'm proudest of: it imports your Tumblr, Twitter archive, WordPress export, Mastodon and Pixelfed data. Not into a database — into plain text files in a folder you own.

    I moved over 13,000 of my own posts through it. That's how it got written.

    No database. No gems. No admin. Just ./blog.sh

    #blogsh #IndieWeb #SelfHosted #DataOwnership

  9. 3 hours to v1.0. 🚀

    The part I'm proudest of: it imports your Tumblr, Twitter archive, WordPress export, Mastodon and Pixelfed data. Not into a database — into plain text files in a folder you own.

    I moved over 13,000 of my own posts through it. That's how it got written.

    No database. No gems. No admin. Just ./blog.sh

    #blogsh #IndieWeb #SelfHosted #DataOwnership

  10. Decentralized browser-based P2P E2EE messaging.

    The key detail that sets this apart from other messaging apps is the browser-based client-side cryptography philosophy.

    No need to install anything. Your ID is crypto-random and so the app doesnt need to rely on any central registration system like phone numbers. Your ID is unguessable and to connect to someone, you have to explicitly share it.

    WebRTC has other nuances like being to route through a shared network for secure/faster transfer.

    I hope this project has reached a level i can share the following details. I've made a genuine effort towards documentation and transparancy. I dont think it'll ever be enough and so im still concerned it isnt ready to share. While im using AI throughout. This is not a vibecoded project. There is attention throughout for unit tests and formal-verification. With your feedback, id like to make improvements for clarity throughout.

    This version of the app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. I know it's impossible for any system to be the "world's most secure", but that isnt a reason to not try. By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possible.

    * [Enkrypted.Chat](enkrypted.chat/)

    This is intended to demonstrate client-side managed secure cryptography.

    * [Introducing Enkrypted Chat](positive-intentions.com/blog/i)
    * [Whitepaper (work-in-progress)](positive-intentions.com/docs/t)
    * [Protocol Spec (work-in-progress)](positive-intentions.com/docs/t)
    * [Roadmap](positive-intentions.com/docs/t)

    I know ive tried to compress a lot of my journey into one post. The project above is going to be tricky to understand. Feel free to reach out for clarity on any of the details.

    IMPORTANT: While this is aiming to provide a secure experience, It is [not audited or reviewed](reddit.com/r/CyberSecurityAdvi). **Shared for testing, feedback and demo purposes only.** Please use responsibly.

    #Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #OpenSource #SelfHosted #BetaTesting #FeedbackWelcome #TechDemo #ProofOfConcept #BuildInPublic #IndieDev #DevCommunity

  11. Decentralized browser-based P2P E2EE messaging.

    The key detail that sets this apart from other messaging apps is the browser-based client-side cryptography philosophy.

    No need to install anything. Your ID is crypto-random and so the app doesnt need to rely on any central registration system like phone numbers. Your ID is unguessable and to connect to someone, you have to explicitly share it.

    WebRTC has other nuances like being to route through a shared network for secure/faster transfer.

    I hope this project has reached a level i can share the following details. I've made a genuine effort towards documentation and transparancy. I dont think it'll ever be enough and so im still concerned it isnt ready to share. While im using AI throughout. This is not a vibecoded project. There is attention throughout for unit tests and formal-verification. With your feedback, id like to make improvements for clarity throughout.

    This version of the app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. I know it's impossible for any system to be the "world's most secure", but that isnt a reason to not try. By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possible.

    * [Enkrypted.Chat](enkrypted.chat/)

    This is intended to demonstrate client-side managed secure cryptography.

    * [Introducing Enkrypted Chat](positive-intentions.com/blog/i)
    * [Whitepaper (work-in-progress)](positive-intentions.com/docs/t)
    * [Protocol Spec (work-in-progress)](positive-intentions.com/docs/t)
    * [Roadmap](positive-intentions.com/docs/t)

    I know ive tried to compress a lot of my journey into one post. The project above is going to be tricky to understand. Feel free to reach out for clarity on any of the details.

    IMPORTANT: While this is aiming to provide a secure experience, It is [not audited or reviewed](reddit.com/r/CyberSecurityAdvi). **Shared for testing, feedback and demo purposes only.** Please use responsibly.

    #Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #OpenSource #SelfHosted #BetaTesting #FeedbackWelcome #TechDemo #ProofOfConcept #BuildInPublic #IndieDev #DevCommunity

  12. Decentralized browser-based P2P E2EE messaging.

    The key detail that sets this apart from other messaging apps is the browser-based client-side cryptography philosophy.

    No need to install anything. Your ID is crypto-random and so the app doesnt need to rely on any central registration system like phone numbers. Your ID is unguessable and to connect to someone, you have to explicitly share it.

    WebRTC has other nuances like being to route through a shared network for secure/faster transfer.

    I hope this project has reached a level i can share the following details. I've made a genuine effort towards documentation and transparancy. I dont think it'll ever be enough and so im still concerned it isnt ready to share. While im using AI throughout. This is not a vibecoded project. There is attention throughout for unit tests and formal-verification. With your feedback, id like to make improvements for clarity throughout.

    This version of the app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. I know it's impossible for any system to be the "world's most secure", but that isnt a reason to not try. By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possible.

    * [Enkrypted.Chat](enkrypted.chat/)

    This is intended to demonstrate client-side managed secure cryptography.

    * [Introducing Enkrypted Chat](positive-intentions.com/blog/i)
    * [Whitepaper (work-in-progress)](positive-intentions.com/docs/t)
    * [Protocol Spec (work-in-progress)](positive-intentions.com/docs/t)
    * [Roadmap](positive-intentions.com/docs/t)

    I know ive tried to compress a lot of my journey into one post. The project above is going to be tricky to understand. Feel free to reach out for clarity on any of the details.

    IMPORTANT: While this is aiming to provide a secure experience, It is [not audited or reviewed](reddit.com/r/CyberSecurityAdvi). **Shared for testing, feedback and demo purposes only.** Please use responsibly.

    #Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #OpenSource #SelfHosted #BetaTesting #FeedbackWelcome #TechDemo #ProofOfConcept #BuildInPublic #IndieDev #DevCommunity

  13. Decentralized browser-based P2P E2EE messaging.

    The key detail that sets this apart from other messaging apps is the browser-based client-side cryptography philosophy.

    No need to install anything. Your ID is crypto-random and so the app doesnt need to rely on any central registration system like phone numbers. Your ID is unguessable and to connect to someone, you have to explicitly share it.

    WebRTC has other nuances like being to route through a shared network for secure/faster transfer.

    I hope this project has reached a level i can share the following details. I've made a genuine effort towards documentation and transparancy. I dont think it'll ever be enough and so im still concerned it isnt ready to share. While im using AI throughout. This is not a vibecoded project. There is attention throughout for unit tests and formal-verification. With your feedback, id like to make improvements for clarity throughout.

    This version of the app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. I know it's impossible for any system to be the "world's most secure", but that isnt a reason to not try. By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possible.

    * [Enkrypted.Chat](enkrypted.chat/)

    This is intended to demonstrate client-side managed secure cryptography.

    * [Introducing Enkrypted Chat](positive-intentions.com/blog/i)
    * [Whitepaper (work-in-progress)](positive-intentions.com/docs/t)
    * [Protocol Spec (work-in-progress)](positive-intentions.com/docs/t)
    * [Roadmap](positive-intentions.com/docs/t)

    I know ive tried to compress a lot of my journey into one post. The project above is going to be tricky to understand. Feel free to reach out for clarity on any of the details.

    IMPORTANT: While this is aiming to provide a secure experience, It is [not audited or reviewed](reddit.com/r/CyberSecurityAdvi). **Shared for testing, feedback and demo purposes only.** Please use responsibly.

    #Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #OpenSource #SelfHosted #BetaTesting #FeedbackWelcome #TechDemo #ProofOfConcept #BuildInPublic #IndieDev #DevCommunity

  14. Decentralized browser-based P2P E2EE messaging.

    The key detail that sets this apart from other messaging apps is the browser-based client-side cryptography philosophy.

    No need to install anything. Your ID is crypto-random and so the app doesnt need to rely on any central registration system like phone numbers. Your ID is unguessable and to connect to someone, you have to explicitly share it.

    WebRTC has other nuances like being to route through a shared network for secure/faster transfer.

    I hope this project has reached a level i can share the following details. I've made a genuine effort towards documentation and transparancy. I dont think it'll ever be enough and so im still concerned it isnt ready to share. While im using AI throughout. This is not a vibecoded project. There is attention throughout for unit tests and formal-verification. With your feedback, id like to make improvements for clarity throughout.

    This version of the app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. I know it's impossible for any system to be the "world's most secure", but that isnt a reason to not try. By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possible.

    * [Enkrypted.Chat](enkrypted.chat/)

    This is intended to demonstrate client-side managed secure cryptography.

    * [Introducing Enkrypted Chat](positive-intentions.com/blog/i)
    * [Whitepaper (work-in-progress)](positive-intentions.com/docs/t)
    * [Protocol Spec (work-in-progress)](positive-intentions.com/docs/t)
    * [Roadmap](positive-intentions.com/docs/t)

    I know ive tried to compress a lot of my journey into one post. The project above is going to be tricky to understand. Feel free to reach out for clarity on any of the details.

    IMPORTANT: While this is aiming to provide a secure experience, It is [not audited or reviewed](reddit.com/r/CyberSecurityAdvi). **Shared for testing, feedback and demo purposes only.** Please use responsibly.

    #Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #OpenSource #SelfHosted #BetaTesting #FeedbackWelcome #TechDemo #ProofOfConcept #BuildInPublic #IndieDev #DevCommunity

  15. Day 290

    If a journalist eventually finds it, the story waiting for them is no longer “Amazon misspelled an actor’s name.”

    It is:

    “A German woman spent nearly a year documenting a systemic catalogue-integrity problem while every major stakeholder said, in one form or another, that responsibility belonged somewhere else.”

    is.gd/AmazonDEMetadata

    #namesmatter #respecttheartist #metadata #dataintegrity #amazon #datagovernance #dataownership #qualityassurance #qafail #metadatamess #breakingnews

  16. Day 290

    If a journalist eventually finds it, the story waiting for them is no longer “Amazon misspelled an actor’s name.”

    It is:

    “A German woman spent nearly a year documenting a systemic catalogue-integrity problem while every major stakeholder said, in one form or another, that responsibility belonged somewhere else.”

    is.gd/AmazonDEMetadata

    #namesmatter #respecttheartist #metadata #dataintegrity #amazon #datagovernance #dataownership #qualityassurance #qafail #metadatamess #breakingnews

  17. Day 290

    If a journalist eventually finds it, the story waiting for them is no longer “Amazon misspelled an actor’s name.”

    It is:

    “A German woman spent nearly a year documenting a systemic catalogue-integrity problem while every major stakeholder said, in one form or another, that responsibility belonged somewhere else.”

    is.gd/AmazonDEMetadata

    #namesmatter #respecttheartist #metadata #dataintegrity #amazon #datagovernance #dataownership #qualityassurance #qafail #metadatamess #breakingnews

  18. Privacy is more than compliance. It is how trust is built.

    With Mautic, your data stays in infrastructure you control. Build marketing that respects your customers and your ownership.

    Start your 14-day free trial: mautic.org/start-using-mautic/

    #Mautic #DataOwnership #Marketing Automation

  19. Privacy is more than compliance. It is how trust is built.

    With Mautic, your data stays in infrastructure you control. Build marketing that respects your customers and your ownership.

    Start your 14-day free trial: mautic.org/start-using-mautic/

    #Mautic #DataOwnership #Marketing Automation

  20. Privacy is more than compliance. It is how trust is built.

    With Mautic, your data stays in infrastructure you control. Build marketing that respects your customers and your ownership.

    Start your 14-day free trial: mautic.org/start-using-mautic/

    #Mautic #DataOwnership #Marketing Automation

  21. Privacy is more than compliance. It is how trust is built.

    With Mautic, your data stays in infrastructure you control. Build marketing that respects your customers and your ownership.

    Start your 14-day free trial: mautic.org/start-using-mautic/

    #Mautic #DataOwnership #Marketing Automation

  22. Oh, look! Another *revolutionary* idea: let users decide where their data goes! 🚀 Because who wouldn't want the privilege of navigating the labyrinth of BaaS, triplestores, and serverless authorization? 🙄 Meanwhile, GitHub's throwing AI and automation at everything, apparently hoping we'll all just forget what real development looks like. 🤖🔧
    github.com/wolfoo2931/linkedre #revolutionaryideas #userempowerment #dataownership #AIautomation #GitHubdevelopment #HackerNews #ngated

  23. Oh, look! Another *revolutionary* idea: let users decide where their data goes! 🚀 Because who wouldn't want the privilege of navigating the labyrinth of BaaS, triplestores, and serverless authorization? 🙄 Meanwhile, GitHub's throwing AI and automation at everything, apparently hoping we'll all just forget what real development looks like. 🤖🔧
    github.com/wolfoo2931/linkedre #revolutionaryideas #userempowerment #dataownership #AIautomation #GitHubdevelopment #HackerNews #ngated

  24. Oh, look! Another *revolutionary* idea: let users decide where their data goes! 🚀 Because who wouldn't want the privilege of navigating the labyrinth of BaaS, triplestores, and serverless authorization? 🙄 Meanwhile, GitHub's throwing AI and automation at everything, apparently hoping we'll all just forget what real development looks like. 🤖🔧
    github.com/wolfoo2931/linkedre #revolutionaryideas #userempowerment #dataownership #AIautomation #GitHubdevelopment #HackerNews #ngated

  25. Oh, look! Another *revolutionary* idea: let users decide where their data goes! 🚀 Because who wouldn't want the privilege of navigating the labyrinth of BaaS, triplestores, and serverless authorization? 🙄 Meanwhile, GitHub's throwing AI and automation at everything, apparently hoping we'll all just forget what real development looks like. 🤖🔧
    github.com/wolfoo2931/linkedre #revolutionaryideas #userempowerment #dataownership #AIautomation #GitHubdevelopment #HackerNews #ngated

  26. Oh, look! Another *revolutionary* idea: let users decide where their data goes! 🚀 Because who wouldn't want the privilege of navigating the labyrinth of BaaS, triplestores, and serverless authorization? 🙄 Meanwhile, GitHub's throwing AI and automation at everything, apparently hoping we'll all just forget what real development looks like. 🤖🔧
    github.com/wolfoo2931/linkedre #revolutionaryideas #userempowerment #dataownership #AIautomation #GitHubdevelopment #HackerNews #ngated

  27. 🚨 ALERT: Tech bro discovers that data ownership is as elusive as #Bigfoot 🦶—after diving into ATProto's murky waters, he realizes that PDS operators might as well be his doppelgängers! 🤯 Shockingly, the article fails to mention that the real horror is the author's newfound understanding of his own insignificance. 😂
    kevinak.se/blog/who-actually-o #TechBro #DataOwnership #PDSOperators #SelfDiscovery #HackerNews #ngated

  28. 🚨 ALERT: Tech bro discovers that data ownership is as elusive as #Bigfoot 🦶—after diving into ATProto's murky waters, he realizes that PDS operators might as well be his doppelgängers! 🤯 Shockingly, the article fails to mention that the real horror is the author's newfound understanding of his own insignificance. 😂
    kevinak.se/blog/who-actually-o #TechBro #DataOwnership #PDSOperators #SelfDiscovery #HackerNews #ngated

  29. 🚨 ALERT: Tech bro discovers that data ownership is as elusive as #Bigfoot 🦶—after diving into ATProto's murky waters, he realizes that PDS operators might as well be his doppelgängers! 🤯 Shockingly, the article fails to mention that the real horror is the author's newfound understanding of his own insignificance. 😂
    kevinak.se/blog/who-actually-o #TechBro #DataOwnership #PDSOperators #SelfDiscovery #HackerNews #ngated

  30. 🚨 ALERT: Tech bro discovers that data ownership is as elusive as #Bigfoot 🦶—after diving into ATProto's murky waters, he realizes that PDS operators might as well be his doppelgängers! 🤯 Shockingly, the article fails to mention that the real horror is the author's newfound understanding of his own insignificance. 😂
    kevinak.se/blog/who-actually-o #TechBro #DataOwnership #PDSOperators #SelfDiscovery #HackerNews #ngated

  31. 🚨 ALERT: Tech bro discovers that data ownership is as elusive as #Bigfoot 🦶—after diving into ATProto's murky waters, he realizes that PDS operators might as well be his doppelgängers! 🤯 Shockingly, the article fails to mention that the real horror is the author's newfound understanding of his own insignificance. 😂
    kevinak.se/blog/who-actually-o #TechBro #DataOwnership #PDSOperators #SelfDiscovery #HackerNews #ngated

  32. WHERE OTHERS LOSE CONTROL – WE STAY IN THE LOOP.

    At Infinito.Nexus, we believe that AI should never replace human judgment. We are the captains. AI is our navigator. While others hand over responsibility to black-box systems, we stay in control. We design the architecture, review the code, verify every deployment, and make the decisions that shape the future of the systems we build. AI is one of the most powerful tools ever created. But it remains a tool. We are the engineers, architects, and craftsmen who use it to build sovereign digital infrastructure faster, more reliably, and at a scale that was impossible only a few years ago. […]

    blog.infinito.nexus/blog/2026/

  33. WHERE OTHERS LOSE CONTROL – WE STAY IN THE LOOP.

    At Infinito.Nexus, we believe that AI should never replace human judgment. We are the captains. AI is our navigator. While others hand over responsibility to black-box systems, we stay in control. We design the architecture, review the code, verify every deployment, and make the decisions that shape the future of the systems we build. AI is one of the most powerful tools ever created. But it remains a tool. We are the engineers, architects, and craftsmen who use it to build sovereign digital infrastructure faster, more reliably, and at a scale that was impossible only a few years ago. […]

    blog.infinito.nexus/blog/2026/

  34. 200 000 bilder och en fu*k you-lösning!

    Del 2 i min bloggserie om projektet digital hemflytt är nu publicerad. Denna gång är fokus hanteringen av bilder med en hybridlösning.

    https://noldal.se/02-200-000-bilder-och-en-fu-k-you-losning/

    #selfhosting #degoogleyourself #dataownership #immich #Lightroom #foto

  35. 200 000 bilder och en fu*k you-lösning!

    Del 2 i min bloggserie om projektet digital hemflytt är nu publicerad. Denna gång är fokus hanteringen av bilder med en hybridlösning.

    https://noldal.se/02-200-000-bilder-och-en-fu-k-you-losning/

    #selfhosting #degoogleyourself #dataownership #immich #Lightroom #foto

  36. Är mitt digitala liv verkligen mitt? Eller hyr jag det bara?

    Startskottet för min bloggserie om projekt digital hemflytt -
    varför jag tröttnade på att bo i någon annans digitala hyreshus.

    https://noldal.se/01-projekt-digital-hemflytt/

    #SelfHosting #DeGoogle #Privacy #DataOwnership

  37. Är mitt digitala liv verkligen mitt? Eller hyr jag det bara?

    Startskottet för min bloggserie om projekt digital hemflytt -
    varför jag tröttnade på att bo i någon annans digitala hyreshus.

    https://noldal.se/01-projekt-digital-hemflytt/

    #SelfHosting #DeGoogle #Privacy #DataOwnership

  38. Är mitt digitala liv verkligen mitt? Eller hyr jag det bara?

    Startskottet för min bloggserie om projekt digital hemflytt -
    varför jag tröttnade på att bo i någon annans digitala hyreshus.

    https://noldal.se/01-projekt-digital-hemflytt/

    #SelfHosting #DeGoogle #Privacy #DataOwnership

  39. Är mitt digitala liv verkligen mitt? Eller hyr jag det bara?

    Startskottet för min bloggserie om projekt digital hemflytt -
    varför jag tröttnade på att bo i någon annans digitala hyreshus.

    https://noldal.se/01-projekt-digital-hemflytt/

    #SelfHosting #DeGoogle #Privacy #DataOwnership

  40. Är mitt digitala liv verkligen mitt? Eller hyr jag det bara?

    Startskottet för min bloggserie om projekt digital hemflytt -
    varför jag tröttnade på att bo i någon annans digitala hyreshus.

    https://noldal.se/01-projekt-digital-hemflytt/

    #SelfHosting #DeGoogle #Privacy #DataOwnership

  41. You own your phone, but do you own your history? 📱🤔

    When your data is buried inside encrypted local backup files, it might as well not exist. #Keepita opens that black box, converting raw phone data into an instantly readable and searchable dashboard.

    Reclaim your digital archive: keepita.com/

    #Keepita #DataOwnership #TechTools #BuildInPublic #IndieDev

  42. FYI: Infillion tells DSP buyers what questions they are afraid to ask: Infillion MediaMath published a 15-question DSP buyer guide on AI architecture, pricing transparency, data ownership, and identity resolution for programmatic. ppc.land/infillion-tells-dsp-b #DSP #ProgrammaticAds #AIArchitecture #DataOwnership #AdvertisingTrends

  43. FYI: Infillion tells DSP buyers what questions they are afraid to ask: Infillion MediaMath published a 15-question DSP buyer guide on AI architecture, pricing transparency, data ownership, and identity resolution for programmatic. ppc.land/infillion-tells-dsp-b #DSP #ProgrammaticAds #AIArchitecture #DataOwnership #AdvertisingTrends