1

Hey all, just ran into this this morning, I was replying to a comment and it showed up at the same level as the comment I was replying to until a refresh. I'll see if I can reproduce it for screenshots in a bit. Has anyone else noticed this or is it just me so far?

[-] thegreekgeek@midwest.social 1 points 3 days ago

I can too, which is what gets me. Honestly after I think it might boil down to how far removed your provider is from directly getting the number from the FCC(or how trigger happy the entity they're getting the number from). Also possibly if it's considered a landline or mobile number, it looks like those are distributed differently.

[-] thegreekgeek@midwest.social 4 points 4 days ago

Sort of? It looks like this is unique to SMS over VOIP. Which don't get me wrong, it's still fucking stupid. But maybe, just maybe there's a middle ground between getting inundated in robocallers trying to reach us about our cars extended warranty and not being able to send the word Scunthorpe over SMS.

[-] thegreekgeek@midwest.social 22 points 2 weeks ago* (last edited 2 weeks ago)

The tl;dr is that the play version of termux has been lagging behind the master github branch because of Google's fuck fuck games with Android permissions. Now it's been updated, but effectively neutered.

Basically, PlayStore termux-app v0.120 release is functionally equivalent to v0.108

1
submitted 3 weeks ago* (last edited 3 weeks ago) by thegreekgeek@midwest.social to c/syncforlemmy@lemmy.world

It happened recently, the share function doesn't seem to be pulling the URL from the page.

Edit: this is with Firefox mobile beta 127.0b9 as my default browser

[-] thegreekgeek@midwest.social 24 points 1 month ago

Oh that series is so much fun! I need to read those books again. Another good one is Scott Meyer's Magic 2.0 series. Basically a random dude finds the rules.ini file for the universe hiding out on the internet and ends up using it to travel back back to Arthurian England to live openly as a Wizard. Except he's not the first one with that idea...

[-] thegreekgeek@midwest.social 30 points 1 month ago

Oh fuck I forgot about that troglodyte. My parents were Limbaugh losers back in the day. Now they're anti-vaxxers.

[-] thegreekgeek@midwest.social 23 points 3 months ago* (last edited 3 months ago)

Looks like someone on reddit was asking a few years ago, hopefully this points you in the right direction.

EDIT: Just got to the bottom of the thread, found THIS.

[-] thegreekgeek@midwest.social 25 points 3 months ago

Defo gonna try lol

[-] thegreekgeek@midwest.social 31 points 3 months ago

I saw a terminal app a few weeks ago that had AI INTEGRATION of all things.

5
submitted 3 months ago* (last edited 3 months ago) by thegreekgeek@midwest.social to c/homeassistant@lemmy.world

Hey all! I've been chewing on this problem for a bit and I've hit a wall, I'm hoping someone here can point me in the right direction.

I have an auto entities card populating a series of mushroom chips on the top of my dashboard for stuff like lights on, available updates, and open doors.

The thing is, some of the doors that have sensors on them are open by default, and as a result the chips are there all the time.

Ideally I'd like to have seperate auto entities entries for each group, default open and default closed, but I'd like to keep them in the same card as everything else(they're sorted by time triggered); and I can't for the life of me figure out how to filter out specific entities from a single entry in the include filter. I can exclude something from the whole card, but I haven't found anything that would allow me to just show certain closed doors or certain open ones.

Hopefully this made sense! I appreciate any ideas you have.

EDIT: So I finally got it figured out without futzing with my setup too much, sorry @borebore, I didn't end up going with the template sensor. I ended up finding a python script that allows you to inject custom attributes, so I made an automation that anytime the "normally closed" doors updated their status it'd give them an "is_normally_open: true" attribute and filtered the auto entities chips off of that attribute.

Thanks everyone!

[-] thegreekgeek@midwest.social 34 points 3 months ago

It's Adam Osbourne, saved you a click.

1
submitted 3 months ago* (last edited 3 months ago) by thegreekgeek@midwest.social to c/syncforlemmy@lemmy.world

My first time encountering it, just scrolled to it like three times to check, anyone else having this issue?

Edit: ope, looks like I can't edit the title lol.

11
Anyone tried zenroad? (midwest.social)
submitted 4 months ago* (last edited 4 months ago) by thegreekgeek@midwest.social to c/android@lemdro.id

Hey all! I was looking for an Android Auto replacement app recently and came across Zenroad there's also an android build but it's not compatible with my device unfortunately. Has anyone had any experience with this app?

Edit: ope, just saw the sidebar. Apologies!

[-] thegreekgeek@midwest.social 22 points 5 months ago

Damn straight! I miss pebble. :(

23
Weird vase mode bulging (midwest.social)

Hey all, I just finished a run of Popandsicle's excellent vase mode ornaments and I noticed these weird bulges happening all over the prints. The last run in a different color was flawless so I'm not sure where to start. I couldn't find much on the issue with a bit of googling so I thought I'd check with you folks and see if you all had any insight.

I've calibrated my esteps and adjusted the resolution to be a bit easier on my printer (modified CR-10v2), and unfortunately my mainboard isn't capable of linear advance.

Filament is overture royal gold, layer width is 0.6, height is 0.2.

I appreciate the help!

[-] thegreekgeek@midwest.social 24 points 7 months ago

Yeah, that's fucking slick right there.

34

To be clear I know it's not well lol. I just wanted the community's thoughts on what I'm doing wrong. I'm using Overture Royal Gold on a modified CR-10v2 with a real V6. Model was sliced in cura with default low quality settings.

The filament I bought a few months ago but just broke it open yesterday. It's making some small popping noises every now and again but the seal didn't appear to be broken. It seems all right otherwise, if a little sticky on the roll. I had to move it out of my filament dryer to keep it from opening the lid because it was binding so much. That's what happened to the last tower, that failed mid print. Looks nice at least.

[-] thegreekgeek@midwest.social 29 points 7 months ago

I mean with the amounts in this thing you'd need to eat a server farm to get a lethal dose, the lethal concentration is 1800mg/kg. But after the first few you probably wouldnt want to anymore, it looks like it was used to treat bipolar disorder in the early 20th century.

view more: next ›

thegreekgeek

joined 1 year ago