Search
1000 results for “localfirst”
-
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.
https://www.fractalkitty.com/streamof-me/
#streamOfMe #journal #mathOfMe #cinquain #birding #microBlog #localFirst #rss #indieWeb
-
#Apple should’ve ignored the (pseudo) AI hype
Continue #NeuralAccelerator hardware & #MLX software development, enable running useful LLM locally
Partner with Steam, make running #Games on #macOS & porting to #iOS trivially easy
Embrace a “local first, intermittent connections, eventually consistent” view of the future
Be an alternative to the “cloud first, always on, always connected” future everyone else in trying to sell
Focus on #HomeAutomation
-
As anyone heard of #PiecesOS? Seems like a fancy AI tool, but local first (which I like).
I don't care all the corporate features, but I am interested in the integration with #SublimeText to run local models:
https://pieces.app/learn/ai-connector/sublime-text
The other plugins I tested are meh. -
As anyone heard of #PiecesOS? Seems like a fancy AI tool, but local first (which I like).
I don't care all the corporate features, but I am interested in the integration with #SublimeText to run local models:
https://pieces.app/learn/ai-connector/sublime-text
The other plugins I tested are meh. -
As anyone heard of #PiecesOS? Seems like a fancy AI tool, but local first (which I like).
I don't care all the corporate features, but I am interested in the integration with #SublimeText to run local models:
https://pieces.app/learn/ai-connector/sublime-text
The other plugins I tested are meh. -
As anyone heard of #PiecesOS? Seems like a fancy AI tool, but local first (which I like).
I don't care all the corporate features, but I am interested in the integration with #SublimeText to run local models:
https://pieces.app/learn/ai-connector/sublime-text
The other plugins I tested are meh. -
As anyone heard of #PiecesOS? Seems like a fancy AI tool, but local first (which I like).
I don't care all the corporate features, but I am interested in the integration with #SublimeText to run local models:
https://pieces.app/learn/ai-connector/sublime-text
The other plugins I tested are meh. -
"Local-first software - You own your data, in spite of the cloud" 👍
https://www.inkandswitch.com/local-first
#privacy #dataskydd #dataprotection #gdpr #localfirst #software #CloudSolutions #cloud #collaboration #crdt
-
DoubleMemory is here to revolutionize your #procrastination game with a read-it-later app that's "local-first" because, you know, the cloud is so last decade 🙄. Now you can finally ignore articles with unparalleled #efficiency right from your own device! 🚀📚✨
https://doublememory.com #DoubleMemory #readitlater #localfirst #cloudalternative #HackerNews #ngated -
CW: Non-weather related thought:
The time has come to help people realize that they need to be more #diligent and #thoughtful when finding their information sources.
Personally, I will pick #local first, #profession second, then #interests and #hobbies third.
#Mastadon gives me all this, and has helped me reexamine how I use the Internet in my everyday life.
The question I ask is simple: will this #website or #app or #socialmedia source help me be my best person?
-
https://www.infosecworrier.dk/blog/2021/12/how-to-build-cyberchef.html How to build CyberChef. Tested with latest version 10.6.0 (2024-02-03) #CyberSecurity #Information #Analysis #CyberChef #GCHQ #LocalInstall
-
Old postcard of The Church, #Goosey, nr #Wantage. It's in #Oxfordshire now but it used to be in #Berkshire. Its also in our store!
#oldpostcardsforsale #history #localhistory #nostalgia #church #churchhistory #vintage -
50 YEARS OF THE ST. JACOB’S MARKET
For over 50 years, the St. Jacobs Market has been a community staple in the Waterloo region.
What started as a livestock exchange in 1975 eventually amalgamated into the St. Jacobs Market.
Joanna Loebach, general manager of St. Jacobs Market District, said the market grew from family members of those participating in the livestock exchange swapping or selling their produce.
“It sort of evolved to become known to people in the area that on sale days, that was a good time to come and actually buy produce from some of the wives or the children of the farmers,” Loebach said.
“From that origin, they set up concrete bunkers…that was the first evolution to actually formalize this into something that the public could attend,” she said.
Seven years later, the first building was built on the market property to accommodate for year-round sales. As more farmers and vendors joined, the attraction to the market grew amongst the community. In the early 90s, the market became a tourist attraction for those looking for authentic maple syrup to be sold there.
From there, the Village of St. Jacobs began to grow along with the additions of the outlet and antique mall in the surrounding areas of the market.
Loebach said now, more than ever, the farm-to-table movement has become increasingly more popular.
“There was a big movement to being more aware about what you were putting into your body and the practices that were behind growing your produce,” Loebach said.
“I think that’s something that has made the farmers market experience just so much more desirable. You get to know who you’re buying from, you’re way more guaranteed about freshness than you are at a grocery store and you’re also getting insider information about how to best serve it or how to store it,” Loebach said.
While the spirit of the market has remained the same, the market has also evolved to mirror the change in demographics and evolution of needs and buying habits.
“There’s always something new here,” Loebach said.
“It keeps it fresh, but it also keeps us being able to adapt to the changing demographics within KW and what the local population is looking for…the market is able to keep pace with that so that it never feels antiquated,” she said.
To celebrate 50 years, the market is reflecting on their legacy vendors—some of which have been a staple at the market since the beginning—as well as some of the newer, more entrepreneurial vendors.
Robert Foreman, owner of 100 Mile Produce, has been a vendor at the St. Jacobs Market for 25 years. Prior to that, he used to come to the market as a child to help at his father’s stall.
For Foreman, a big piece of what makes the market so special for vendors and patrons is that connections made between the food, the farmer and the buyer.
“Depending on which vendors you choose to shop with, you can look the person in the eye and find out exactly where that came from, when it was picked, what the variety name is—the entire history of whatever you’re purchasing,” Foreman said.
As a life-long vendor of the market, Foreman has seen the waves of change that have shaped the evolution of the market, specifically, with regards to changing demographics.
“I can remember years ago, a lot of Eastern European people has moved here in the early 2000’s…and they were asking us to grow certain things,” Foreman said.
“Just because we don’t eat them or we didn’t grow them doesn’t mean we can’t do that, right? And we’ve seen that with each wave of immigration that’s come through,” he said.
As the market continues to evolve and grow, Loebach said this next era continues to acknowledge and celebrate its roots, while finding ways to develop and meet ever-changing needs.
“I am loving how we’re continuing to build on the successes of the farmers market but continuing to make this a spot that will continue to resonate with people over time,” she said.
#100MileProduce #easternEuropean #farmToTable #groceryStore #JoannaLoebach #KatWex #localFood #localHistory #robertForeman #SafinaJennah #StJacobS #waterlooRegion
-
Today a bit of #Advertising for the new issue of "Hessischen Genealogie ( #Hessian #Genealogy ), the journal of @HfV_eV, #Familienkunde Nassau and GFKW:
https://shop.odw-verlag.de/Hessische-Genealogie-1-2026
It includes “#Lampertheim emigrants to #Chillicothe”, an article by me about the #History of the #Migration of around 400 #Refugees from my #Hometown to the former #Capital of #Ohio, #USA.
#FamilyHistory #Hessia #Germany #America #Emigration #GermanEmigration #LocalHistory #GermanSettlers #HistoricalResearch
-
How does MCP work? Maksim built a 'local first' #FlutterDev client to find out.
#DevFest speaker @maks presents: MCP, Flutter and YouSee our full schedule & get tickets at
https://gdg-melbourne-devfest-2025.sessionize.com/ #DevFestMelbourne2025 -
Open Codex CLI: Local-First AI Coding CLI Emerges As Alternative to OpenAI Codex CLI
#OpenCodex #AICoding #LLM #LocalLLM #OpenSource #DeveloperTools #CLI #Python #Phi4Mini #Terminal #AI #CodingAssistant #CommandLine
-
New post: The Markdown Link No. 6
Today’s links include: MiaoYan, a local-first markdown editor; how to create slides from Obsidian docs; Hike, a local markdown browser; Typst, a markup language for typesetting documents; Gram, an opinionated code editor; and 11ty is now Build Awesome.
https://md-handbook.com/blog/markdown-link-no-6
#markdown #markdowneditor #LaTeX #MiaoYan #Obsidian #slides #Hike #Gram
-
New post: The Markdown Link No. 6
Today’s links include: MiaoYan, a local-first markdown editor; how to create slides from Obsidian docs; Hike, a local markdown browser; Typst, a markup language for typesetting documents; Gram, an opinionated code editor; and 11ty is now Build Awesome.
https://md-handbook.com/blog/markdown-link-no-6
#markdown #markdowneditor #LaTeX #MiaoYan #Obsidian #slides #Hike #Gram
-
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:
- https://github.com/cryptocat/cryptocat
- https://github.com/jeremyckahn/chitchatter
(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: https://www.reddit.com/r/cryptography/comments/1cint8h/what_are_your_thoughts_on_subtlecrypto_vs_wasm ... 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.
-
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:
- https://github.com/cryptocat/cryptocat
- https://github.com/jeremyckahn/chitchatter
(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: https://www.reddit.com/r/cryptography/comments/1cint8h/what_are_your_thoughts_on_subtlecrypto_vs_wasm ... 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.
-
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:
- https://github.com/cryptocat/cryptocat
- https://github.com/jeremyckahn/chitchatter
(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: https://www.reddit.com/r/cryptography/comments/1cint8h/what_are_your_thoughts_on_subtlecrypto_vs_wasm ... 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.
-
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:
- https://github.com/cryptocat/cryptocat
- https://github.com/jeremyckahn/chitchatter
(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: https://www.reddit.com/r/cryptography/comments/1cint8h/what_are_your_thoughts_on_subtlecrypto_vs_wasm ... 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.
-
Schön mal wieder in der #Romanfabrik zu sein. Ich war ewig nicht hier. Heute ist The #LocalListener. Gregor Praml trifft u. a. #UncleMaze und #KurtCobain ist Thema.
-
Privacy First, Security Always: The Only Sane Default
“Privacy first, security always” is either a real principle or it is marketing wallpaper.
People can smell the difference now. Not because everyone became a cryptography nerd overnight, but because the consequences turned personal. Accounts get drained. Identities get cloned. A harmless preference turns into a predictive profile. Then a company calls it “personalization” and expects gratitude.
I keep coming back to a simple line: if a system cannot respect boundaries, it does not deserve trust.
The quiet theft is not the breach. It is the business model
Security failures arrive with sirens. Privacy failures arrive with a checkbox.
Teams hide the most invasive defaults behind consent banners, vague policies, and settings buried three menus deep. That is why privacy first has to be architectural. If your product needs intimate data to function, the relationship starts compromised and every debate becomes about permission instead of necessity.
A practical test helps.
Picture your product landing on the desk of a skeptical customer who has already been burned. They ask one question: “Why do you need this data?”
A hand-wavy answer like “we might use it later” reveals the truth. You are not building a service. You are building a warehouse.
Privacy first means you design so the system does not need to know everything about someone in order to work.
Security always is not paranoia. It is respect for entropy
Security is not a feature you bolt on. Security is the discipline you practice.
Most compromises are not clever or dramatic. Routine mistakes create them: misconfigurations, over-permissioned accounts, leaked secrets, and unpatched dependencies.
Permissions sprawl until nobody can map them. Teams ship misconfigurations. Secrets leak because nobody rotates them. Dependencies drag risk into your product like barnacles. Backups fail the one day you need them. Logs exist but never tell a story.
Security always means you assume failure will happen and you engineer the impact down to something survivable.
That mindset can sound pessimistic. In reality, it respects entropy. Systems decay, incentives shift, and people make mistakes. Entropy does not care about your roadmap.
The practical blueprint: collect less, separate, prove
I like frameworks when they sharpen thinking and do not become religious scrolls. The simplest operating model I trust looks like this.
1) Collect less
Collect only what you can defend in one sentence to a skeptical user. Not to your lawyer. To your user.
Reduce identity where you can. Prefer short-lived identifiers over permanent ones. Process locally whenever it makes sense.
A privacy-first system does not brag about protecting your data. It quietly replies, “we never stored it.”
2) Separate what you must store
Treat data like it can explode, because it can.
Separate identifiers, content, metadata, and billing. Force access through clear boundaries. Encrypt sensitive fields at rest. Keep administrative power narrow and observable.
Isolation is also cultural. Engineers should not casually browse production data. A company that must “look inside” to operate has built a fragile machine.
3) Prove what you did
Logging is not glamorous. Auditability is not optional.
Teams earn trust when they can show what happened, who accessed what, and why. If you cannot prove access, you do not control access.
This is where “security always” stops being a vibe and becomes engineering.
Where AI changes the stakes
AI increases the temptation to repurpose data. More data looks like more capability.
That logic has a shadow.
Once the data exists, incentives attack it from every angle. Governments demand it. Attackers leak it. Brokers sell it. Lawyers subpoena it. Insiders misuse it. Product teams pull it into models because it feels convenient.
The old scandal playbook that turned personal information into political influence taught a brutal lesson. People do not hate being measured. People hate being manipulated.
Privacy first, security always refuses to build manipulation pipelines by accident.
The surveillance trade is a false bargain
Leaders keep offering societies the same deal: give up a little privacy for a little security.
The pitch sounds reasonable until you watch the pattern. Privacy leaves first. The promised security rarely arrives.
Real security looks boring in practice. Patching, least privilege, planning for failure, and building systems that do not collapse when one component breaks define it.
Mass surveillance does not deliver security. It delivers power.
That matters if you care about liberal values, because agency needs a private interior. People who feel watched do not explore ideas. They perform. When performance replaces honesty, innovation dies quietly.
What “privacy first, security always” looks like in real products
It looks like choices that feel slightly harder in the short term and far cheaper in the long term.
- End-to-end encryption where it actually matters, especially for private content.
- Local-first or edge-first intelligence where feasible, so insights do not require central hoarding.
- Clear data lifecycles: expiration by default, deletion that is real, retention that is justified.
- User agency that is not performative: export, revoke, rotate, and leave.
- Transparency that is specific: what is collected, why, where it goes, and how long it stays.
Open source helps here, not as ideology, but as visibility. Opaque systems force trust to become faith. Visible systems let trust return to engineering.
Shift: trust is becoming a business strategy again
For years, growth came easiest to the companies that treated people as data sources. That era is wearing out, because distrust is becoming expensive.
Customers ask better questions now. Teams tire of cleaning up preventable incidents. Regulators tighten expectations around data usage, especially when AI enters the picture. Investors learn that “move fast” turns expensive when you pay for the mess.
The economics stay simple: trust costs less to build early than to buy back later.
A line I like has stuck with me.
“You don’t need to drive the car to influence the journey. Speak clearly, and the driver might begin to listen. Place a sign on the roadside, and someone behind you will see it. Offer a compass, and you guide even without steering.”
Privacy first, security always is one of those signposts.
A society that shrugs at surveillance becomes a society that cannot breathe. A company that shrugs at security becomes a company that cannot be trusted. The two failures reinforce each other.
“Privacy first, security always” is the design stance that says: we do not need to own people to serve them.
Build systems that deserve users.
Call to action
If you build products, pick one system this week and run a simple trust audit.
Ask:
- What personal data do we collect that we could remove?
- What do we keep longer than we can justify?
- Who can access sensitive data today, and how do we prove it?
- Which dependency or vendor would hurt us most if it failed?
- What would we tell users within 24 hours of a breach?
If you find a gap, fix one thing. Small repairs compound.
If this resonates, share the post with someone who ships software, and leave a comment with the hardest privacy or security tradeoff you are facing right now. I read them and I will reply.
Key Takeaways
- Privacy first means designing systems that respect user boundaries and don’t require excessive data.
- Security always involves assuming failures will happen and engineering to minimize their impact.
- The practical blueprint consists of collecting less data, separating necessary data, and proving access to it.
- Privacy first, security always discourages manipulation and builds trust between users and companies.
- Companies that prioritize trust will thrive as users demand better data practices and transparency.
-
Save the date! #AllAboutThatPlace is back! It starts Friday 27 September 2024. What are you hoping to learn? What would you like to see more of?
#FamilyHistory #LocalHistory #OnePlaceStudy #OnePlaceStudies #StreetStudy #StreetStudies #HouseHistory #HouseHistories #CemeteryStudy #CemeteryStudies
-
In addition to her #RootsTech presentation #OnePlaceStudies: Studying a Village, @Liz has one with a different #OnePlaceStudy focus: #StreetStudies.
Find out how Liz is researching the history of her street and its residents—lots of great ideas on how you can do the same for the street where you live, or one that your ancestors inhabited! https://www.familysearch.org/en/rootstech/session/one-place-studies-studying-a-street
#FamilyHistory #LocalHistory #StreetStudy #RootsTech2024 #NotAtRootsTech
-
For #MapMonday, a close-up view of part of #Rawtenstall, Lancashire, where Bank Street is the subject of a #OnePlaceStudy (or #StreetStudy) recently begun (and registered with us) by our Chair, @Springhill_OPS.
Profile page: https://www.one-place-studies.org/bank-street-rawtenstall/
-
The latest member-registered #OnePlaceStudy to be added to our website is Tony Smith's #StreetStudy of St John's Square, Wakefield.
Find out more on the OPS profile page: https://www.one-place-studies.org/europe/england/west-yorkshire/st-johns-square-wakefield/
#FamilyHistory #LocalHistory #OnePlaceStudies #OnePlaceWednesday
-
Another new member-registered #OnePlaceStudy is a #StreetStudy, of Northdown Close, #Ruislip, Middlesex—a living memory of the street where one-placer Christine Payne lived.
Find out more in the overview on this study's profile page on our website: https://www.one-place-studies.org/europe/england/middlesex/northdown-close-ruislip/
-
We've three newly-registered #OnePlaceStudies to tell you about today!
First, a #StreetStudy—our member John Cordwell is researching the residents of Haw Street in Wotton-under-Edge, #Gloucestershire, from the 18th to the mid-20th centuries.
Profile page: https://www.one-place-studies.org/europe/england/gloucestershire/haw-street-wotton-under-edge/
#FamilyHistory #LocalHistory #OnePlaceStudy #WottonUnderEdge