home.social

Search

1000 results for “localfirst”

  1. Ever look at your life and think “wtf is this”? 🤪

    Perfice looked at my data and said: “You’re not cursed - you’re just running on 3 hours of sleep and pure delusion.”

    Perfice is a local-first, open-source self-tracking app that shows how your sleep, mood, habits, and daily chaos actually connect.
    No cloud uploads.
    No creepy analytics.
    Just you and your uncomfortable truths.

    github.com/p0lloc/perfice

    #opensource #selftracking #localfirst #sleep #techlife #devlife

  2. Ever look at your life and think “wtf is this”? 🤪

    Perfice looked at my data and said: “You’re not cursed - you’re just running on 3 hours of sleep and pure delusion.”

    Perfice is a local-first, open-source self-tracking app that shows how your sleep, mood, habits, and daily chaos actually connect.
    No cloud uploads.
    No creepy analytics.
    Just you and your uncomfortable truths.

    github.com/p0lloc/perfice

    #opensource #selftracking #localfirst #sleep #techlife #devlife

  3. The frontier of digital expression is returning to code and text.

    Instead of massive models or flashy UIs,
    trust grows in small, readable code and honest words.

    ZINEs in .txt or .md, local AI, and the minimal beauty of UNIX.
    True freedom comes from technology you can understand.

    #TextCulture #UNIX #LocalFirst #SmallIsBeautiful #DIYTech #FediTech

  4. 🧐 Ah, yes, the #BeeKEM protocol, where we learn that #privacy and #consent are apparently revolutionary ideas—because obviously, no one ever thought of them before these "local-first" geniuses. 🤦‍♂️ Let's all pretend the world didn't already know about #autonomy before #Keyhive came along to save us from ourselves! 🚀
    meri.garden/a-deep-dive-explai #localfirst #HackerNews #ngated

  5. With PodOS you can now access your data while offline. Opt-in by visiting the Settings page (Button in the footer)

    browser.pod-os.org

  6. Apparently, we've reached the glorious era where an #open-source #AI agent can regurgitate cookie-cutter apps from the bowels of a "Neon" platform, all while developers sip coffee and pretend to be productive ☕🤖. In true tech fashion, it proudly claims to be "localfirst"—because what's more revolutionary than solving problems no one had? 🌟✨
    app.build/ #localfirst #techhumor #appdevelopment #coffeeandcode #HackerNews #ngated

  7. 🎩 Ah, the age-old "Local-First Software is the shiny new knight" tale, where #databases are the misunderstood protagonists in a techie soap opera no one auditioned for. 🤖 Spoiler alert: it's a #JavaScript jamboree with enough buzzwords to power a small startup, yet still manages to trip over its own limitations while chasing its offline dreams. 🚀
    rxdb.info/articles/local-first #LocalFirstSoftware #TechBuzz #OfflineFirst #HackerNews #ngated

  8. I have a new post on my experimental journal and on how it's going, implemented, and may change. I may also have noted a way to get digital bird stickers.

    fractalkitty.com/streamof-me/

    #streamOfMe #journal #mathOfMe #cinquain #birding #microBlog #localFirst #rss #indieWeb

  9. Last talk before LoFi hacking is @daffl talking about his DWeb chat app that we are using as the backchannel for the event this weekend 💬

    #LoFiWKND #DWebYVR #LocalFirstSoftware

  10. Our first speaker @pvh gives us a rundown of local-first software, Automerge, and some live coding! 🔥

    #LoFiWKND #DWebYVR #LocalFirstSoftware

  11. @kkarhan

    thanks for the reply! far from being discouraged, i appriciate your engagement. i will try to be reasonably brief in my reponse to your points and give a general update on progress and objective.

    > scout out existing solutions

    i have seem similar #webapp implementation, i think so far for "that kind" of chat app, the chat app is able to demonstrate similar basic functionality. for a wider adoption, the user interface needs to be more appealing, but i think its important to have a working proof-of-concept first. the project is specifically aiming to be a #javascript #localFirst #webapp.

    a couple notable similar implementation to mine are:
    - github.com/cryptocat/cryptocat
    - github.com/jeremyckahn/chitcha
    (im sure there are many more, but i think my approach is yet different and unique to the ones i've come across.)

    > DO NOT DIY ENCRYPTION!

    this is indeed a reccomended practice i have seen several times. here is a previsous reddit post on the matter: reddit.com/r/cryptography/comm ... tldr; the underlying implementation provided by the browser is the best way to go. i have implemented the #encryption using the #webcrypto #api. i aim to not use a library for this.

    i generally try to word things in a way that users can provide feedback on features. the app is still in a very early stage, but has a reasonable amount of features. im generally open to requests and questions.

    > minimum viable product

    what you see as the chat app is also the #minimum #viable #product. i think its sufficiently demonstrates the basic functionality of a chat app. i think the next step is to make the app more stable and user friendly.

    those other apps youve mentions ive come across before. what sets my approach apart is that mine it's purely a webapp. with what id like to describe as #p2p #authentication over #webrtc, im able to remove reliance on a backend for #authenticate #data #connections. in some cases, bypass the internet (wifi/hotspot). while there are several ways to #selfhost, in this approach of a #javascript implementation, im able to store large amounts of data in the browser so things like images and #encryptionKeys can be #selfhosted" in the browser. while this form has nuanced limitations, it also has interesting implications to security and privacy.

    there are many nice features from the different apps you mentioned and i think i have some unique features too. the bottle neck in this project is that i dont put in enough time to the app.

    > feel free to slowly ibtegrate them.

    this is basically already my approach to get the app to where it is now.

    thanks for the luck, take care and i hope you stay tuned for updates.

  12. @kkarhan

    thanks for the reply! far from being discouraged, i appriciate your engagement. i will try to be reasonably brief in my reponse to your points and give a general update on progress and objective.

    > scout out existing solutions

    i have seem similar #webapp implementation, i think so far for "that kind" of chat app, the chat app is able to demonstrate similar basic functionality. for a wider adoption, the user interface needs to be more appealing, but i think its important to have a working proof-of-concept first. the project is specifically aiming to be a #javascript #localFirst #webapp.

    a couple notable similar implementation to mine are:
    - github.com/cryptocat/cryptocat
    - github.com/jeremyckahn/chitcha
    (im sure there are many more, but i think my approach is yet different and unique to the ones i've come across.)

    > DO NOT DIY ENCRYPTION!

    this is indeed a reccomended practice i have seen several times. here is a previsous reddit post on the matter: reddit.com/r/cryptography/comm ... tldr; the underlying implementation provided by the browser is the best way to go. i have implemented the #encryption using the #webcrypto #api. i aim to not use a library for this.

    i generally try to word things in a way that users can provide feedback on features. the app is still in a very early stage, but has a reasonable amount of features. im generally open to requests and questions.

    > minimum viable product

    what you see as the chat app is also the #minimum #viable #product. i think its sufficiently demonstrates the basic functionality of a chat app. i think the next step is to make the app more stable and user friendly.

    those other apps youve mentions ive come across before. what sets my approach apart is that mine it's purely a webapp. with what id like to describe as #p2p #authentication over #webrtc, im able to remove reliance on a backend for #authenticate #data #connections. in some cases, bypass the internet (wifi/hotspot). while there are several ways to #selfhost, in this approach of a #javascript implementation, im able to store large amounts of data in the browser so things like images and #encryptionKeys can be #selfhosted" in the browser. while this form has nuanced limitations, it also has interesting implications to security and privacy.

    there are many nice features from the different apps you mentioned and i think i have some unique features too. the bottle neck in this project is that i dont put in enough time to the app.

    > feel free to slowly ibtegrate them.

    this is basically already my approach to get the app to where it is now.

    thanks for the luck, take care and i hope you stay tuned for updates.

  13. @kkarhan

    thanks for the reply! far from being discouraged, i appriciate your engagement. i will try to be reasonably brief in my reponse to your points and give a general update on progress and objective.

    > scout out existing solutions

    i have seem similar #webapp implementation, i think so far for "that kind" of chat app, the chat app is able to demonstrate similar basic functionality. for a wider adoption, the user interface needs to be more appealing, but i think its important to have a working proof-of-concept first. the project is specifically aiming to be a #javascript #localFirst #webapp.

    a couple notable similar implementation to mine are:
    - github.com/cryptocat/cryptocat
    - github.com/jeremyckahn/chitcha
    (im sure there are many more, but i think my approach is yet different and unique to the ones i've come across.)

    > DO NOT DIY ENCRYPTION!

    this is indeed a reccomended practice i have seen several times. here is a previsous reddit post on the matter: reddit.com/r/cryptography/comm ... tldr; the underlying implementation provided by the browser is the best way to go. i have implemented the #encryption using the #webcrypto #api. i aim to not use a library for this.

    i generally try to word things in a way that users can provide feedback on features. the app is still in a very early stage, but has a reasonable amount of features. im generally open to requests and questions.

    > minimum viable product

    what you see as the chat app is also the #minimum #viable #product. i think its sufficiently demonstrates the basic functionality of a chat app. i think the next step is to make the app more stable and user friendly.

    those other apps youve mentions ive come across before. what sets my approach apart is that mine it's purely a webapp. with what id like to describe as #p2p #authentication over #webrtc, im able to remove reliance on a backend for #authenticate #data #connections. in some cases, bypass the internet (wifi/hotspot). while there are several ways to #selfhost, in this approach of a #javascript implementation, im able to store large amounts of data in the browser so things like images and #encryptionKeys can be #selfhosted" in the browser. while this form has nuanced limitations, it also has interesting implications to security and privacy.

    there are many nice features from the different apps you mentioned and i think i have some unique features too. the bottle neck in this project is that i dont put in enough time to the app.

    > feel free to slowly ibtegrate them.

    this is basically already my approach to get the app to where it is now.

    thanks for the luck, take care and i hope you stay tuned for updates.

  14. @kkarhan

    thanks for the reply! far from being discouraged, i appriciate your engagement. i will try to be reasonably brief in my reponse to your points and give a general update on progress and objective.

    > scout out existing solutions

    i have seem similar #webapp implementation, i think so far for "that kind" of chat app, the chat app is able to demonstrate similar basic functionality. for a wider adoption, the user interface needs to be more appealing, but i think its important to have a working proof-of-concept first. the project is specifically aiming to be a #javascript #localFirst #webapp.

    a couple notable similar implementation to mine are:
    - github.com/cryptocat/cryptocat
    - github.com/jeremyckahn/chitcha
    (im sure there are many more, but i think my approach is yet different and unique to the ones i've come across.)

    > DO NOT DIY ENCRYPTION!

    this is indeed a reccomended practice i have seen several times. here is a previsous reddit post on the matter: reddit.com/r/cryptography/comm ... tldr; the underlying implementation provided by the browser is the best way to go. i have implemented the #encryption using the #webcrypto #api. i aim to not use a library for this.

    i generally try to word things in a way that users can provide feedback on features. the app is still in a very early stage, but has a reasonable amount of features. im generally open to requests and questions.

    > minimum viable product

    what you see as the chat app is also the #minimum #viable #product. i think its sufficiently demonstrates the basic functionality of a chat app. i think the next step is to make the app more stable and user friendly.

    those other apps youve mentions ive come across before. what sets my approach apart is that mine it's purely a webapp. with what id like to describe as #p2p #authentication over #webrtc, im able to remove reliance on a backend for #authenticate #data #connections. in some cases, bypass the internet (wifi/hotspot). while there are several ways to #selfhost, in this approach of a #javascript implementation, im able to store large amounts of data in the browser so things like images and #encryptionKeys can be #selfhosted" in the browser. while this form has nuanced limitations, it also has interesting implications to security and privacy.

    there are many nice features from the different apps you mentioned and i think i have some unique features too. the bottle neck in this project is that i dont put in enough time to the app.

    > feel free to slowly ibtegrate them.

    this is basically already my approach to get the app to where it is now.

    thanks for the luck, take care and i hope you stay tuned for updates.