#couchdb — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #couchdb, aggregated by home.social.
-
Anyone using Obsidian and the self-hosted LiveSync (https://github.com/vrtmrz/obsidian-livesync)? Seems to be the only self-hosted sync with relevant attention. But the docs are a little weird and confusing. CouchDB can be used, which I find interesting for this use case. But LiveSync's docs are not confident inspiring. e.g. it's totally unclear how conflicts are handled or resolved.
-
Anyone using Obsidian and the self-hosted LiveSync (https://github.com/vrtmrz/obsidian-livesync)? Seems to be the only self-hosted sync with relevant attention. But the docs are a little weird and confusing. CouchDB can be used, which I find interesting for this use case. But LiveSync's docs are not confident inspiring. e.g. it's totally unclear how conflicts are handled or resolved.
-
Anyone using Obsidian and the self-hosted LiveSync (https://github.com/vrtmrz/obsidian-livesync)? Seems to be the only self-hosted sync with relevant attention. But the docs are a little weird and confusing. CouchDB can be used, which I find interesting for this use case. But LiveSync's docs are not confident inspiring. e.g. it's totally unclear how conflicts are handled or resolved.
-
Anyone using Obsidian and the self-hosted LiveSync (https://github.com/vrtmrz/obsidian-livesync)? Seems to be the only self-hosted sync with relevant attention. But the docs are a little weird and confusing. CouchDB can be used, which I find interesting for this use case. But LiveSync's docs are not confident inspiring. e.g. it's totally unclear how conflicts are handled or resolved.
-
Anyone using Obsidian and the self-hosted LiveSync (https://github.com/vrtmrz/obsidian-livesync)? Seems to be the only self-hosted sync with relevant attention. But the docs are a little weird and confusing. CouchDB can be used, which I find interesting for this use case. But LiveSync's docs are not confident inspiring. e.g. it's totally unclear how conflicts are handled or resolved.
-
NoSQL Injection Attacks: MongoDB, CouchDB, and More – NoSQL injection
In this article, I cover how NoSQL injection works, common attack vectors, and practical mitigation techniques.
https://denizhalil.com/2025/12/23/nosql-injection-attacks-mongodb-couchdb/#CyberSecurity #NoSQL #MongoDB #CouchDB #WebSecurity #AppSec #Injection #InfoSec #Pentesting #RedTeam #BlueTeam #securecoding
-
NoSQL Injection Attacks: MongoDB, CouchDB, and More – NoSQL injection
In this article, I cover how NoSQL injection works, common attack vectors, and practical mitigation techniques.
https://denizhalil.com/2025/12/23/nosql-injection-attacks-mongodb-couchdb/#CyberSecurity #NoSQL #MongoDB #CouchDB #WebSecurity #AppSec #Injection #InfoSec #Pentesting #RedTeam #BlueTeam #securecoding
-
NoSQL Injection Attacks: MongoDB, CouchDB, and More – NoSQL injection
In this article, I cover how NoSQL injection works, common attack vectors, and practical mitigation techniques.
https://denizhalil.com/2025/12/23/nosql-injection-attacks-mongodb-couchdb/#CyberSecurity #NoSQL #MongoDB #CouchDB #WebSecurity #AppSec #Injection #InfoSec #Pentesting #RedTeam #BlueTeam #securecoding
-
Почему я сделал свой сервис синхронизации для Obsidian
В августе 2025 я открыл для себя мощный инструмент для менеджмента своих мыслей — Obsidian. Мою оперативную память в голове он очень сильно разгрузил. Но речь в статье пойдет не об этом. О синхронизации.
-
Почему я сделал свой сервис синхронизации для Obsidian
В августе 2025 я открыл для себя мощный инструмент для менеджмента своих мыслей — Obsidian. Мою оперативную память в голове он очень сильно разгрузил. Но речь в статье пойдет не об этом. О синхронизации.
-
Почему я сделал свой сервис синхронизации для Obsidian
В августе 2025 я открыл для себя мощный инструмент для менеджмента своих мыслей — Obsidian. Мою оперативную память в голове он очень сильно разгрузил. Но речь в статье пойдет не об этом. О синхронизации.
-
Почему я сделал свой сервис синхронизации для Obsidian
В августе 2025 я открыл для себя мощный инструмент для менеджмента своих мыслей — Obsidian. Мою оперативную память в голове он очень сильно разгрузил. Но речь в статье пойдет не об этом. О синхронизации.
-
Actually, there is an #activitypub software that uses #couchdb as a backend - flohmarkt: https://codeberg.org/flohmarkt/flohmarkt
-
TIL about couchDB
I am going to play with this DB on one of my distributions. couchDB scales from massive all the way down to mobile
quote:
Apache CouchDB ™ lets you access your data where you need it. The Couch Replication Protocol is implemented in a variety of projects and products that span every imaginable computing environment from globally distributed server-clusters, over mobile phones to web browsers.
https://docs.couchdb.org/en/stable/intro/why.html
#couchDB #database #scaling #Apache #Linux #dBASE #programming #technology #OpenSource #POSIX
-
TIL about couchDB
I am going to play with this DB on one of my distributions. couchDB scales from massive all the way down to mobile
quote:
Apache CouchDB ™ lets you access your data where you need it. The Couch Replication Protocol is implemented in a variety of projects and products that span every imaginable computing environment from globally distributed server-clusters, over mobile phones to web browsers.
https://docs.couchdb.org/en/stable/intro/why.html
#couchDB #database #scaling #Apache #Linux #dBASE #programming #technology #OpenSource #POSIX
-
TIL about couchDB
I am going to play with this DB on one of my distributions. couchDB scales from massive all the way down to mobile
quote:
Apache CouchDB ™ lets you access your data where you need it. The Couch Replication Protocol is implemented in a variety of projects and products that span every imaginable computing environment from globally distributed server-clusters, over mobile phones to web browsers.
https://docs.couchdb.org/en/stable/intro/why.html
#couchDB #database #scaling #Apache #Linux #dBASE #programming #technology #OpenSource #POSIX
-
TIL about couchDB
I am going to play with this DB on one of my distributions. couchDB scales from massive all the way down to mobile
quote:
Apache CouchDB ™ lets you access your data where you need it. The Couch Replication Protocol is implemented in a variety of projects and products that span every imaginable computing environment from globally distributed server-clusters, over mobile phones to web browsers.
https://docs.couchdb.org/en/stable/intro/why.html
#couchDB #database #scaling #Apache #Linux #dBASE #programming #technology #OpenSource #POSIX
-
TIL about couchDB
I am going to play with this DB on one of my distributions. couchDB scales from massive all the way down to mobile
quote:
Apache CouchDB ™ lets you access your data where you need it. The Couch Replication Protocol is implemented in a variety of projects and products that span every imaginable computing environment from globally distributed server-clusters, over mobile phones to web browsers.
https://docs.couchdb.org/en/stable/intro/why.html
#couchDB #database #scaling #Apache #Linux #dBASE #programming #technology #OpenSource #POSIX
-
TIL CouchDB uses irc #Couchdb for chat with developers. So, it can be done without discord 👏
-
TIL CouchDB uses irc #Couchdb for chat with developers. So, it can be done without discord 👏
-
TIL CouchDB uses irc #Couchdb for chat with developers. So, it can be done without discord 👏
-
TIL CouchDB uses irc #Couchdb for chat with developers. So, it can be done without discord 👏
-
TIL CouchDB uses irc #Couchdb for chat with developers. So, it can be done without discord 👏
-
#obsidian #selfhosted sync with #couchdb is kinda magical! (once you have it set up and understand what it does...)
-
#obsidian #selfhosted sync with #couchdb is kinda magical! (once you have it set up and understand what it does...)
-
#obsidian #selfhosted sync with #couchdb is kinda magical! (once you have it set up and understand what it does...)
-
#obsidian #selfhosted sync with #couchdb is kinda magical! (once you have it set up and understand what it does...)
-
#obsidian #selfhosted sync with #couchdb is kinda magical! (once you have it set up and understand what it does...)
-
Help shape the future of @couchdb 📣
It’s time again for the Annual Apache #CouchDB User Survey, where we collect insights that help project contributors prioritise what to build, write about and enhance.
Take part in the 2025 - 2026 survey: https://forms.gle/KGkPp8qxmwyrTrJR6
Boosts and shares appreciated — let’s reach as many users as we can! 🌐
Take a look at last year’s results to learn how the findings will be shared: https://blog.couchdb.org/2025/06/18/2024-apache-couchdb-user-survey-results/
-
Help shape the future of @couchdb 📣
It’s time again for the Annual Apache #CouchDB User Survey, where we collect insights that help project contributors prioritise what to build, write about and enhance.
Take part in the 2025 - 2026 survey: https://forms.gle/KGkPp8qxmwyrTrJR6
Boosts and shares appreciated — let’s reach as many users as we can! 🌐
Take a look at last year’s results to learn how the findings will be shared: https://blog.couchdb.org/2025/06/18/2024-apache-couchdb-user-survey-results/
-
Help shape the future of @couchdb 📣
It’s time again for the Annual Apache #CouchDB User Survey, where we collect insights that help project contributors prioritise what to build, write about and enhance.
Take part in the 2025 - 2026 survey: https://forms.gle/KGkPp8qxmwyrTrJR6
Boosts and shares appreciated — let’s reach as many users as we can! 🌐
Take a look at last year’s results to learn how the findings will be shared: https://blog.couchdb.org/2025/06/18/2024-apache-couchdb-user-survey-results/
-
Help shape the future of @couchdb 📣
It’s time again for the Annual Apache #CouchDB User Survey, where we collect insights that help project contributors prioritise what to build, write about and enhance.
Take part in the 2025 - 2026 survey: https://forms.gle/KGkPp8qxmwyrTrJR6
Boosts and shares appreciated — let’s reach as many users as we can! 🌐
Take a look at last year’s results to learn how the findings will be shared: https://blog.couchdb.org/2025/06/18/2024-apache-couchdb-user-survey-results/
-
Help shape the future of @couchdb 📣
It’s time again for the Annual Apache #CouchDB User Survey, where we collect insights that help project contributors prioritise what to build, write about and enhance.
Take part in the 2025 - 2026 survey: https://forms.gle/KGkPp8qxmwyrTrJR6
Boosts and shares appreciated — let’s reach as many users as we can! 🌐
Take a look at last year’s results to learn how the findings will be shared: https://blog.couchdb.org/2025/06/18/2024-apache-couchdb-user-survey-results/
-
#Sharding is (another) one of the things that makes @couchdb such a scalable distributed database 📐
It’s an architectural consideration that very few DBs make as automatic and transparent as CouchDB.
We cover, in depth:
- what shards are
- how #CouchDB uses them
- performance gains and trade-offsin our new post:
https://neighbourhood.ie/blog/2025/10/01/first-steps-sharding-in-couchdb?pk_campaign=mastodon&pk_kwd=shard -
#Sharding is (another) one of the things that makes @couchdb such a scalable distributed database 📐
It’s an architectural consideration that very few DBs make as automatic and transparent as CouchDB.
We cover, in depth:
- what shards are
- how #CouchDB uses them
- performance gains and trade-offsin our new post:
https://neighbourhood.ie/blog/2025/10/01/first-steps-sharding-in-couchdb?pk_campaign=mastodon&pk_kwd=shard -
#Sharding is (another) one of the things that makes @couchdb such a scalable distributed database 📐
It’s an architectural consideration that very few DBs make as automatic and transparent as CouchDB.
We cover, in depth:
- what shards are
- how #CouchDB uses them
- performance gains and trade-offsin our new post:
https://neighbourhood.ie/blog/2025/10/01/first-steps-sharding-in-couchdb?pk_campaign=mastodon&pk_kwd=shard -
#Sharding is (another) one of the things that makes @couchdb such a scalable distributed database 📐
It’s an architectural consideration that very few DBs make as automatic and transparent as CouchDB.
We cover, in depth:
- what shards are
- how #CouchDB uses them
- performance gains and trade-offsin our new post:
https://neighbourhood.ie/blog/2025/10/01/first-steps-sharding-in-couchdb?pk_campaign=mastodon&pk_kwd=shard -
#Sharding is (another) one of the things that makes @couchdb such a scalable distributed database 📐
It’s an architectural consideration that very few DBs make as automatic and transparent as CouchDB.
We cover, in depth:
- what shards are
- how #CouchDB uses them
- performance gains and trade-offsin our new post:
https://neighbourhood.ie/blog/2025/10/01/first-steps-sharding-in-couchdb?pk_campaign=mastodon&pk_kwd=shard -
Un clip bien sympa pour la promotion de "Couch DB", Ya 15 ans déjà ...
https://vimeo.com/11852209
#sgbd #couchdb -
Un clip bien sympa pour la promotion de "Couch DB", Ya 15 ans déjà ...
https://vimeo.com/11852209
#sgbd #couchdb -
Revisiting an Old Idea: Building a Rules Engine with CouchDB
A few years back, while working at 18F, I created a prototype that explored something a bit unconventional: using CouchDB’s document validation functions as the foundation for a rules engine. The idea was to leverage CouchDB’s built-in validation capabilities to create business rules that could be applied to documents as they’re inserted or updated.
I’ve always been somewhat obsessed with CouchDB—there’s something elegant about its document-oriented approach and the way it handles replication, versioning, and distributed architectures. (Here’s a video I made over 10 years ago showing how to load polling location data into a CouchDB instance.) So even though my prototype remained just that, the concept has continued to bubble in the back of my brain.
Recently, I decided to dust off this old project and give it the attention it deserves. I’ve worked to develop a comprehensive roadmap to transform the basic prototype into a more functional and usable product that truly leverages CouchDB’s unique strengths.
What Makes This Interesting
Instead of building yet another traditional rules engine, this approach uses CouchDB’s native validation functions as the rule execution environment. This means:
- Native versioning through CouchDB’s document revision system
- Built-in replication for distributing rules across environments
- RESTful rule management using CouchDB’s HTTP API
- Distributed validation that scales with CouchDB clusters
The roadmap I’ve created takes my earlier work from a proof-of-concept to a (hopefully) production-ready system with a web-based rule management interface, comprehensive testing infrastructure, and advanced rule capabilities—all while maintaining the elegance of the core CouchDB foundation.
Looking Ahead
Over the next few weeks (again, hopefully), I’ll be working through the development phases, starting with a modern testing framework and a clean web interface for rule management. The goal is to create something that demonstrates how CouchDB’s unique features can be leveraged in ways that traditional databases simply can’t match.
If you’re interested in following along or have thoughts about creative uses for CouchDB, I’d love to hear from you. Sometimes the most interesting solutions come from pushing familiar tools in unexpected directions.
#art #books #CouchDB #governmet #Javascript #OpenSource #politics #rules #serviceDelivery #software #technology
-
Revisiting an Old Idea: Building a Rules Engine with CouchDB
A few years back, while working at 18F, I created a prototype that explored something a bit unconventional: using CouchDB’s document validation functions as the foundation for a rules engine. The idea was to leverage CouchDB’s built-in validation capabilities to create business rules that could be applied to documents as they’re inserted or updated.
I’ve always been somewhat obsessed with CouchDB—there’s something elegant about its document-oriented approach and the way it handles replication, versioning, and distributed architectures. (Here’s a video I made over 10 years ago showing how to load polling location data into a CouchDB instance.) So even though my prototype remained just that, the concept has continued to bubble in the back of my brain.
Recently, I decided to dust off this old project and give it the attention it deserves. I’ve worked to develop a comprehensive roadmap to transform the basic prototype into a more functional and usable product that truly leverages CouchDB’s unique strengths.
What Makes This Interesting
Instead of building yet another traditional rules engine, this approach uses CouchDB’s native validation functions as the rule execution environment. This means:
- Native versioning through CouchDB’s document revision system
- Built-in replication for distributing rules across environments
- RESTful rule management using CouchDB’s HTTP API
- Distributed validation that scales with CouchDB clusters
The roadmap I’ve created takes my earlier work from a proof-of-concept to a (hopefully) production-ready system with a web-based rule management interface, comprehensive testing infrastructure, and advanced rule capabilities—all while maintaining the elegance of the core CouchDB foundation.
Looking Ahead
Over the next few weeks (again, hopefully), I’ll be working through the development phases, starting with a modern testing framework and a clean web interface for rule management. The goal is to create something that demonstrates how CouchDB’s unique features can be leveraged in ways that traditional databases simply can’t match.
If you’re interested in following along or have thoughts about creative uses for CouchDB, I’d love to hear from you. Sometimes the most interesting solutions come from pushing familiar tools in unexpected directions.
#art #books #CouchDB #governmet #Javascript #OpenSource #politics #rules #serviceDelivery #software #technology
-
Revisiting an Old Idea: Building a Rules Engine with CouchDB
A few years back, while working at 18F, I created a prototype that explored something a bit unconventional: using CouchDB’s document validation functions as the foundation for a rules engine. The idea was to leverage CouchDB’s built-in validation capabilities to create business rules that could be applied to documents as they’re inserted or updated.
I’ve always been somewhat obsessed with CouchDB—there’s something elegant about its document-oriented approach and the way it handles replication, versioning, and distributed architectures. (Here’s a video I made over 10 years ago showing how to load polling location data into a CouchDB instance.) So even though my prototype remained just that, the concept has continued to bubble in the back of my brain.
Recently, I decided to dust off this old project and give it the attention it deserves. I’ve worked to develop a comprehensive roadmap to transform the basic prototype into a more functional and usable product that truly leverages CouchDB’s unique strengths.
What Makes This Interesting
Instead of building yet another traditional rules engine, this approach uses CouchDB’s native validation functions as the rule execution environment. This means:
- Native versioning through CouchDB’s document revision system
- Built-in replication for distributing rules across environments
- RESTful rule management using CouchDB’s HTTP API
- Distributed validation that scales with CouchDB clusters
The roadmap I’ve created takes my earlier work from a proof-of-concept to a (hopefully) production-ready system with a web-based rule management interface, comprehensive testing infrastructure, and advanced rule capabilities—all while maintaining the elegance of the core CouchDB foundation.
Looking Ahead
Over the next few weeks (again, hopefully), I’ll be working through the development phases, starting with a modern testing framework and a clean web interface for rule management. The goal is to create something that demonstrates how CouchDB’s unique features can be leveraged in ways that traditional databases simply can’t match.
If you’re interested in following along or have thoughts about creative uses for CouchDB, I’d love to hear from you. Sometimes the most interesting solutions come from pushing familiar tools in unexpected directions.
#art #books #CouchDB #governmet #Javascript #OpenSource #politics #rules #serviceDelivery #software #technology
-
Revisiting an Old Idea: Building a Rules Engine with CouchDB
A few years back, while working at 18F, I created a prototype that explored something a bit unconventional: using CouchDB’s document validation functions as the foundation for a rules engine. The idea was to leverage CouchDB’s built-in validation capabilities to create business rules that could be applied to documents as they’re inserted or updated.
I’ve always been somewhat obsessed with CouchDB—there’s something elegant about its document-oriented approach and the way it handles replication, versioning, and distributed architectures. (Here’s a video I made over 10 years ago showing how to load polling location data into a CouchDB instance.) So even though my prototype remained just that, the concept has continued to bubble in the back of my brain.
Recently, I decided to dust off this old project and give it the attention it deserves. I’ve worked to develop a comprehensive roadmap to transform the basic prototype into a more functional and usable product that truly leverages CouchDB’s unique strengths.
What Makes This Interesting
Instead of building yet another traditional rules engine, this approach uses CouchDB’s native validation functions as the rule execution environment. This means:
- Native versioning through CouchDB’s document revision system
- Built-in replication for distributing rules across environments
- RESTful rule management using CouchDB’s HTTP API
- Distributed validation that scales with CouchDB clusters
The roadmap I’ve created takes my earlier work from a proof-of-concept to a (hopefully) production-ready system with a web-based rule management interface, comprehensive testing infrastructure, and advanced rule capabilities—all while maintaining the elegance of the core CouchDB foundation.
Looking Ahead
Over the next few weeks (again, hopefully), I’ll be working through the development phases, starting with a modern testing framework and a clean web interface for rule management. The goal is to create something that demonstrates how CouchDB’s unique features can be leveraged in ways that traditional databases simply can’t match.
If you’re interested in following along or have thoughts about creative uses for CouchDB, I’d love to hear from you. Sometimes the most interesting solutions come from pushing familiar tools in unexpected directions.
#art #books #CouchDB #governmet #Javascript #OpenSource #politics #rules #serviceDelivery #software #technology
