#BlueBrick
The old phone booth and blue glazed brick wall drew me towards this old Bell Telephone building in Vandalia, Missouri.

#photography #vandalia #illinois #streetscape #streetview #streetscapephotography #phonebooth #belltelephone #bellblue #bluebrick #glazedbrick
November 18, 2026 at 7:00 PM
If you see this, QP your dragons!🐉

This is actually my eldest daughter’s OC, Becky Bluebrick The Bubble Dragon, drawn in my style as a guest OC in #Premonitia
November 6, 2026 at 11:30 PM
If you see this, post something blue. 👁️👁️💙🩵🫧🐚
October 23, 2026 at 2:05 AM
Es gibt keine wirkliche Garantie, dass wir in der Sache dieser einen Anfrage Erfolg haben werden, aber am wichtigsten ist die rechtliche Klärung. Möglich wird das nur aufgrund der großzügigen Unterstützung von Rechtsanwalt Dr. Rainer Hable und …
About Dr. Rainer Hable | Bluebrick Chambers - bluebricklaw.com
Dr. Rainer Hable | Vita | Attorney at Law | EU Law & Litigation
bluebricklaw.com
October 21, 2026 at 10:13 AM
Thank you for hosting! 🤘🤩🤘

This time I’m compelled to share my interpretation of my daughter’s OC: Becky Bluebrick The Bubble Dragon! 🐉 🫧🩵🩷
October 9, 2026 at 7:43 PM
Thank you for hosting! I was tagged !! 🤘🥳🤘

I’m writing and illustrating a graphic novel series about dreams I’ve been having since I was a tiny child. Here’s some scenes and characters:

A little bit of abs, but a WHOLE LOT of SPARKLES!!✨
September 22, 2026 at 12:29 AM
I wound this beautiful gradient up. The plan is a shawl for a friend that will remind her of the Ukrainian flag. I don't want to waste a bit of those colour changes. Yarn by The Blue Brick, a Canadian indie dyer. #Yarn #knitting #Shawl #BlueBrick #gradient #Canadian #indiedyer
January 31, 2025 at 6:14 AM
AfterHannah &Sascha walkplay Nelson Park🚶‍♀️🐕 🐕❤️ ❤️ Jog UTube🎶🇨🇦
In A Lifetime-Ain't No Stopping Us
Until You Come Back to Me-Never Let Me Down-Spiritual High
April FoolPainted Moon-The Silencers ❤️RecklessI'm BlueBrick House-American Idiot-Holiday
When I Come Around -Brain Stew
A Woman's Got the Power
May 2, 2026 at 6:40 PM
Bluebrick Lego GIF
Alt: Legoblock mir AUgen
media.tenor.com
August 6, 2024 at 6:05 AM
random LEGO piece ;0)
July 26, 2024 at 4:13 PM
Off the blocking pins... Pattern is #WildSwan off Ravelry, yarn is Tulipa from #BlueBrick yarns.

#knitting #knittedlace #gradientyarn
April 17, 2026 at 2:28 PM
And yes, this is all one ship.
BlueBrick & BrickBandana came from the trinkets.
CloudySpikes, DarkDreams, DarkClouds, and DreamSpikes came from the skins.
June 17, 2025 at 12:05 PM
I like BoxShrimp, BentoBox, DissTrack, BreakDance, ShyAnger, HateSong, ShrimpBox, MusicalHatred, ShrimpSong, HateBox, ShyShrimp, AngryBox, AngryMusic, BlueBrick, BrickBandana, CloudySpikes, DarkDreams, DarkClouds, DreamSpikes …oh, and Boxten x Shrimpo!
#Boxten #Shrimpo #BoxShrimp #ShrimpBox
June 17, 2025 at 12:03 PM
Some recent updates in BlueBrick for the digital design plan for my Lego City of Brooksville!
December 29, 2025 at 2:14 AM
On a Monday Popup Brookstream: Continued my Brooksville City redevelopment in BlueBrick. Some major progress and steps forward with a few adjustments made. Super happy about where this is going!
July 8, 2025 at 2:44 AM
On my Thursday Evening Brookstream: Got back into some BlueBrick design work to continue redesign of my Lego City of Brooksville! More progress made and some breakthroughs with the "lower" section! Feeling good about where it's going!
July 4, 2025 at 12:24 AM
On my Tuesday Evening Brookstream: A completely new concept for me - doing digital design work! I'm using a program called BlueBrick to do a wholescale redesign of my Lego City from scratch. Here is some of the initial stages of what it looks like. This is all subject to change and evolve!
April 30, 2025 at 1:36 AM
Interview With Cape, a Privacy-Focused Carrier
bluebrick: > IMZ IMSI bluebrick: > wouldn’t it make a feature like IMZ rotation redundant There’s three things going on here: 1. Your IMSI can be seen by **anyone** in the local area. This is the primary way things _other than your carrier_ , such as MITM/Stingray devices, track people. Your IMEI, on the other hand, can only be seen by the carrier after mutual authentication is performed. This **is** a legitimate protection that IMSI rotation provides, where the IMEI doesn’t matter, and IMO it’s the main protection most people should be thinking about. 2. Your IMSI is used by attackers to perform SS7 (or similar) attacks, they need it to hijack your connection via a compromised carrier. Because your IMSI changes very infrequently with most carriers, attackers will sometimes/usually store people’s IMSI numbers for _months/years_ before they perform an attack. IMSI rotation renders this nearly impossible because the window to attack is very small. This is a legitimate protection IMSI rotation provides as well, but IMO less useful to most people simply because you probably will not be targeted by this sort of attack. If you are a target though, IMSI Rotation and Network Lock are both very useful tools. 3. Cape’s general thesis is that most carriers are tracking people and/or monetizing their data only using IMSI numbers, because they are per-user identifiers they control, whereas your IMEI can theoretically change for any reason (like, you change your phone) or be shared amongst multiple users (if you give your phone to a family member or someone later). So throwing IMSI rotation into the mix (see 20:02 in the interview I think) kind of makes tracking _uneconomical._ Since AT&T can track the 99.9% of people who aren’t using Cape much more accurately with IMSI numbers, they simply haven’t really built the tools to track people via IMEI in the same way. This might be true tbh, but obviously it is not a _technical_ protection like the other two points, since they _can_ track people using their IMEI as you said, they just “don’t.” The long story short is that IMSI rotation has legitimate protections against attackers _other than your carrier_ , but IMSI rotation is not enough to protect you from the carrier itself. Also, note that #3 only applies to AT&T/T-Mobile when you connect to Cape using their towers. Cape themselves basically have full access all of your carrier activity, the only protections _from Cape_ are basically their logging policy and the fact that they collect very limited billing data, but defending yourself _from Cape_ is not the primary use-case for this carrier. bluebrick: > As I understand it the tower operators would only be the main number. Yes. I am also told _at some point_ they want to protect the main number in the same way secondary numbers are protected, so that any primary number usage goes directly through their servers, but that hasn’t been built yet.
discuss.privacyguides.net
July 17, 2026 at 12:19 AM
How do MFA methods compare?
bluebrick: > someone steals from me in public This hopefully doesn’t happen every day but even if it does, they will still need to have some other things to access your account. Moreover, most websites do have verification regarding a new IP so you will never have the situation where stealing your hardware key grants access to everything of yours. It is still usually additive and not the only way. bluebrick: > Even sync options could cause issues because if all devices which have access to said services are stolen at once If you do have some cloud sync, you’re not really loosing the data ever. If you do the sync yourself, it could be always available on a server/NAS of some sort. Moreover, if your threat model is such I suppose you need to consider having one of your devices stored in a safe place at all time and is more of a physical compromise/backup/redundancy concern rather than MFA. bluebrick: > So, to me it seems if I want to do things properly I either remember the passwords to such services Wouldn’t recommend this one. bluebrick: > I am not really seeing a huge benefit in using a YubiKey Yubikeys have the edge of: * phishing resistance (unlike TOTP where you could just type the code into a fake input text) * doesn’t need to have a battery to work * less prone to being stolen (most people might not known what those are even used for) unlike a phone that looks more appealing/resell-able * it cannot be compromised unlike your phone with it being a keylogger or any other kind of malicious apps running on it * less friction (subjective take) None of those might apply to you but I personally do see a lot of value in them. bluebrick: > FOSS YubiKey Authenticator app You can do such a thing yes but it is meanwhile not FOSS This is the one I’m referring too so that we’re sure of which one it is. Yubico ### Download Yubico Authenticator - Yubico Authenticator The safest authenticator app experience across mobile and desktop | Secure your accounts and protect your data with the Yubico Authenticator App. Get authentication seamlessly across all major desktop and mobile platforms.
discuss.privacyguides.net
March 5, 2026 at 2:04 PM
How do MFA methods compare?
bluebrick: > someone steals from me in public This hopefully doesn’t happen every day but even if it does, they will still need to have some other things to access your account. Moreover, most websites do have verification regarding a new IP so you will never have the situation where stealing your hardware key grants access to everything of yours. It is still usually additive and not the only way. bluebrick: > Even sync options could cause issues because if all devices which have access to said services are stolen at once If you do have some cloud sync, you’re not really loosing the data ever. If you do the sync yourself, it could be always available on a server/NAS of some sort. Moreover, if your threat model is such I suppose you need to consider having one of your devices stored in a safe place at all time and is more of a physical compromise/backup/redundancy concern rather than MFA. bluebrick: > So, to me it seems if I want to do things properly I either remember the passwords to such services Wouldn’t recommend this one. bluebrick: > I am not really seeing a huge benefit in using a YubiKey Yubikeys have the edge of: * phishing resistance (unlike TOTP where you could just type the code into a fake input text) * doesn’t need to have a battery to work * less prone to being stolen (most people might not known what those are even used for) unlike a phone that looks more appealing/resell-able * it cannot be compromised unlike your phone with it being a keylogger or any other kind of malicious apps running on it * less friction (subjective take) None of those might apply to you but I personally do see a lot of value in them. bluebrick: > FOSS YubiKey Authenticator app You can do such a thing yes but it is meanwhile not FOSS This is the one I’m referring too so that we’re sure of which one it is. Yubico ### Download Yubico Authenticator - Yubico Authenticator The safest authenticator app experience across mobile and desktop | Secure your accounts and protect your data with the Yubico Authenticator App. Get authentication seamlessly across all major desktop and mobile platforms.
discuss.privacyguides.net
March 5, 2026 at 12:03 PM
Email Aliasing Strategy Planning
bluebrick: > Go with the lifetime plan and not be stuck in a subscription model I also do not like subscriptions but sometimes they are a necessary evil (like an electricity bill). I’d also rather be “stuck” in a subscription but free to move to a better service rather than sit there with a service I do not like. And with the burden of needing to then get a subscription after paying a lifetime. The more you go into an ecosystem, the harder it is to get away from it. I value (freedom of choice + better specific tool for 1 given task) more than some savings. Nothing is eternal and things will go to shit at some point, hence I’d rather not have hard ties and avoid putting all eggs into 1 single _cozy_ basket. For all the things that can be done DIY or can be done for free without privacy compromises then sure! But software + politics + companies’ mood might change in 1 year, maybe 5 or maybe 10. It’s easier to drop out from Addy and move to [the new hot FOSS service in town] that way. * * * If you really don’t care that much and would rather prefer saving money with an all in one solution, then go all in on the Proton ecosystem for sure! There is a reason they are a quite successful business so far: convenience. But yeah, I’ve had my fair share of walled garden with Apple. I’m quite allergic to the idea of “ecosystem” as of lately. And prefer to not have such a thing. But again, it’s just me. Maybe give a quick trial to Proton for 1 month or alike before going all in! If you’re happy enough, then sure. Simple login was just not cutting it for me… * * * bluebrick: > So, is there a big difference between the free and paid vpn, because, the free one has met my needs so far. Any other reasons to do Unlimited? If not, is just the Proton Drive enough for Unlimited? Here same: * their VPN is decent enough but as Rtings recently shown, they are not the best in their own domain * they also do have quite some KYC overall given that you do have an account under the same roof * are not the best in terms of their policies + company practices * I’d rather pay for the best service in their own domain (for the few critical ones) * the free VPN is **very basic** but if it’s fine for you, why not? * Proton Drive also is not as flexible as I wanted it to be for me * too restrictive as of how I access the data (no WebDav for example) * not as refined of an experience as I wanted It’s again very personal regarding your threat model + budget + needs. I’ll be always vouching for the fact that “lifetime [anything]” is quite a big bait. Especially as seen in the past years: not a lot of companies are trustworthy. Hence yearly plans are still the way to go IMO. * * * Grapeg: > The huge advantage is portability Yes. Trade-off of anonymity in favor of portability/ownership. I would argue that you could also just skip the entire Aliasing system if all you need is a clean mailbox + brand identity because you can also create on the fly usernames. A bit more work but probably doable (if not using the catch all).
discuss.privacyguides.net
January 20, 2026 at 10:25 PM
Email Aliasing Strategy Planning
bluebrick: > I do not plan to use a custom domain anytime soon. That’s good. Custom domain GREATLY reduce your privacy (since whatever you use before `@` you still youse same domain used only by you). bluebrick: > I’d prefer to avoid subscribing to the full Proton suite; a SimpleLogin or Addy.io subscription is ideal. Addy not recommended, since they have limitations on bandwidth. I recommend SL or Duck aliasing. If you can go with Proton Pass + Simplelogin Lifetime. No subscriptions, just one time purchase. bluebrick: > However, many aliases end up looking “messy.” If I need to give out an email address in person (for example, at a doctor’s office), what’s the best way to handle this? Should I just pull out my phone and write down an alias? For situations you don’t need anonymity (like doctor, bank etc who already know who are you) use subdomain feature in SL. It allows you to get something like `hi@your-subdomain.simplelogin.com`. But remember NOT to use it where you need to hide who are you (for ex. newsletters) because subdomains unique and whatever you use before `@` you still you use same subdomain used only by you bluebrick: > If I forward emails from my old email account to the new Proton account, should I forward them to an alias that then redirects to Proton, so the old provider doesn’t learn my actual Proton address? I don’t see any issues. I did exactly like this. But it can vary. bluebrick: > What are the benefits of using an alias for accounts that already contain other personal information? If alias leaks, you can change it, without need of getting tons of spam on real email, which is nearly impossible to change. bluebrick: > How bad is it to group multiple services under a single alias? This would avoid needing any subscriptions. Not so bad, but if you decide to change alias (e.g leak) you will get a hassle to go through all this group. bluebrick: > Slightly unrelated: Is it recommended to formally delete unused accounts, or is it fine to leave them inactive? Yes. You should delete them, because if ever leaked, bad actors can use varios tactics (eg credentials stuffing, rainbow tables etc) to access them and use for nefarious purposes. P.S.: i recommend to disable catch-all on subdomain, because of spam.
discuss.privacyguides.net
January 20, 2026 at 2:21 PM