home.social
Sign in Create account

Search

184 results for “neuroexception”

  1. eerlijkdigitaalonderwijs.nl @[email protected] ·

    @neuroexception
    Reason 4: Schools teach children that it is perfectly normal to give away all your data to BigTech
    #chromebook #GoogleClassroom #office365 #BigTech

    #bigtech #office365 #googleclassroom #chromebook
  2. aaron ~# :blinkingcursor: @[email protected] ·

    Quick update about my Pixel Watch project

    Progress so far:

    • Wear OS and Android apps
    • Stable and reliable Bluetooth connection between these two
    • Basic Flask backend server
    • Postgresql for data persistence

    The Wear OS app runs the Bluetooth server to which the Android app connects to. After a lot of troubleshooting and testing, i've managed to make it work.

    Even though i'm not sure why. Google claims that the Wearable Data Layer API is the only communication one can use. They even explicitly state that you cannot open a low level socket.

    I will now start building my own wearable API via the existing Bluetooth implementation. I'm very proud of the progress so far. I wasn't sure if this project will be possible.

    I will also try to reproduce the setup process so that one can setup the watch without needing to install the official Pixel Watch app even once.

    #google #pixel #pixelwatch #bluetooth #api #googleplay #googleplayservices #wearable #coding #dev #backend #development #privacy

    #google #pixel #pixelwatch #bluetooth #api #googleplay
  3. aaron ~# :blinkingcursor: @[email protected] ·

    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

    #opensource #smartwatch #pinetime #refurbished #privacy #security
  4. aaron ~# :blinkingcursor: @[email protected] ·

    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

    #opensource #smartwatch #pinetime #refurbished #privacy #security
  5. aaron ~# :blinkingcursor: @[email protected] ·

    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

    #opensource #smartwatch #pinetime #refurbished #privacy #security
  6. aaron ~# :blinkingcursor: @[email protected] ·

    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

    #homelab #selfhosted #selfhosting #api #frontend #googleplayservices
  7. aaron ~# :blinkingcursor: @[email protected] ·

    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

    #opensource #smartwatch #pinetime #refurbished #privacy #security
  8. aaron ~# :blinkingcursor: @[email protected] ·

    I just bought a #refurbished #Google #Pixelwatch2 to try to build my own "Pixel Watch" companion app. Can i make the Pixel Watch 2 work with faked API's? How much can i improve the privacy ? So many ideas. That will be a fun project!

    Let's see how that will go.

    #privacy #surveillance #google #pixel #foss

    #refurbished #google #pixelwatch2 #privacy #surveillance #pixel
  9. aaron ~# :blinkingcursor: @[email protected] ·

    I just bought a #refurbished #Google #Pixelwatch2 to try to build my own "Pixel Watch" companion app. Can i make the Pixel Watch 2 work with faked API's? How much can i improve the privacy ? So many ideas. That will be a fun project!

    Let's see how that will go.

    #privacy #surveillance #google #pixel #foss

    #refurbished #google #pixelwatch2 #privacy #surveillance #pixel
  10. aaron ~# :blinkingcursor: @[email protected] ·

    I just bought a #refurbished #Google #Pixelwatch2 to try to build my own "Pixel Watch" companion app. Can i make the Pixel Watch 2 work with faked API's? How much can i improve the privacy ? So many ideas. That will be a fun project!

    Let's see how that will go.

    #privacy #surveillance #google #pixel #foss

    #refurbished #google #pixelwatch2 #privacy #surveillance #pixel
  11. aaron ~# :blinkingcursor: @[email protected] ·

    I just bought a #refurbished #Google #Pixelwatch2 to try to build my own "Pixel Watch" companion app. Can i make the Pixel Watch 2 work with faked API's? How much can i improve the privacy ? So many ideas. That will be a fun project!

    Let's see how that will go.

    #privacy #surveillance #google #pixel #foss

    #foss #pixel #surveillance #privacy #pixelwatch2 #google
  12. aaron ~# :blinkingcursor: @[email protected] ·

    I just bought a #refurbished #Google #Pixelwatch2 to try to build my own "Pixel Watch" companion app. Can i make the Pixel Watch 2 work with faked API's? How much can i improve the privacy ? So many ideas. That will be a fun project!

    Let's see how that will go.

    #privacy #surveillance #google #pixel #foss

    #refurbished #google #pixelwatch2 #privacy #surveillance #pixel
  13. aaron ~# :blinkingcursor: @[email protected] ·

    #GamesOnWhales is by far the coolest thing i've set up in 2025. I have an #AMD #Radeon RX 9060 XT, 48GB of ram and a #Ryzen 5 in there. Being able to build custom desktops using #Docker and use them without any latency is AWESOME! Now i can play games on my #thinkpad, spin up various different desktops for any usecase, or use my #kalilinux desktop from whatever device i want to. I can even play #Cyberpunk on my #AndroidTV. I have no words to describe how much i love this 😁

    #gaming #docker #gow #gamesonwhales #cloudgaming #cloudcomputing #selfhosting #selfhosted #homelab

    #gamesonwhales #amd #radeon #ryzen #docker #thinkpad
  14. aaron ~# :blinkingcursor: @[email protected] ·

    This makes perfect sense, right?

    Excluding a process from windows defender will be detected.

    Excluding a process and a path from windows defender won't.

    (this is windows 10 on it's last security update)

    #windows #windows10 #windowsdefender

    #windows #windows10 #windowsdefender
  15. aaron ~# :blinkingcursor: @[email protected] ·

    This makes perfect sense, right?

    Excluding a process from windows defender will be detected.

    Excluding a process and a path from windows defender won't.

    (this is windows 10 on it's last security update)

    #windows #windows10 #windowsdefender

    #windows #windows10 #windowsdefender
  16. aaron ~# :blinkingcursor: @[email protected] ·

    This makes perfect sense, right?

    Excluding a process from windows defender will be detected.

    Excluding a process and a path from windows defender won't.

    (this is windows 10 on it's last security update)

    #windows #windows10 #windowsdefender

    #windowsdefender #windows10 #windows
  17. aaron ~# :blinkingcursor: @[email protected] ·

    #ChatControl is over and i can't believe that shit was actually threatening our privacy. Kind of surreal this was a thing.

    #privacy #PrivacyIsARight

    #chatcontrol #privacy #privacyisaright
  18. aaron ~# :blinkingcursor: @[email protected] ·

    I love improving my #homelab. I installed the #docker-socket-proxy to allow #UptimeKuma to access the #Docker #sockets of all my #VMs in a secure manner. The advantage by doing so is that i can now monitor every service including the ones that don't expose a port like #watchtower. And i can also restrict access to given functionalities.

    #selfhosting #homelabs #security #monitoring #uptime #docker #linux #server

    #homelab #docker #uptimekuma #sockets #vms #watchtower
  19. aaron ~# :blinkingcursor: @[email protected] ·

    I love improving my #homelab. I installed the #docker-socket-proxy to allow #UptimeKuma to access the #Docker #sockets of all my #VMs in a secure manner. The advantage by doing so is that i can now monitor every service including the ones that don't expose a port like #watchtower. And i can also restrict access to given functionalities.

    #selfhosting #homelabs #security #monitoring #uptime #docker #linux #server

    #homelab #docker #uptimekuma #sockets #vms #watchtower
  20. aaron ~# :blinkingcursor: @[email protected] ·

    I love improving my #homelab. I installed the #docker-socket-proxy to allow #UptimeKuma to access the #Docker #sockets of all my #VMs in a secure manner. The advantage by doing so is that i can now monitor every service including the ones that don't expose a port like #watchtower. And i can also restrict access to given functionalities.

    #selfhosting #homelabs #security #monitoring #uptime #docker #linux #server

    #server #linux #uptime #monitoring #security #homelabs
  21. aaron ~# :blinkingcursor: @[email protected] ·

    I love improving my #homelab. I installed the #docker-socket-proxy to allow #UptimeKuma to access the #Docker #sockets of all my #VMs in a secure manner. The advantage by doing so is that i can now monitor every service including the ones that don't expose a port like #watchtower. And i can also restrict access to given functionalities.

    #selfhosting #homelabs #security #monitoring #uptime #docker #linux #server

    #homelab #docker #uptimekuma #sockets #vms #watchtower
  22. aaron ~# :blinkingcursor: @[email protected] ·

    Making the most out of a small LLM

    Yesterday i finally built my own #AI #server. I had a spare #Nvidia RTX 2070 with 8GB of #VRAM laying around and wanted to do this for a long time.

    The problem is that most #LLMs need a lot of VRAM and i don't want to buy another #GPU just to host my own AI. Then i came across #gemma3 and #qwen3. Both of these are amazing #quantized models with stunning reasoning given that they need so less resources.

    I chose huihui_ai/qwen3-abliterated:14b since it supports #deepthinking, #toolcalling and is pretty unrestricted. After some testing i noticed that the 8b model performs even better than the 14b variant with drastically better performance. I can't make out any quality loss there to be honest. The 14b model sneaked in chinese characters into the response very often. The 8b model on the other hand doesn't.

    Now i've got a very fast model with amazing reasoning (even in German) and tool calling support. The only thing left to improve is knowledge. #Firecrawl is a great tool for #webscraping and as soon as i implemented websearching, the setup was complete. At least i thought it was.

    I want to make the most out of this LLM and therefore my next step is to implement a basic #webserver that exposes the same #API #endpoints as #ollama so that everywhere ollama is supported, i can point it to my python script instead. This way it feels like the model is way more capable than it actually is. I can use these advanced features everywhere without being bound to it's actual knowledge.

    To improve this setup even more i will likely switch to a #mixture_of_experts architecture soon. This project is a lot of fun and i can't wait to integrate it into my homelab.

    #homelab #selfhosting #privacy #ai #llm #largelanguagemodels #coding #developement

    #ai #server #nvidia #vram #llms #gpu
  23. aaron ~# :blinkingcursor: @[email protected] ·

    I was today years old when i realized that #Obsidian is absolutely #overpowered when it comes to creating a #resume. Using #HTML, #CSS and #Markdown gives me so much more flexibility.

    #productivity

    #obsidian #overpowered #resume #html #css #markdown
  24. aaron ~# :blinkingcursor: @[email protected] ·

    It's my first time using an #AMD #GPU on #linux and oh boy, what a difference. Might also be the first time to experience true, stutter-free #165hz. There is a world of a difference between my old #nvidia gpu and the new #amd gpu.

    #amd #gpu #linux #165hz #nvidia
  25. aaron ~# :blinkingcursor: @[email protected] ·

    Managing #OpenWRT via #Ansible is a breeze. I just love the fact that all the settings, all the #firewall rules, all the good stuff is configured with config files.

    I've created 6 #VLANs, all of them completely #isolated, with a few allowed traffic rules. I've even isolated the #Windows #PC of my roommate inside of the #trusted #network.

    Now his #XiaomiTVBox can't scan the network anymore (yes it actually does that. I've noticed it while working on my packet monitoring project).

    #networking #subnetting #subnet #homelab #selfhosting #openwrt #privacy #security #vlan #isolation #dmz

    #openwrt #ansible #firewall #vlans #isolated #windows
  26. aaron ~# :blinkingcursor: @[email protected] ·

    I just signed myself on for another 6 years of #GrapheneOS by getting a new #Pixel9ProXL. I absolutely love this device. The performance is stunning and the design is so clean. This is a good fit for the next years 😄

    #grapheneos #pixel9proxl
  27. aaron ~# :blinkingcursor: @[email protected] ·

    Yesterday i worked on #IPv6 support on my #openwrt #router. Splitting the IPv6-PD into my 6 interfaces felt like rocket sience since i never had to actually understand IPv6. Customizing the #ULA to include the interface ID and custom prefix wasn't easier either.

    But hey, it's working now and it's definitely worth learning. As soon as that's done i'm gonna work on my #packet #monitoring service again because this time i can #deploy it directly on my router and ban abusive IP's #network wide.

    #ipv6 #openwrt #router #ula #packet #monitoring
  28. aaron ~# :blinkingcursor: @[email protected] ·

    It took a bit of trial and error but i finally got the #tor routing to work properly without any dns leaks. This is probably the coolest #AccessPoint around.

    #openwrt #tornetwork #proxy #privacy

    #tor #accesspoint #openwrt #tornetwork #proxy #privacy
  29. aaron ~# :blinkingcursor: @[email protected] ·

    #OpenWRT on a #Fritzbox is kinda pain since there are so many things i could technically do if the fritzbox had more powerful hardware. Can't wait to build my own router.

    A #Fujitsu #Thinclient S920 would be a perfect fit and is also cheap as hell.

    More powerful hardware would allow me to take advantage of #tor #routing, local #tailscale resolving, #adblocking and much more. Maybe even some #docker #containers like #caddy.

    #OpenWRT is a real #gamechanger for my #homenetwork.

    #homelab #selfhosting #opensource #freeandopensource #network #networking #firewall

    #openwrt #fritzbox #fujitsu #thinclient #tor #routing
  30. aaron ~# :blinkingcursor: @[email protected] ·

    #OpenWRT is such a valuable learning experience. I'm able to test it, learn how it works and will definitely buy a #OpenWRTOne

    #openwrt #openwrtone
Next page