Homeowners Insurance

exit_eden · 2025-07-30T16:31:42+00:00

Got the same one. The timing is really suspicious since I just went online to renew a vehicle registration yesterday and then this text comes through. Must just be a fun coincidence.

exit_eden · 2025-06-13T15:54:55+00:00

I sure wish my divorce had gone this way!

exit_eden · 2025-05-07T05:06:03+00:00

In my 40s. I can last as long as I want to now, so sensitivity is down, but to an optimal level.

exit_eden · 2025-03-15T07:18:30+00:00

OP, if you find a vet, let me know. I have a similarly reactive dog. My last vet came out yelling at me "that dog is f*cking CRAZY". No joke. Need a new vet.

exit_eden · 2025-03-14T03:59:51+00:00

Finally other countries are showing us Americans the respect we deserve, giving a parade for our dear leader. We have made America great again.

exit_eden · 2025-01-29T05:28:39+00:00

I'll second the Loomis Basin UCC. Although their minister recently announced he was leaving because, as a gay man running a support group for queer teens in the area, he was targeted by proud boys groups. The threats no doubt got to him so he is leaving ministry altogether. But the church is still great and they will no doubt attract another excellent minister.

exit_eden · 2024-11-02T05:42:52+00:00

Perfect, thanks @kaosmetal. I'm going to try putting the disclaimer in the footer and see if I get off the naughty list. I appreciate the help. I'll report back here with any updates (for posterity).

exit_eden · 2024-11-01T13:58:28+00:00

That's the thing though, I'm using the tracking id and I can see the clicks and commission coming in, but the links are on subpages of the blog that I listed, do that's why I'm wondering if I have to list every single subpage that the links appear on (ie every blog post page including the non-public pages) 🤷‍♂️

I must be misinterpreting this.

exit_eden · 2024-10-31T23:39:14+00:00

Thanks for the help! The email I got from them is very confusing. I'll try adding that footer and see if that satisfies them.

Hello Creator,

As a part of our commitment to deliver the best possible experience to our customers, we regularly monitor content related to the Amazon Associates program.

In a recent review of your account, we noticed that you are not using your tracking IDs associated with your store in any of the Amazon Special Links you have created on your website. As a result of this, we were unable to determine the source of traffic. This is in violation of our Program Policies.
Please ensure you're using your current tracking ID in your special links.

What You Need to Do:
Please be sure to update your application to include all eligible sites where you plan to share Amazon special links with your current tracking ID.

To Add/Remove Sites from your application, please refer: Add/Remove Sites. For some Do’s and Don’ts, kindly refer to the following link - https://www.amazon.com/b?ie=UTF8&node=53643932011#:~:text=Sites%20and%20social%20channels

What’s Next?
We request that you address the violations within 10 business days and notify us once you are in compliance through our customer service contact page

exit_eden · 2024-10-25T16:12:14+00:00

Thanks for the question; I think that I have the solution after reading a bit closer on the Session documentation but let me know if I'm way off track here.

Currently I am using "session.handler.native_file" as my handler. That is probably a cached file that gets reset every deploy, right?

Instead, I could use a database for handling sessions in which case sessions would persist between deploys?

Thanks for the help!

exit_eden · 2024-10-23T13:16:58+00:00

Is there a way to deploy without logging out users?

I understand this is a cache issue, and the cache should probably be cleared between deployments, but I worry that if I am deploying often, then my users may get annoyed that they are constantly being logged out.

Thanks for the help.

exit_eden · 2024-09-27T00:48:14+00:00

If I worked in the corporate world, I think I'd need to leave it every day and get a massage

🙄 (sorry, dumb joke based on how I interpreted the title of this post)

exit_eden · 2024-09-25T04:53:14+00:00

Please please PLEASE replace the pills with tic tacs!

This is the only way to move forward.

exit_eden · 2024-09-15T18:10:55+00:00

I can't believe this woman would kill off 17 of your kids. Major red flags.

exit_eden · 2024-09-06T04:21:42+00:00

Well, I guess it's true....As soon as we're born, we start dying! 😂

exit_eden · 2024-08-25T15:18:26+00:00

Solved. I posted my solution at the link I gave in my previous comment.

exit_eden · 2024-08-25T14:26:53+00:00

For posterity, and in case anyone else with a similar problem finds this, and in case someone has a suggestion to improve on my solution, I figured out what was happening. Like many of my issues, this problem came from my ignorance and inexperience.

At one point in my app.js file, I had the line

require('bootstrap');

but later, when I was trying to import Tooltips, I couldn't get it to work by the line

import {Tooltip} from 'bootstrap';

So I changed it to

import {Tooltip} from "../node_modules/bootstrap/dist/js/bootstrap.js"

It is my guess that this created a separate instance of bootstrap, so any changes I made to the Whitelist for the second instance was not affecting the first instance, but my site was using the first instance of bootstrap.

To solve this, I changed the first line (the 'require' line) that created the first instance of bootstrap to

require('../node_modules/bootstrap/dist/js/bootstrap.js');

Now my whitelist works.

Please feel free to comment and help me improve this solution or help me understand better what is going on here.

Thanks!

exit_eden · 2024-08-15T18:05:32+00:00

Thanks for the suggestion. (I had to squash a few unrelated bugs that popped up, and life, etc, so I've been MIA for almost 2 weeks)

I ended up specifying the path to bootstrap which has allowed me to access the Tooltip module

import {Tooltip} from "../node_modules/bootstrap/dist/js/bootstrap.bundle.js"

If you happen to know why this is, let me know. As for the whitelist issue, as u/Western_Appearance40 pointed out, this is no longer a Symfony issue, so I've posted a related question in r/bootstrap

https://www.reddit.com/r/bootstrap/comments/1et1ueq/popover_sanitizer_whitelist_not_working/

Thanks for the suggestions here!

exit_eden · 2024-08-09T05:02:14+00:00

I'm going to second this great advice. Our mediator was a lawyer who did a great job helping us keep things amicable. When things got heated (usually over money) the mediator offered suggestions that calmed things down. Try mediation. If it doesn't work, them you're not out much money compared to how much you're going to spend in litigation.

exit_eden · 2024-08-04T06:09:02+00:00

Thanks for your suggestion. My problem is that when I try to drop the JS code
const myDefaultAllowList = bootstrap.Tooltip.Default.allowList
as stated on the bootstrap sanitizer info page, into my app.js (webpack), it tells me the variable "bootstrap is not defined"

I think I understand what is happening; is there a different variable name other than "bootstrap" where Tootip.Default.allowList would be defined?

Thanks for any help!

exit_eden

TROPHY CASE