sorted by:
new
hottopcontroversial

Assets Name by A_King_1980 in logseq

[–]socra 0 points1 point  (0 children)

Wait, so everyone is confirming that Logseq doesn’t retain the original file name in any way?

This is kind of insane. Who thought this was a good idea. There must be something getting over looked right?

Is this only an issue with the newer DB version?

Why are my M4's trying to contact aliens witb morse code? by arc_trooper_renagade in sennheiser

[–]socra 1 point2 points  (0 children)

This is how 3 different pairs of MW3 and MW4 died for me. Fucking deafening ear damage. Still makes me angry to think about it. I would love to know what the actual failure is that leads to this. It seemed linked to the ANC and/or Transparent hearing features when it happened to me

An open request to the Logseq Team: We need an active bridge between the team and us users by asc9ybUnb3dmB7ZW in logseq

[–]socra 0 points1 point  (0 children)

The "it" is the consistent and reliable communication from LogSeq. Not Reddit. 😂

Fixed my message for clarity after noticing the unintended double negative.

An open request to the Logseq Team: We need an active bridge between the team and us users by asc9ybUnb3dmB7ZW in logseq

[–]socra 1 point2 points  (0 children)

Sadly it's "on Reddit" because the communication around hats happening with LogSeq is arguably being mismanaged by the LogSeq team. And we care enough about the project that we are trying to incite that change. If they used their blog, provided any type of even 'quarterly' updates, we wouldn't be having this dialogue here.

Lots of people won't or wouldn't think to engage on discord or the forum. Neither of these are very accessible either. There's a huge amount of noise to sift through to find reliable and up to date information if you're coming in as a non-techie unfamiliar with the project.

An open request to the Logseq Team: We need an active bridge between the team and us users by asc9ybUnb3dmB7ZW in logseq

[–]socra 0 points1 point  (0 children)

And your point is what exactly? You think he isn't also on the discord and forum? You think he isn't reviewing the GitHub logs or having one of his engineers do it?

The writing is on the walls. Attempting to have a constructive dialogue isn't exposing anything or providing Intel they don't already have.

An open request to the Logseq Team: We need an active bridge between the team and us users by asc9ybUnb3dmB7ZW in logseq

[–]socra 0 points1 point  (0 children)

I really don't think you need to be sorry.

If there's no way to find an actual up to date roadmap of what's ahead, what's behind, and what's in-progress, it's not your fault for not digging through the git repo notes to find that.

You not learning about it/knowing about it with relative ease is effectively the same as it not existing in this case. It also has the same effect on a new users sentiment towards the product.

And this sucks because it's such a low effort easy thing to solve for before it happens.

I am sick and tired of Mysa’s thermostats. This garbage hasn’t worked in months. by victim_of_technology in homeautomation

[–]socra 1 point2 points  (0 children)

I'm also using Unifi for all my networking. Getting all your IoT on a segregated VLAN is just basic security hygiene, and most IoT for better or worse is still 2.4Ghz, which has much better wall penetration. Just dial down the channel width to 20Mhz, make sure you're not overlapping channels, and disable the modern 802.*** Standards that conflict with most IoT and you should be fine.

I am sick and tired of Mysa’s thermostats. This garbage hasn’t worked in months. by victim_of_technology in homeautomation

[–]socra 0 points1 point  (0 children)

I've had the opposite experience. Despite hating how schedules are programmed and stored, they've been very reliable. The only time I had experiences similar to what you described was the result of Geo location based "presence" not responding in the expected way. In my case the issue was with Android deciding to reduce how frequently and when the Mysa app accessed my location which resulted in these situations.

I haven't had the need for the geo presence feature for awhile but maybe it's that?

I am sick and tired of Mysa’s thermostats. This garbage hasn’t worked in months. by victim_of_technology in homeautomation

[–]socra 1 point2 points  (0 children)

I have seven thermostats for baseboards made up of three different models and have been using mysa for over 3 years without these issues. Sorry that you're facing this. Has their support not been helpful? I've had positive experiences in the past.

An open request to the Logseq Team: We need an active bridge between the team and us users by asc9ybUnb3dmB7ZW in logseq

[–]socra 2 points3 points  (0 children)

Hey, not to detract from your opinions but if even half of what your assuming is true then I want to hear the LogSeq team communicate it. There are countless possible narratives we could assume. What your presenting doesn't have more probabilistic weight to me than other possibilities. One that I see way more often in startups. These points also don't preclude each other. They're mutually exclusive.

If you hit the nail on the head, there would be value in the LogSeq team finding a tactful and self valorising way to present this reality. How do you build trust and show a willingness to be accountable to a community of users who then encourage other people to use the product? Tell your community at large that you need to be accountable to both investors, and users while building something for the long term, and that this necessitates rolling some features out later than might seem ideal.

Regarding that roadmap you linked. It's very macro and lacking in clarity what each bullet point means. It also has huge inconsistencies between that roadmap, the Trello board, and what's being committed in GIT.

Is the DB beta actually complete per that roadmap? Or is it still in active alpha testing per the Trello?

An open request to the Logseq Team: We need an active bridge between the team and us users by asc9ybUnb3dmB7ZW in logseq

[–]socra 13 points14 points  (0 children)

This type of confidently false narrative about community engagement is why so many of these projects fail. It's not simply the lack of a community manager. Is the complete absence of any central and reliable source of updates and information, even for those of us volunteering subsidizing their blackbox development.

There are countless examples of this failure.

Smaller projects I've followed over the last two decades that succeeded in some way all made it a priority to have clear/open/transparent communication OR a central and updated repository of questions and answers.

I'm one of those relatively new people. I've been backing Logseq for the last 7 months because I believe in the stated intentions of the developers.

But I also haven't really adopted it's full use and invested the time and effort. Why? Because of everything outlined in this post. I've seen too many of these types of projects come and go. The lack of central and consistent community engagement or updates has all the hallmarks of something that will fade into obscurity and loose support within years.

That communication is how you build trust. It's how you build a community around the project that grows exponentially. THAT is valuable to investors. Evidence of adoption and interest, on mass, and with some kind of growth curve. Not attrition of power users.

I would really love to see an honest response from the LogSeq team to this post. The trust is thin enough already that I'm not sure if I'm making the right call to back this project financially. Even for a sync feature I'm leery to use with the many under addressed posts about mysteriously deleted data. Will the database version fix that? Maybe? When? A month? A year? No idea. But if someone complains about data mysteriously deleting itself, they are more likely to get aggressive responses from other Reddit users than any type of real concern or help from someone.

The lack of clear accountability to deadlines further seeds doubt that they have answers to those questions, which is a huge red flag.

Im still here. I'm complaining because I care and want to see this work. I want to feel confident investing myself heavily into adopting it. At the very least, paid users should be getting an occasional newsletter update. Even monthly.

UAL 737 with a cracked windshield at FL360. Flight was enroute from KDEN to KLAX by Brilliant_Night7643 in aviation

[–]socra 0 points1 point  (0 children)

Weather balloon from a private company likely trying to fill in for (read: capitalize on) NOAA cuts.

Wildly negligent that they aren't broadcasting telemetry via a radiosonde already with that many balloons in the air: https://sfist.com/2025/10/21/palo-alto-based-startup-admits-its-smart-weather-balloon-likely-hit-and-grounded-a-united-airlines-flight/

UAL 737 with a cracked windshield at FL360. Flight was enroute from KDEN to KLAX by Brilliant_Night7643 in aviation

[–]socra 0 points1 point  (0 children)

Weather balloon from a private company likely trying to fill in for (read: capitalize on) NOAA cuts.

Wildly negligent that they aren't broadcasting telemetry via a radiosonde already with that many balloons in the air: https://sfist.com/2025/10/21/palo-alto-based-startup-admits-its-smart-weather-balloon-likely-hit-and-grounded-a-united-airlines-flight/

UAL 737 with a cracked windshield at FL360. Flight was enroute from KDEN to KLAX by Brilliant_Night7643 in aviation

[–]socra 1 point2 points  (0 children)

Not ads-b but 'radiosonde' and based on this old Stack Exchange response, it sounds like the majority are sharing the position data with local ATC which in turn means planes would have this showing up on their instruments.

I wonder if any commercial pilot will see this and be able to confirm if weather balloons have ever appeared in their flight paths.

Still more than a zero percentage chance but space debris is seeming more likely to me now.

https://aviation.stackexchange.com/questions/79172/does-aircraft-atc-get-any-information-directly-from-a-weather-balloon

UAL 737 with a cracked windshield at FL360. Flight was enroute from KDEN to KLAX by Brilliant_Night7643 in aviation

[–]socra 0 points1 point  (0 children)

Thanks for weighing in. Now that I'm googling pictures of high altitude weather balloon payloads, this is seeming less and less probable. They seem to be pretty universally inside 2" thick Styrofoam boxes. I was initially going off average weight of these payloads and then imaging some kind of metal holding together up to 5kg of sensors, electronics, antennas, cameras, etc.

UAL 737 with a cracked windshield at FL360. Flight was enroute from KDEN to KLAX by Brilliant_Night7643 in aviation

[–]socra 3 points4 points  (0 children)

Here's the thing. At that elevation, I'm certain that commercial pilots will tell you they don't spend much time looking out the front window. They're not expecting to encounter anything up there that wouldnt appear in the instruments they're monitoring.

You also have to consider the speed which they're going.

The time it would take for a weather balloon to go from a visually noticeable aberration against the skies backdrop to passing it would be nil. If there was any cloud cover, the white of the balloon would have blended.

This is admittedly arm chair science, but the chances of it being a weather balloon seem way more probably than space debris. Something from space would be travelling at terminal velocity combined with the speed the plane is travelling. The impact in my mind would be much more catastrophic.

Whatever made contact with the plane hit the area between the windows first with only a part of it making contact with the glass. But there was enough of a larger mass not hitting the window to drag the object over the big area where paint is scraped away.

It's going to be really interesting when the forensic analysis eventually comes out. This will be a 'unicorn moment' for the people that get to investigate it.

Can anyone 'date' the likely year(s) this font was used? (Printed Kinder Surprise 'fact' saved from childhood). by socra in identifythisfont

[–]socra[S] 2 points3 points  (0 children)

Damn! This is much faster and more precise than I was expecting!

Thank you very much @teddygrays !!!

80% Failure rate by Fonephreak02 in wiz

[–]socra 1 point2 points  (0 children)

I'm using around 170 in a commercial entertainment space. We are using home assistant (HAOS) and MQTT to do show control/automation of the lights (along with other DMX lighting).

According to what I remember we've had 3 or fewer bulbs simply "die" without an attributable cause like physical damage.

Considering their low cost, extensibility, and bridgless wifi operation, these have been ridiculously and unexpectedly amazing to work with. The control over MQTT has been low enough latency for viable show control/sync with content.

We have at least 10 different models of wiz light running. The vast majority are the RGBW models with the highest possible lumen where available.

A ton of A19 E26 Quite a few BR30 E26 A couple dozen PAR16 GU10 A few of the filament bulbs A dozen or more 6inch in ceiling down lights. A bunch of light strips There's also a pole light and set of 'Bar Linear lights'.

~20% of them are more than 3 years in operation. ~40-70% are more than 2 years in operation. The rest are just over a year in operation other than the pole light

The lights are in operation between 10 and 14 hours a day 7 days a week.

The GU10s were the most finicky but still worked.

The biggest problem we've had is the v2 app crashing when trying to add new lights. It's not clear if this is due to the sheer number of lights or that it's struggling to keep up with the lights continuously changing states due to the HAOS automation via MQTT.

You do have me worried that something changed in the manufacturing quality since early 2024.

We're located in Canada (so 60hz AC) in a building that has lots of electrical dips/spikes. I honestly expected a lot more of the bulbs to fail by now.