gastro ./ gastrointestinal tract
Peptic Ulcer Disease
An ulcer is defined as a breach in the mucosa of the alimentary tract, which extends through the muscularis mucosae into the submucosa or deeper. Although ulcers may occur anywhere in the alimentary tract, none are as prevalent as the peptic ulcers that occur in the duodenum and stomach. Acute gastric ulcers may also appear under conditions of severe systemic stress.
Peptic ulcers
Peptic ulcers are chronic , most often solitary, lesions that occur in any portion of the gastrointestinal tract exposed to the aggressive action of acid peptic juices. Peptic ulcers are usually solitary lesions less than 4 cm in diameter, located in the following sites, in order of decreasing frequency:
Duodenum, first portion
Stomach, usually antrum
At the gastroesophageal junction, in the setting of gastroesophageal reflux
Within the margins of a gastrojejunostromy
In the duodenum,stomach, or jejunum of patients with Zollinger-Ellison syndrome.
Within or adjacent to a Meckel diverticulum that contains ectopic gastric mucosa
In the United States, approximately 4 million people have peptic ulcers (duodenal and gasteric), and 350,000 new cases are diagnosed each year. Around 100,000 patients are hospitalized yearly , and about 3000 people die each year as a result of peptic ulcer disease. The lifetime likelihood of developing a peptic ulcer is about 10% for American men and 4% for women. Visit for Medical help
Peptic ulcers are remitting , relapsing lesions that are most often diagnosed in middle aged to older aged, but
This could maybe explain some of the emails I received, but not all of them
I received some responses to yesterday's post.
The first was from Lionel Dricot who reported that he, too,
has received emails for other Lionel Dricot's that lived near him.
He also stated that it may be a bug in Gmail where one person can register ?seanconner@gmail.com?;
someone else could register ?sean.conner@gmail.com?
but when receiving emails,
Gmail condenses the two addresses into one.
That's possible,
but I would suspect that would have been an issue caught early on.
I've had my Gmail account for twenty years now
.
and it's only been in the past few years that this has been an issue.
He also stated that people could just really be that bad with email addresses.
The second response has an explanation that is rather dire:
Hi, considering you've been shared on Hacker News, I'm afraid sooner or
later some script kiddie will start abusing your address just to annoy you.
I hope this will never happen ;) Thanks for sharing your blog, ave [sic] a nice
day, White_Rabbit
That could explain maybe some of the email I get,
which to me,
I consider spam that Gmail hasn't filtered yet.
But it doesn't explain emails sent to ?sean.conner@gmail.com? that are obviously not a ?Sean Conner,?
and yet definitely contains private information.
It also seems excessive to register a TikTok account or even an Instagram account.
And speaking of Tiktok,
I finally have an account name associated with the TikTok account,
so I have to wonder why ?mommakmiller? decided to use my Gmail account?
Perhaps they don't have an email account and need one to sign up for TikTok?
Perhaps they didn't want to use their real email account?
Perhaps they don't realize the danger in that?
]]>
How? How do people not know their own email addresses?
I'm still receiving emails from strangers who for some reason or another,
think their email address is ?seanconner@gmail.com?
(no, really, I get so many emails).
This time,
it's from someone who's TikTok account was accessed on a new device:
Hi xs,
We?re writing to inform you that we detected a login to your account from a new device.
When: 09/03 00:56 EDT
Device: iPhone 11
Near: Louisiana
If this was you, you can ignore this message.
If this wasn?t you, open the TikTok app and go to ?Settings and privacy? > ?Security and login? > ?Security alerts? and review unauthorized logins. If you?re unable to access your account, contact TikTok support.
You can also set up 2-step verification to secure your account by going to ?Security and login? > ?2-step verification?.
Learn more about 2-step verification
This is an automatically generated email.
Replies to this email address aren?t monitored.
This email was generated for xs
Privacy Policy
TikTok 5800 Bristol Pkwy, Culver City, CA 90230
It's not a phishing email as the raw message doesn't contain a link to ?login? to TikTok,
and the links that are in the email all point to the TikTok domain.
So I'm at a loss.
?xs? created a TikTok account,
using my email address ?
Why?
I don't know why this should surprise me any more,
but it still does.
I just ? why?
How?
What's the angle here?
I can't even contact anyone,
because TikTok send email from an address that isn't checked.
I don't know who ?xs? is,
nor do I have any way to contact ?xs? to inform them of their error.
Sigh.
]]>
The programmer's obsession with version numbers
It's yet another round of hand wringing about software versioning.
Woot!
Over the years,
I've found that semantic versioning works for me,
but only for code code that is to be used in larger projects,
like libraries,
modules,
or classes.
Yes,
a code base using semantic versioning doesn't always mean the code base follows semantic versioning to the degree that some would like
(like any bug fix should automatically update the major version number,
because bug fixes could break some code, somewhere).
But in my mind,
it signals intent,
which,
sans an extremely obnoxious and overly bureaucratic process,
is the best we can expect.
So for me,
the MAJOR.MINOR.PATCH of semantic versioning breaks down like this:
- MAJOR
- Some change in the code base was made; either a change in API behavior, removal of some portion of the API,
file format,
or otherwise any visible change (except for bug fixes) in how the code works.
Work will probably be required to update to this version of the library/module/class.
- MINOR
- Only additions to the API were made,
in a backward compatible way.
No work is expected,
unless you were already using a name used in the updated library.
- PATCH
- A bug fix.
The intent is for no work required to upgrade,
unless you were relying upon the buggy behavior,
or used a workaround that might now interfere with the library.
For applications,
I've found that semantic versioning doesn't work.
At least,
it doesn't work for me.
I've switched to either using a monotonically increasing number
(mod_blog is now at version 60?but given the five releases in just the past week because of a misplaced obsession with version numbers,
I might entirely stop with the version numbers?especially since I seem to be the only one using it)
or skip it entirely
(my Gemini server has no version number,
but it's had 322 commits over its five year life so far).
The worst form of versioning I've enountered is ?named versions.?
A ?named version? give no semantic information about the version and,
at least to me,
leads to confustion.
Is ?Bulldog? newer than ?Beagle??
Or is ?Bloodhound? the latest version?
Oh,
it's ?Berzoi? that's less than 20 minutes old.
Sheesh.
But if I had to apply ?semantic versioning? to an application,
I would like information about any breaking changes to either work flow or file formats.
To me,
an incompatable change to a file format,
or any change in workflow
(even a change in location of a menu item)
is a breaking change
(muscle memory is an incredible drug).
Hell,
even a change in color scheme is enough to possibly break my workflow
(I'm looking at you, Google Maps,
who changed the color of all the roads to the same color!
Why?
I liked the distinction between highways, major roads and minor roads.
Did you see a 0.001% increase in engagement for that change?
Did someone get promoted just because of that change?
Okay,
I'll stop ranting now).
]]>
How to run valgrind on a CGI program in C
There was still one bug left with mod_blog?it would crash with a memory corruption error
(thanks to checking in glibc when doing a POST.
I only found the bug because I was using the old web interface to make sure I had the right credentials when testing the PUT method.
How long had the bug existed?
At least six years?it's been seven sine I last used the web interface
(I checked).
It did not crash on the development server due to subtle differences between the operating system and versions of glibc being used.
But it is ultimately a memory corruption,
so the use of valgrind would be instrumental in finding the issue.
The problem is?it only manefests itself when doing a POST,
which means testing the program under a web server.
And a web server will pass information about the request to the CGI program through environment variables,
and any input comes in via stdin.
So just how do you run valgrind on a program meant to be run as a CGI program?
After some thought,
I figured out a way.
I need to capture the environment the CGI program runs under,
so I added the following bit of code to mod_blog to capture the environment:
extern char *envriron;
FILE *fp = fopen("/tmp/env.txt","w");
for (size_t i = 0 ; environ[i] != NULL ; i++)
fprintf(fp,"export %s\n",environ[i]);
fclose(fp);
I wasn't worried about error checking?this is temporary code anyway.
I then do a POST and I now have the environment variables in a file:
...
export GATEWAY_INTERFACE=CGI/1.1
export HTTP_ACCEPT=text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
export CONTENT_LENGTH=149
export CONTENT_TYPE=application/x-www-form-urlencoded
export REQUEST_METHOD=POST
...
The reason I added ?export? was to copy these environment variables to a shell script where I can then run valgrind and debug the situation:
...
export GATEWAY_INTERFACE=CGI/1.1
export HTTP_ACCEPT=text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,\*/\*\;q=0.8
export CONTENT_LENGTH=149
export CONTENT_TYPE=application/x-www-form-urlencoded
export REQUEST_METHOD=POST
...
valgrind $HOME/source/boston/src/main <r.stdin
Of course,
I had to escape some problematic characters like the asterisk or semicolon,
but there were only a few such characters and they could be done by hand.
And I had to create the input feed into stdin but that was easy enough.
From there,
it's straightforward?ish enough to resolve the issues.
]]>
Sigh
The previous bug fix was buggy.
And yes,
programming and deployments can always get this messy.
]]>
they may first become evident in young adult life. They often appear without obvious precipitating influences and may then after a periof of weeks to months of active disease, heal with or without therapy. Even with healing however, the propensity to develop peptic ulcers remains in part because of the propensity for recurrent infections with H.pylori. The male to female ration for duodenal ulcers is about 3:1 and for gasteric ulcers about 1.5 to 2:1. Women are most often affected at or after menopause. For unknown reasons, there has been a significant decrease in the prevalence of duodenal ulcers over the past decades but little change in the prevalence of gastric ulcers.
Peptic ulcers appear to be produced by an imbalance between the gastroduodenal mucosal defense mechanisms and the damaging forces. Gastric acid and pepsin are requisite for all peptic ulcerations. Hyperacidity is not a prerequisite because only a minority of patients with duodenal ulcers have hyperacidity, and it is even less common in those with gastric ulcers. Gasric ulceration can rapidily occur when mucosal defenses fall, however as when mucosal blood flow drops gastric emptying is delayed or epithelial restitution is impaired. Article Source: http://www.articlemap.com For More information visit www.medicalhealthcenter.net
|
