remotelove

joined 3 years ago
MODERATOR OF
196
[–] remotelove@lemmy.ca 4 points 10 hours ago* (last edited 10 hours ago) (1 children)

I am sure there are a ton of factors involved. I am also sure that there is a lot of financial incentives to publish positive studies.

There is a huge caveat to posting a study to counter your stats above since you technically aren't wrong. "Typically" can mean many different things, but here, it can also fit within published data.

https://pmc.ncbi.nlm.nih.gov/articles/PMC1125407/

Most articles I found usually point to roughly the same numbers as that study, but there is a lot of variation in how those numbers are presented. (Even that study initially presents stats in a way that is confusing: A percentage of a percentage of a percentage, over time.)

My point is that it's one of those stats that is super easy view as "really good" or simultaneously "exceptionally bad". IMHO, I still think it's crazy that we can even do transplants at all.

Edit: I believe everyone should at least get a chance to live a bit longer, but it sucks that it comes at extreme cost. The procedures are extremely expensive and a person could potentially be put on expensive anti-rejection drugs for the remainder of their life. Add in all the follow-up appointments and occasional hiccups in recovery (adding even more cost) a person is likely going to die broke and be put through even more stress that is a very real danger to health anyway.

[–] remotelove@lemmy.ca 2 points 2 days ago* (last edited 2 days ago)

Those drones are still very inaccurate compared to other weapons that we use today and are basically just terror weapons. It is an automated killing machine, sure. It doesn't target anything other than a coordinate.

It's the decision by a machine to target something specific that is the moral conundrum. If you give a machine the ability to "decide" to kill one person over another, there isn't anyone to blame for the death. There is a ton of randomness introduced into neutral networks (AI) and any decisions are non-deterministic in nature. You can jam in as many guardrails as you want, but if the ultimate decision is to kill or not to kill, the guardrails do not matter. This spawns a ton of questions about giving machines the intelligence to kill. Even though there is randomness in any conflict, we can get away with calling it "collateral damage".

If a machine decides that a book looks like a gun and hoses a classroom of 5 year olds, there isn't really any accountability if the machine was approved by law. Again, there isn't anyone to blame, which is a huge part of how humanity works, unfortunately. (Side thought: This would get even more complicated if said machine was supposed to fill the role of a protector or guardian.)

Even with the most complex weapons today, they are just following specific directions to hit a coordinate at a specific time. There isn't any real thought behind it even if it is extremely accurate. Once the trigger is pulled, weapon go to destination and the trigger person is responsible.

Edit: I made a fuck ton of edits to add clarification. Sorry if you were an unfortunate recipient of a draft.

[–] remotelove@lemmy.ca 2 points 2 days ago

Used to watch him on the Today show on a black and white TV when I was a kid. We aren't that old, TBH.

[–] remotelove@lemmy.ca 2 points 2 days ago (1 children)

Tilt the head in the left picture forward a bit? You could probably get alignment on the face holes, maybe?

The ears could be moved and the new holes could be purely cosmetic. That seems more in-line with the form-over-function theme we seem to have going on here.

Seriously, I do think you are correct but it also doesn't take much to throw perspective off with different cameras or lenses.

[–] remotelove@lemmy.ca 4 points 4 days ago (1 children)

Just the other 60% or it.

[–] remotelove@lemmy.ca 5 points 4 days ago

Double-posting means two good weeks in a row. Sweet.

[–] remotelove@lemmy.ca 1 points 5 days ago

Highly likely. However, it's also just as likely that this is an inexperienced "researcher" or there is poor translation in-play.

There is a possibility that this is an attempt at (poor) social engineering and an attempt to trick an admin into performing actions to start a real compromise. (Extortion is also a common path here as well.)

I have been dealing with this kinda shit for decades now, unfortunately.

[–] remotelove@lemmy.ca 2 points 5 days ago* (last edited 5 days ago) (2 children)

This is an interesting vulnerability notification and what is with that spoiler tag? The wording and/or bad translation negates just about any sense of urgency.

Can you clarify your wording on 'hosting a botnet'? That can be interpreted a few ways. There are a few ways a host can communicate to network of bots and I find it highly unlikely that you would see that traffic from the open Internet. Unless you were on the server yourself and you saw evidence of malicious code, it's generally difficult to determine what a host is/isn't infected with.

A public notification is likely not the best avenue for a notification. Exploring private methods to contact an admin is always a better path, even if you believe the channel is compromised.

TBH, this post is more of a red flag than anything else.

[–] remotelove@lemmy.ca 1 points 1 week ago

I certainly wouldn't say it was incompetent and there is a good set of data points. Given the nature of what the study is attempting to correlate, not explaining what limitations were taken into account is a a significant limitation, IMHO. It is called out that there are limitations, but that it is essentially just a short footnote. (The full paper does a better job of calling out other studies and some contradictions.)

This referenced study found the opposite and had a no (or weaker correlation) to cancer associated with SSBs: Khairan P, et al. Sugary drink consumption and the subsequent risk of gastric cancer: Khairan P, et al. Sugary drink consumption and the subsequent risk of gastric cancer: The Japan Public Health Center-based Prospective Study. Eur J Clin Nutr 2023;77:218-25.

Without doing a comparative analysis of the studies, which would be interesting, I have open questions about what the key differences were. My first guess (without calling either study "wrong") is that maybe risk factors were calculated differently?

On the darker side, there is motivation for keying-in on a specific correlation and that cannot be ignored either. (Past grants, groups requesting the study, etc.) The original paper also sets itself up to be a marketing call-out for artificially sweetened beverages, unfortunately. (I am not saying that is the intent, but the wording aligns exactly with what vitamin water-type company would want to see. It made for a good Lemmy post title, at a minimum.)

At the end of the day, they stated what they were looking for and presented what seems to be a clean analysis of that data. The limitations that were presented have the potential to be significant, however.

[–] remotelove@lemmy.ca 3 points 1 week ago

"War is just a racket. A racket is best described, I believe, as something that is not what it seems to the majority of people. Only a small 'inside' group knows what it is about. It is conducted for the benefit of the very few, at the expense of the masses." -Major General Smedley D. Butler.

[–] remotelove@lemmy.ca 1 points 1 week ago (2 children)

So my chance of developing gastric cancer doubles to 1.8% chance over my lifetime if I drink sugar-beverages every day.. (This math wasn't sponsored by a cancer testing company.)

After you actually get the the study, there wasn't any mention of other associated lifestyle behaviors that may contribute to the risk of gastric cancers. What sticks out to me is that people drinking one or more sugar-packed beverages per day likely have additional diet or lifestyle concerns.

It's not that I think the number crunching for the study was wrong or that the sample sizes were too small, it's just that it was extremely focused on making a correlation for the sake of making a correlation.

 

Hindsight is 20/20 and I realize this probably wasn't the best idea to begin with....

(Scott Kirkland, if you were wondering..)

 

Bug Report

If I make a comment on a post, it will not show for at least an hour. Clicking on my comment in my history does not show the comment on the post. (Editing a post or participating in conversations is extremely difficult.)

Replies to that comment will show that there is a reply "waiting", but the reply will not unroll in my post history, nor is it visible in the post thread.

Steps to reproduce:

  1. Make a comment
  2. Attempt to navigate to comment
  3. Cannot see comment on post.

Device Information

  • App Version: 1.0.427 (427)
  • Platform: android
  • OS Version: CP1A.260405.005

Modified Settings

The following settings have been changed from defaults:

  • isNotificationEnabled: 1 (default: 0)
  • alwaysShowInstance: true (default: false)
  • shouldShowPageNumbers: true (default: false)
  • commentTextStyle: bodyMedium (default: bodyLarge)
  • enableCommentNavigator: true (default: false)
  • showFullVotes: true (default: false)
  • shouldAlwaysDisplayAvatars: true (default: false)
  • shouldHighlightNewComments: false (default: true)
  • defaultPostSort: New (default: Active)
  • nsfwView: Hide (default: Blur)
  • applyNsfwInCommunities: false (default: true)
  • cardType: list (default: card)
  • shouldResolveOpenGraph: false (default: true)
  • imageDomainRewrites: {} (default: {})
 

(I guess this is a 7mo update too? https://lemmy.ca/post/53008395)

Running and breathing control is a topic repeated ad nauseam on the interwebs, but is probably worth a rehash as new techniques are discovered or newer runners run into issues. (I still consider myself a new runner, as I still have not reached what I would consider to be an "acceptable" or consistent pace for anything over a casual 5k.)

My biggest limiter with my running is breathing. While nasal issues are absolutely in-play for me (severely deviated septum; surgery this week), I have been able to inch my way up to between 4-6 miles with a regular running schedule, strict recovery schedule and of course, pushing myself consistently and safely. My "running out of air" is always the hard wall I hit, head first.

The muscle burn has always been easy for me to push through, but if I start to hold my running/heartrate even a hair over 140bpm I will crash fairly quick (10-15mins), "run out of air" and have to stop before my current target time of 45 mins.

I suspect my blood pressure meds may be in play as well, capping my heart rate to a degree and limiting O2 uptake. I am going to talk with my Dr. about that as I may be to a point soon that I don't need them. I have already gone through two medication "downgrades" and have stopped one completely under supervision, of course.

Most of my running is treadmill, mostly because I love the consistency at a chill 10min/mi pace. Once a week, I will hit the track and practice at my target marathon pace of 8:30min/mi, but that is essentially just glorified sprints, as I can only handle .25 miles at a time as my heartrate peaks fairy quick, for obvious reasons. (Run faster, heart more beat faster.)

Casual track running will push my breathing harder, but does not seem to peak my heart rate as fast, which is super weird. When spring started and I hit the track again this year, I was gasping for air at an 11min pace and my heartrate wasn't a beat over 135. Talk about a demotivating experience. I am recovering my track pace again slowly and it's taking more time than I anticipated. (I can still run like a champ on the treadmill though, so it's a good morale boost.)

Do you specifically train for breathing in your exercise of choice? Do you go so far as to allocate an entire training day to just breathing or work it into your routine normally?

I know most of the basics like belly breathing, in one/out two and all the variations, coordinated breathing with pace, etc. I am still settling into, and experimenting with, different techniques as my pace and distance increases. However, feel free to rehash anything as getting different perspectives and starting discussion is the ultimate goal of this post.

6
submitted 4 months ago* (last edited 4 months ago) by remotelove@lemmy.ca to c/lemmyconnect@lemmy.ca
 

Bug Report

Describe the issue:

  1. The text selector is sticky again during comment or edit
  2. Some comment replies do not unroll/expand in profile history.
  3. Not all comments load.
  4. My new comments don't always load until after app reload in profile history.
  5. Votes aren't updated until after app restart. (In profile history)
  6. Strange loading behavior/broken search for piefed instances.
  7. Text selector is un-broken editing this post sometimes.
  8. (Maybe not a bug) I can't sort by new in Connect community.

There are plenty more, and they all are mostly tiny things. A button might not work, comment replies won't unroll, etc. "Major" functions work, but everything around the edges needs polish.

The text selector one is absolute torture.


Device Information

  • App Version: 1.0.423 (423)
  • Platform: android
  • OS Version: CP1A.260405.005

Modified Settings

The following settings have been changed from defaults:

  • isNotificationEnabled: 1 (default: 0)
  • alwaysShowInstance: true (default: false)
  • shouldShowPageNumbers: true (default: false)
  • commentTextStyle: bodyMedium (default: bodyLarge)
  • enableCommentNavigator: true (default: false)
  • showFullVotes: true (default: false)
  • shouldAlwaysDisplayAvatars: true (default: false)
  • shouldHighlightNewComments: false (default: true)
  • defaultPostSort: New (default: Active)
  • nsfwView: Hide (default: Blur)
  • applyNsfwInCommunities: false (default: true)
  • cardType: list (default: card)
  • shouldResolveOpenGraph: false (default: true)
  • imageDomainRewrites: {} (default: {})
 

Bug Report

Describe the issue: NSFW blur/hide/show/etc setting will not save.

Steps to reproduce:

  1. Change NSFW Setting
  2. Scroll up/down or back out of settings
  3. NSFW Setting reverts to Hide

Device Information

  • App Version: 1.0.403 (403)
  • Platform: android
  • OS Version: BP4A.260105.004.E1

Modified Settings

The following settings have been changed from defaults:

  • isNotificationEnabled: 1 (default: 0)
  • isMarkdownEditorEnabled: false (default: true)
  • alwaysShowInstance: true (default: false)
  • shouldShowPageNumbers: true (default: false)
  • commentTextStyle: bodyMedium (default: bodyLarge)
  • enableCommentNavigator: true (default: false)
  • shouldAlwaysDisplayAvatars: true (default: false)
  • shouldHighlightNewComments: false (default: true)
  • defaultPostSort: New (default: Active)
  • nsfwView: Hide (default: Blur)
  • applyNsfwInCommunities: false (default: true)
  • cardType: list (default: card)
  • shouldResolveOpenGraph: false (default: true)
  • imageDomainRewrites: {} (default: {})
 

Bug Report

Describe the issue: Images may be assigned different IDs on page reloads resulting in duplicate cache items. (See attached image: Not sure if actually duplicate files or if cached files are soft linked to each other.)

Steps to reproduce:

  1. Clear cache
  2. Reload same feed or page multiple times

Device Information

  • App Version: 1.0.332 (332)
  • Platform: android
  • OS Version: BP3A.251105.015
  • Notice: Using legacy Shared Preferences

Modified Settings

The following settings have been changed from defaults:

  • isNotificationEnabled: 1 (default: 0)
  • alwaysShowInstance: true (default: false)
  • shouldShowPageNumbers: true (default: false)
  • showFullVotes: true (default: false)
  • defaultPostSort: New (default: Active)
  • nsfwView: hide (default: blur)
  • cardType: list (default: card)
  • maxCacheSizeGB: 5 (default: 2)

6
submitted 8 months ago* (last edited 8 months ago) by remotelove@lemmy.ca to c/lemmyconnect@lemmy.ca
 

Bug Report

Describe the issue: Just feed scrolling lag. I noticed it this time after page 20, with about 1Gb in process memory. (It seems to take a bit more scrolling now to see issues.)

Steps to reproduce:

  1. Have no life
  2. Leverage online media as a form of social acceptance
  3. Keep doom scrolling.

Device Information

  • App Version: 1.0.319 (319)
  • Platform: android
  • OS Version: BP3A.251105.015

Modified Settings

The following settings have been changed from defaults:

  • isNotificationEnabled: 1 (default: 0)
  • alwaysShowInstance: true (default: false)
  • shouldShowPageNumbers: true (default: false)
  • showFullVotes: true (default: false)
  • defaultPostSort: New (default: Active)
  • nsfwView: hide (default: blur)
  • cardType: list (default: card)
  • maxCacheSizeGB: 5 (default: 2)
 

Bug Report

Describe the issue: Click thumbnail for external link

Steps to reproduce:

  1. click all the post links!

Device Information

  • App Version: 1.0.318 (318)
  • Platform: android
  • OS Version: BP3A.251105.015

Modified Settings

The following settings have been changed from defaults:

  • isNotificationEnabled: 1 (default: 0)
  • alwaysShowInstance: true (default: false)
  • shouldPreloadImages: false (default: true)
  • shouldShowPageNumbers: true (default: false)
  • showFullVotes: true (default: false)
  • defaultPostSort: New (default: Active)
  • nsfwView: hide (default: blur)
  • cardType: list (default: card)
  • maxCacheSizeGB: 5 (default: 2)

 

Bug Report

Describe the issue: Lemmy doom scrolling gets super laggy over 400mb memory usage. App ram usage is estimated as I can only see temporary app cache through Android dev settings when the app gets kicked into the background. Memory usage will mostly self-clear, but it takes a bit.

Steps to reproduce:

  1. Doom scrolling FTW!

Device Information

  • App Version: 1.0.316 (316)
  • Platform: android
  • OS Version: BP3A.251105.015

Modified Settings

The following settings have been changed from defaults:

  • isNotificationEnabled: 1 (default: 0)
  • alwaysShowInstance: true (default: false)
  • shouldPreloadImages: false (default: true)
  • shouldShowPageNumbers: true (default: false)
  • showFullVotes: true (default: false)
  • defaultPostSort: New (default: Active)
  • nsfwView: hide (default: blur)
  • cardType: list (default: card)
  • maxCacheSizeGB: 5 (default: 2)

(Recommend moving nsfwView preference out of a public bug report. It's not a huge issue, but it could be a private setting for some people.)

 

My background: Long time IT security engineer here that can code when I need. For dev experience, I have worked with various languages over the years like assembly, C/C++, js, typescript, PERL, python, etc. When needed, I can hack out a specialized tool but I am absolutely not a professional developer.

My ask: I just want a simple web framework that I don't need to think about too much. There are a few ideas I have regarding security analyst workflow in a SIEM-type of environment and need a way to code simple tools as basic snap-ins to a central analysis console.

The ELK stack serves a inspiration (specifically Kibana). However, there is so much more I want to build into an security specific analysis console and building it one snap-in at a time seems manageable over time.

What is the current flavor of the day regarding Web app dev frameworks that might function how I want? What frameworks would be compatible with a broad audience over a long period of time? (I never liked open source applications that use super niche libraries or frameworks that become obsolete and stale after a few months.)

I hope I was able to describe clearly enough what I am looking for. I would google around for ideas, but I simply don't know the correct questions to ask about this kind of thing until I get more up-to-speed.

 

I turned off "Preload Images" and my feed hasn't hung since. There is still a tiny bit of wait time while the next group of posts gets cached in the feed (maybe < 1 second) and this is usually when post pre-loading would fail and hang the feed completely.

If for whatever reason, if an image can't be preloaded it'll hang the feed? Maybe if a post gets deleted on one instance and, because fediverse, it may still be listed by my home instance? A failed cross-instance image load does sound like an interesting theory for root cause.

 
  1. (Regression, I think.) Strike through markdown broken when used in combination with exclamation point (maybe with other special characters too?) Also affects large blocks text that is marked with a strike through

~~Strike~~

~~Strike! ~~

  1. Cannot select text from comment that you are replying to

  2. Selecting text on your comment is appended with multiple spaces if there is no punctuation.

  • to reproduce: create post or reply, press and hold the last word of the sentence with no ending punctuation
  1. Text selection can become "sticky". (Unknown cause) Moving cursor around on a comment in progress results in the text selection bar that cannot be turned off. Connect restart is required.

  2. Post cache is not always refreshed after edit. Requires Connect restart to see changes made to a post. (Post text is where the caching issue is, not generally comments.)

view more: next ›