#qualityoflife — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #qualityoflife, aggregated by home.social.
-
Warsaw’s Post-Pandemic Renaissance: A European Capital Rising
1.WarsawPoland Some 34 years since the fall of communism, Warsaw is a thriving European capital with an increasingly…
#Poland #Polska #PL #Europe #Europa #EU #Warsaw #Cities #dubai #europeancities #KualaLumpur #malaysia #Mérida #Mexico #Morocco #politicaltransformation #post-pandemic #qualityoflife #rabat #refugees #UAE #urbandevelopment #urbantransformation #Urbanism
https://www.europesays.com/poland/18280/ -
https://www.europesays.com/dk/134650/ Warsaw’s Post-Pandemic Renaissance: A European Capital Rising #Cities #dubai #EuropeanCities #KualaLumpur #Malaysia #Mérida #Mexico #Morocco #Poland #PoliticalTransformation #PostPandemic #QualityOfLife #rabat #Refugees #UAE #UrbanDevelopment #UrbanTransformation #Urbanism #Warsaw
-
Maribor rises: Slovenia’s second city draws new talent https://www.byteseu.com/2158367/ #ChocolateVillage #CostOfLiving #CreativeIndustries #CreativeStartups #Drava #Entrepreneurs #EuropeanCapitalOfCulture #EuropeanCities #ljubljana #MarcosTavares #maribor #MatejHotko #QualityOfLife #SasaArsenovic #SecondCity #Slovenia #TanjaGolob #TanjaUvera #TechnologyEcosystem #TetaFrida #UrbanLapajne #UrosMlakar
-
Maribor rises: Slovenia’s second city draws new talent
For a second city, Maribor boasts a rem…
#Slovenia #SI #Europe #Europa #EU #chocolatevillage #costofliving #CreativeIndustries #creativestartups #Drava #Entrepreneurs #europeancapitalofculture #europeancities #Ljubljana #MarcosTavares #maribor #MatejHotko #Novice #qualityoflife #SasaArsenovic #secondcity #slovenia #Slovenija #TanjaGolob #TanjaUvera #technologyecosystem #TetaFrida #UrbanLapajne #UrosMlakar
https://www.europesays.com/3101444/ -
Half Of European Municipalities Have Fewer Inhabitants Than 60 Years Ago
--
https://correctiv.org/aktuelles/2026/04/21/die-haelfte-der-europaeischen-gemeinden-hat-weniger-einwohner-als-vor-60-jahren/ <-- shared technical / spatiotemporal article
--
https://data.jrc.ec.europa.eu/dataset/37fcacbf-12e2-4b31-b1af-83117a74b2c7 <-- shared European Joint Research Centre (JRC) ARDECO Local Population Time-Series – 1961-2024
--
#GIS #spatial #mapping #emptyspain #demographics #population #agingpopulation #declining #birthrate #immigration #emigration #shrinking #interactive #webmap #spatialanalysis #spatiotemporal #Europe #geostatistics #logistics #rural #urban #city #transportation #cost #economics #services #infrastructure #workers #qualityoflife #planning
@JointResearchCentre #JRC @europeancommission @correctiv_org -
Last week's #ONS seminar "Introducing the UK headline measures of national #wellbeing" was interesting. The session was not recorded but the slides are available here:
https://www.slideshare.net/slideshow/introducing-the-uk-headline-measures-of-national-well-being/286342213Areas of discussion in the Q&A:
- A report on the methodology deriving these indicators potentially to be published.
- Does #BeyondGDP include GDP? -
Pixel Watch 2 - Privacy Preserving Setup
I've been trying everything i could think of to make the watch work under GrapheneOS - Here is what i learned:
- Unpairing the Watch means factory resetting it.
- Every feature (literally everything) is google dependent (who would have thought.. i know)
- Pairing with your phone requires the "Pixel Watch" -App to be installed on your main profile (not work, not private space) alongside Google Play Services. There's no way around.
This is obviously unacceptable. So i did a bit of research and found a way that will not only be way more practical, it will also be private.
First i created a second user on my Phone, installed Google Play Services and the pixel watch app on it, logged in with a newly created google account and completed the setup.
I know some people use a chinese version of the WearOS app to bypass the google login. Since i don't want a chinese app to configure my watch, i didn't even try that.
After the watch was set up, i continued and:
- Deleted the user profile from which i connected the Watch
- Enabled wireless debugging
- Debloated the watch as good as possible (i will have to root the watch in the future to properly do it)
- Removed the Google account in the settings
- Cleared all Bluetooth preferences
- Enabled Bluetooth discovery
- Installed KDE Connect on it (not meant for WearOS but it does work barely)
The watch is now in a state where i can use it daily.
But i also want to make use of all those fancy quality-of-life features, like heartrate monitoring, sleep tracking and so on.
Now comes the fun part.
I've created a basic Kotlin project with both a mobile and WearOS app.
I will implement features like:
- Notification sync
- Call notifications
- Media Player Control
- Weather (openweathermap)
- Heartrate monitoring
- Sleep tracking
- Do not Distrurb Sync
- Homelab integrations (Nextcloud, Immich, Uptime Kuma, ..)
- And much more ..
The goal is to keep the watch offline, let the phone do the heavy lifting and communicate with a selfhosted database. I may even add a frontend and an API so people can integrate it for their needs.
Sounds good but why don't you just buy an #opensource #smartwatch like the #pinetime - You may ask.
Because as much as i hate to admit it, i love the design, the look and feel of the pixel watch. And i'm sure that i'm not the only one.
I also bought this one cheap for around 120€ #refurbished. So the value i can get out of it seems pretty good to me.
So much for today. I haven't even started tackling the Bluetooth connection yet 😅. Let's see how that turns out
I have added a poll to this post to see how many people would be interested in a setup like this. Please let me know if you have any suggestions, ideas or expertise in that regard.
Cheers.
#privacy #security #android #google #pixel #pixelwatch #degoogle #degoogling #degoogled #adb #rooting #grapheneos #smartwatch #development #wearos #bluetooth #qualityoflife #GooglePlay #GooglePlayServices #frontend #api #selfhosting #selfhosted #homelab #opensource
-
Pixel Watch 2 - Privacy Preserving Setup
I've been trying everything i could think of to make the watch work under GrapheneOS - Here is what i learned:
- Unpairing the Watch means factory resetting it.
- Every feature (literally everything) is google dependent (who would have thought.. i know)
- Pairing with your phone requires the "Pixel Watch" -App to be installed on your main profile (not work, not private space) alongside Google Play Services. There's no way around.
This is obviously unacceptable. So i did a bit of research and found a way that will not only be way more practical, it will also be private.
First i created a second user on my Phone, installed Google Play Services and the pixel watch app on it, logged in with a newly created google account and completed the setup.
I know some people use a chinese version of the WearOS app to bypass the google login. Since i don't want a chinese app to configure my watch, i didn't even try that.
After the watch was set up, i continued and:
- Deleted the user profile from which i connected the Watch
- Enabled wireless debugging
- Debloated the watch as good as possible (i will have to root the watch in the future to properly do it)
- Removed the Google account in the settings
- Cleared all Bluetooth preferences
- Enabled Bluetooth discovery
- Installed KDE Connect on it (not meant for WearOS but it does work barely)
The watch is now in a state where i can use it daily.
But i also want to make use of all those fancy quality-of-life features, like heartrate monitoring, sleep tracking and so on.
Now comes the fun part.
I've created a basic Kotlin project with both a mobile and WearOS app.
I will implement features like:
- Notification sync
- Call notifications
- Media Player Control
- Weather (openweathermap)
- Heartrate monitoring
- Sleep tracking
- Do not Distrurb Sync
- Homelab integrations (Nextcloud, Immich, Uptime Kuma, ..)
- And much more ..
The goal is to keep the watch offline, let the phone do the heavy lifting and communicate with a selfhosted database. I may even add a frontend and an API so people can integrate it for their needs.
Sounds good but why don't you just buy an #opensource #smartwatch like the #pinetime - You may ask.
Because as much as i hate to admit it, i love the design, the look and feel of the pixel watch. And i'm sure that i'm not the only one.
I also bought this one cheap for around 120€ #refurbished. So the value i can get out of it seems pretty good to me.
So much for today. I haven't even started tackling the Bluetooth connection yet 😅. Let's see how that turns out
I have added a poll to this post to see how many people would be interested in a setup like this. Please let me know if you have any suggestions, ideas or expertise in that regard.
Cheers.
#privacy #security #android #google #pixel #pixelwatch #degoogle #degoogling #degoogled #adb #rooting #grapheneos #smartwatch #development #wearos #bluetooth #qualityoflife #GooglePlay #GooglePlayServices #frontend #api #selfhosting #selfhosted #homelab #opensource
-
Pixel Watch 2 - Privacy Preserving Setup
I've been trying everything i could think of to make the watch work under GrapheneOS - Here is what i learned:
- Unpairing the Watch means factory resetting it.
- Every feature (literally everything) is google dependent (who would have thought.. i know)
- Pairing with your phone requires the "Pixel Watch" -App to be installed on your main profile (not work, not private space) alongside Google Play Services. There's no way around.
This is obviously unacceptable. So i did a bit of research and found a way that will not only be way more practical, it will also be private.
First i created a second user on my Phone, installed Google Play Services and the pixel watch app on it, logged in with a newly created google account and completed the setup.
I know some people use a chinese version of the WearOS app to bypass the google login. Since i don't want a chinese app to configure my watch, i didn't even try that.
After the watch was set up, i continued and:
- Deleted the user profile from which i connected the Watch
- Enabled wireless debugging
- Debloated the watch as good as possible (i will have to root the watch in the future to properly do it)
- Removed the Google account in the settings
- Cleared all Bluetooth preferences
- Enabled Bluetooth discovery
- Installed KDE Connect on it (not meant for WearOS but it does work barely)
The watch is now in a state where i can use it daily.
But i also want to make use of all those fancy quality-of-life features, like heartrate monitoring, sleep tracking and so on.
Now comes the fun part.
I've created a basic Kotlin project with both a mobile and WearOS app.
I will implement features like:
- Notification sync
- Call notifications
- Media Player Control
- Weather (openweathermap)
- Heartrate monitoring
- Sleep tracking
- Do not Distrurb Sync
- Homelab integrations (Nextcloud, Immich, Uptime Kuma, ..)
- And much more ..
The goal is to keep the watch offline, let the phone do the heavy lifting and communicate with a selfhosted database. I may even add a frontend and an API so people can integrate it for their needs.
Sounds good but why don't you just buy an #opensource #smartwatch like the #pinetime - You may ask.
Because as much as i hate to admit it, i love the design, the look and feel of the pixel watch. And i'm sure that i'm not the only one.
I also bought this one cheap for around 120€ #refurbished. So the value i can get out of it seems pretty good to me.
So much for today. I haven't even started tackling the Bluetooth connection yet 😅. Let's see how that turns out
I have added a poll to this post to see how many people would be interested in a setup like this. Please let me know if you have any suggestions, ideas or expertise in that regard.
Cheers.
#privacy #security #android #google #pixel #pixelwatch #degoogle #degoogling #degoogled #adb #rooting #grapheneos #smartwatch #development #wearos #bluetooth #qualityoflife #GooglePlay #GooglePlayServices #frontend #api #selfhosting #selfhosted #homelab #opensource
-
Pixel Watch 2 - Privacy Preserving Setup
I've been trying everything i could think of to make the watch work under GrapheneOS - Here is what i learned:
- Unpairing the Watch means factory resetting it.
- Every feature (literally everything) is google dependent (who would have thought.. i know)
- Pairing with your phone requires the "Pixel Watch" -App to be installed on your main profile (not work, not private space) alongside Google Play Services. There's no way around.
This is obviously unacceptable. So i did a bit of research and found a way that will not only be way more practical, it will also be private.
First i created a second user on my Phone, installed Google Play Services and the pixel watch app on it, logged in with a newly created google account and completed the setup.
I know some people use a chinese version of the WearOS app to bypass the google login. Since i don't want a chinese app to configure my watch, i didn't even try that.
After the watch was set up, i continued and:
- Deleted the user profile from which i connected the Watch
- Enabled wireless debugging
- Debloated the watch as good as possible (i will have to root the watch in the future to properly do it)
- Removed the Google account in the settings
- Cleared all Bluetooth preferences
- Enabled Bluetooth discovery
- Installed KDE Connect on it (not meant for WearOS but it does work barely)
The watch is now in a state where i can use it daily.
But i also want to make use of all those fancy quality-of-life features, like heartrate monitoring, sleep tracking and so on.
Now comes the fun part.
I've created a basic Kotlin project with both a mobile and WearOS app.
I will implement features like:
- Notification sync
- Call notifications
- Media Player Control
- Weather (openweathermap)
- Heartrate monitoring
- Sleep tracking
- Do not Distrurb Sync
- Homelab integrations (Nextcloud, Immich, Uptime Kuma, ..)
- And much more ..
The goal is to keep the watch offline, let the phone do the heavy lifting and communicate with a selfhosted database. I may even add a frontend and an API so people can integrate it for their needs.
Sounds good but why don't you just buy an #opensource #smartwatch like the #pinetime - You may ask.
Because as much as i hate to admit it, i love the design, the look and feel of the pixel watch. And i'm sure that i'm not the only one.
I also bought this one cheap for around 120€ #refurbished. So the value i can get out of it seems pretty good to me.
So much for today. I haven't even started tackling the Bluetooth connection yet 😅. Let's see how that turns out
I have added a poll to this post to see how many people would be interested in a setup like this. Please let me know if you have any suggestions, ideas or expertise in that regard.
Cheers.
#privacy #security #android #google #pixel #pixelwatch #degoogle #degoogling #degoogled #adb #rooting #grapheneos #smartwatch #development #wearos #bluetooth #qualityoflife #GooglePlay #GooglePlayServices #frontend #api #selfhosting #selfhosted #homelab #opensource
-
Good Morning #Canada
There is a little known reporting tool on the ##StatsCan website called Canada’s Quality of Life Hub. First proposed in 2021, and launched in 2023, it is a framework that gathers data and evidence to inform priority setting and guide decision-making in various policy areas, including the budgetary process. The Framework comprises five domains –prosperity, health, environment, society, and good governance – and two cross-cutting lenses: fairness and inclusion, and sustainability and resilience. Not enough Canadians have heard of it, and I suspect very few government policies are implemented before analyzing the impact on quality of life measurement by this tool. On a positive note, #StatsCan is looking for feedback on how to improve the hub.#CanadaIsAwesome #QualityOfLife
https://www160.statcan.gc.ca/index-eng.htm -
How the Elite rigged Society (and why it’s falling apart) | David Brooks
https://www.youtube.com/watch?v=QSa52TR9tCA
#socialContracts #Morals #politics #QualityOfLife #Elites #Incompetence #SocialImmobility #Ethics #MoralNorms
