![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
Without teens and boomers, social media would be dead.
Without teens and boomers, social media would be dead.
According to me and most of my buddies, the answer is diverticulitis in varying degrees.
Ah, so very similar to what Amazon did with Sidewalk a few years back. I shocked people are ok with allowing this data through their devices. Sidewalk caused a massive backlash because of privacy and data rate concerns.
I’m not a big Apple person, so I’ve not really cared about Airtags, so I’m probably missing something. If I don’t allow them to connect to my device, how are they a concern?
Edit: I realized I asked my question poorly. I get they’re a tracking device. My understanding is they’re a Bluetooth device that do not have direct Internet access on their own; how is their location being updated if you’re not pairing with them to allow them access to your device?
Imo, nobody won here and the reddit user lost everything. The Fediverse wasnt ready for the influx of users and lost its chance to “win” for a long time. The sites couldn’t support the load and there was a lack of polished mobile apps that felt familiar to people that wanted to browse and shit post.
Without content – without interaction, a platform whithers; and my experience, so far, has been comment oasises while scrolling through pages of desert.
Fair take.
I’ve got a static IP for Truenas now with an internal DNS entry pointing directly to it for smb and another DNS entry pointing to Traefik for the web UI. Annoying to have 2 names for it and was hoping to not have to, but this may be where/how things stay.
Not all. This is all internal. I got annoyed with with insecure warnings for all the internal stuff that runs on SSL and fell down the Traefik rabbit hole after watching TechnoTim’s video on the topic.
I’m not sure that’s right, in the routers section of the Traefik docs they say…
UDP routers can only target UDP services (and not HTTP or TCP services).
Feels possible, just not widely documented. I could be completely wrong, though.
My answer won’t be as popular, but it’ll definitely get the attention of the right people on the customer’s side: charge HANDSOMELY for issues caused due to customers using the systems outside of agreemed to or published best practices.