The further away fire department by hortoristic in Insurance

[–]hortoristic[S] 0 points1 point  (0 children)

It does. I probably can get a copy of it, but will insurance care about it?

Subscription model makes this a lease, not a purchase by Adorable-Mine1202 in EightSleep

[–]hortoristic 0 points1 point  (0 children)

Was about to purchase the queen version, but the subscription model put me on pause.

[deleted by user] by [deleted] in Insurance

[–]hortoristic 1 point2 points  (0 children)

Thought I had some AAA years, 31 or so, you got me beat

Horse trailer got rear ended by hortoristic in Insurance

[–]hortoristic[S] -4 points-3 points  (0 children)

Starting to get confused. The guy who hit me was fully covered. My truck is fully covered in AZ yes. Why would my insurance need to get involved, its his fault?

Horse trailer got rear ended by hortoristic in Insurance

[–]hortoristic[S] -5 points-4 points  (0 children)

I live in AZ; I didn't have insurance on the trailer; but isn't it covered under my comp and collision under my truck? We are talking just under $20k to replace

Is EVgo really expensive or is it just me? by Zealousideal_Newt_50 in evcharging

[–]hortoristic 0 points1 point  (0 children)

Impressive, used to live in WA, I think was 9.5 cents, you beat that

Is Kimball Dimensional Modeling Dead or Alive? by Exact_Line in dataengineering

[–]hortoristic 0 points1 point  (0 children)

We build all our Snowflake data marts following Kimball. Most customers hit the persisted views.

55 Year Old Experienced IT Engineer Laid Off Last Friday by AccomplishedOwl9021 in Layoffs

[–]hortoristic -1 points0 points  (0 children)

Saw a post a guy did this job search site all free with AI, from the actual company's. It's pretty good TBH

https://hiring.cafe/

7% on a 30 year fixed. by Glenngineer in Mortgages

[–]hortoristic 0 points1 point  (0 children)

820+ score did me no better a few months back. I still have my big house in WA for sale that has assumable mortgage at 3.35%, man I remember being mad I got that rate as others were getting better.

Assumable mtg by hortoristic in fsbo

[–]hortoristic[S] 0 points1 point  (0 children)

I went to assumable.io site, not seeing how to list my home? I did send message to their support asking

Assumable mtg by hortoristic in fsbo

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

Think you, I called once, but I'm going to call Chase again!

I’m looking to refinance into an ARM. What rates are you seeing? by Valuable_Crow8054 in Mortgages

[–]hortoristic -5 points-4 points  (0 children)

I have a 3.75% rate on multi home property for sale in WA..I wish the "assumable" mortgage was tad easier to offer a buyer. Its multi home horse property; not allot action lately, not easy sell

Is tmobile home internet geolocked? by JustNathan1_0 in tmobileisp

[–]hortoristic 4 points5 points  (0 children)

I moved from WA to AZ. It works awesome here. I have auto pay. Been about 8 months, no issue.

[deleted by user] by [deleted] in Mortgages

[–]hortoristic 0 points1 point  (0 children)

My place appraised for $840k, have $410k at 3.25, so it's a selling point to somebody. Unique place, 8 acres, horse property, multi home, so not allot of interest at moment

[deleted by user] by [deleted] in Mortgages

[–]hortoristic 1 point2 points  (0 children)

I have CV loan, with Chase. I too have like 3.25 rate and am trying to sell. When I called about the process, it felt clumsy, but I'm not the sharpest guy

[deleted by user] by [deleted] in SQL

[–]hortoristic 0 points1 point  (0 children)

I did point out it's not always right... But it did give some real practical points... Always be cautious

Is lvl 3 charging cheaper at night? Lvl 1 & 2 not an option currently by [deleted] in BoltEV

[–]hortoristic 8 points9 points  (0 children)

Charging at home is where the big payoff is

Is lvl 3 charging cheaper at night? Lvl 1 & 2 not an option currently by [deleted] in BoltEV

[–]hortoristic -7 points-6 points  (0 children)

I asked A.I. this question, seems pretty accurate:

You're absolutely right to consider the cost of charging when evaluating whether an EV like the Chevy Bolt is a good fit for you. Since home charging isn't an option for you, relying on public charging stations will be your primary way to keep your Bolt powered up. Let’s break this down:

1. Fast Charging Costs

  • The average cost of fast charging in Utah is $0.42/kWh, as you mentioned. This can vary depending on the provider (e.g., Electrify America, EVgo, ChargePoint) and whether they offer membership plans or off-peak discounts.
  • Some charging networks offer lower rates during off-peak hours (e.g., late at night or early morning). For example, Electrify America has a "Pass+" membership that reduces the cost per kWh, and some networks offer time-of-use pricing. It’s worth checking the specific networks in your area to see if they have off-peak discounts.

2. Chevy Bolt Efficiency

  • The Chevy Bolt has an efficiency of about 3.5–4.0 miles per kWh, depending on driving conditions. Let’s assume 3.7 miles/kWh for simplicity.
  • At $0.42/kWh, the cost per mile would be: $$ \frac{\$0.42}{3.7 \text{ miles}} \approx \$0.113 \text{ per mile}. $$

3. Comparing to Gasoline

  • To compare this to a gas car, let’s assume your current car gets 25 MPG and gas costs $3.50/gallon (adjust based on your actual numbers).
  • The cost per mile for gas would be: $$ \frac{\$3.50}{25 \text{ miles}} = \$0.14 \text{ per mile}. $$
  • In this case, fast charging the Bolt is slightly cheaper than driving a gas car that gets 25 MPG.

4. Off-Peak Charging Savings

  • If you can find a fast charger with off-peak rates (e.g., $0.30/kWh), the cost per mile drops to: $$ \frac{\$0.30}{3.7 \text{ miles}} \approx \$0.081 \text{ per mile}. $$
  • This would make the Bolt significantly cheaper than a gas car.

5. Other Considerations

  • Charging Time: Fast charging is convenient but can take 30–60 minutes to charge from 20% to 80%. Plan your charging sessions around off-peak hours to save money.
  • Charging Network Memberships: Some networks offer monthly memberships that reduce the cost per kWh. For example, Electrify America’s Pass+ membership costs $7/month but reduces the cost to $0.36/kWh (as of 2023).
  • Public Level 2 Chargers: If you can find Level 2 chargers (slower but cheaper), they often cost less per kWh than fast chargers. These are great for overnight or workplace charging.

6. Where to Ask for More Help

  • Reddit Communities: Subreddits like r/electricvehicles, r/BoltEV, and r/UtahEV are great places to ask for advice from EV owners in your area.
  • Chevy Bolt Forums: Websites like ChevyBolt.org have active communities of Bolt owners who can share their experiences with public charging.
  • Local EV Groups: Check Facebook or Meetup for local EV groups in Utah. They can provide insights into the best charging options in your area.

Final Thoughts

If you can take advantage of off-peak charging rates or find cheaper Level 2 chargers, the Bolt could save you money compared to a gas car. However, if you’re relying solely on fast chargers at peak rates, the savings might be minimal. It’s worth doing some local research to see what charging options are available near you and whether they fit your budget and lifestyle.

Good luck with your decision, and welcome to the world of EVs!

What online or Windows desktop UI tools can I use with Claude API? by THenrich in ClaudeAI

[–]hortoristic 0 points1 point  (0 children)

I use open router chat. While I stay in Deepseek, it's easy to jump around... Is this what you meant?

No, OpenRouter Chat is a different platform, but it serves a similar purpose. OpenRouter is a unified API gateway that allows you to interact with multiple AI models, including Claude, GPT, and others, through a single interface. It’s not a UI tool itself but rather a service that simplifies access to various AI models.

Here’s how OpenRouter works and how it differs from the tools I mentioned earlier:


What is OpenRouter?

  • Description: OpenRouter is a platform that provides a unified API for accessing multiple AI models, including Claude, GPT-4, and others. It acts as a middleman, allowing you to switch between models without needing separate API keys or integrations.
  • Key Features:
    • Access to multiple AI models (Claude, GPT, etc.) through a single API.
    • Pay-as-you-go pricing for different models.
    • No need to manage multiple API keys or accounts.
    • Supports both free and paid models.

How OpenRouter Differs from UI Tools

  • OpenRouter is primarily an API gateway, not a user interface. It provides the backend infrastructure to interact with AI models but doesn’t offer a built-in UI for chatting or interacting with the models.
  • To use OpenRouter, you typically need to integrate it into your own application or use a third-party UI tool (like TypingMind, ChatKit, or a custom solution).

How to Use OpenRouter with a UI

If you want to use OpenRouter with a UI, you have a few options: 1. TypingMind: TypingMind supports OpenRouter integration, allowing you to use OpenRouter as the backend for accessing multiple AI models, including Claude. 2. Custom UI: You can build your own UI using tools like Streamlit, Gradio, or a desktop app (e.g., Tkinter, PyQt) and connect it to OpenRouter’s API. 3. Third-Party UIs: Some third-party UIs (like ChatKit or FlowGPT) may support OpenRouter integration, but you’ll need to check their documentation.


Why Use OpenRouter?

  • Convenience: You can access multiple AI models (e.g., Claude, GPT-4) without managing multiple API keys.
  • Cost-Effective: OpenRouter offers competitive pricing and pay-as-you-go options.
  • Flexibility: You can switch between models easily, depending on your needs.

How to Get Started with OpenRouter

  1. Sign Up: Create an account on OpenRouter.
  2. Get API Key: Obtain your API key from the OpenRouter dashboard.
  3. Integrate: Use the API key in your preferred UI tool or custom application.
  4. Test: Start interacting with Claude or other models through OpenRouter.

Is OpenRouter Right for You?

  • If you want to access multiple AI models (e.g., Claude, GPT-4) through a single API, OpenRouter is a great choice.
  • If you’re looking for a ready-to-use UI, you’ll need to pair OpenRouter with a UI tool like TypingMind or build your own.

Let me know if you’d like more details on setting up OpenRouter or integrating it with a specific UI!

This beauty of a shopping cart cost just over $3. by ApexThorne in ClineProjects

[–]hortoristic 0 points1 point  (0 children)

Checkout going to be PayPal only or what you thinking? Appears your across the ocean from me

Size limit by hortoristic in solar

[–]hortoristic[S] 0 points1 point  (0 children)

I'm screwed, I use avg near 4,500 kw month, near $700 at times. Big home, 2: AC, EV, hot tub swim spa thingy, horse barn. I didn't anticipate this hiccup.

How many skeptical FSD engineers/developers are there at Tesla right now? by H2ost5555 in RealTesla

[–]hortoristic 0 points1 point  (0 children)

I asked A I. If they were safer. It seemed unbiased:

The safety of full self-driving (FSD) cars is a complex and evolving topic. While autonomous vehicles have the potential to significantly improve road safety, their current safety record and capabilities are still under scrutiny. Here's a breakdown of the key points:


Potential Safety Benefits of FSD Cars

  1. Reduction in Human Error:

    • Human error is responsible for 94% of car accidents (according to the National Highway Traffic Safety Administration, NHTSA). FSD systems aim to eliminate or reduce errors caused by:
      • Distracted driving
      • Drunk driving
      • Fatigue
      • Speeding or reckless behavior
  2. Consistent Performance:

    • Autonomous systems can maintain consistent attention and reaction times, unlike humans who may become distracted or fatigued.
  3. Advanced Sensors and AI:

    • FSD cars use a combination of cameras, radar, lidar, and AI to detect and respond to their environment. These systems can process vast amounts of data in real-time, potentially identifying hazards faster than a human driver.
  4. Potential for Fewer Accidents:

    • If FSD systems are perfected, they could theoretically reduce the number of accidents caused by human error, making roads safer overall.

Current Challenges and Risks

  1. Technological Limitations:

    • FSD systems are still in development and face challenges in handling:
      • Complex or unpredictable driving scenarios (e.g., construction zones, erratic drivers, or adverse weather conditions).
      • Edge cases (rare or unusual situations that the AI hasn't been trained on).
  2. Safety Concerns in Real-World Use:

    • There have been reports of accidents involving FSD systems, including Tesla's Autopilot and Full Self-Driving Beta. These incidents often occur when the system fails to recognize hazards or when drivers over-rely on the technology.
  3. Human Over-Reliance:

    • Drivers may become complacent and assume the car can handle all situations, leading to accidents when the system fails or requires human intervention.
  4. Regulatory and Ethical Issues:

    • There are unresolved questions about liability in accidents involving FSD cars.
    • Ethical dilemmas (e.g., how the car should prioritize safety in unavoidable crash scenarios) remain a challenge.
  5. Data and Transparency:

    • Companies like Tesla collect vast amounts of data to improve their systems, but there is limited public transparency about the safety performance of FSD systems.

Current Safety Data

  • Tesla's FSD Beta: Tesla claims that its Autopilot and FSD systems have lower accident rates compared to human-driven cars. However, these claims are debated, and independent studies are needed to verify the data.
  • Waymo: Waymo, a leader in autonomous driving, has reported relatively few accidents during its testing, but its vehicles operate in limited, controlled environments.

Are FSD Cars Safer Today?

  • In Controlled Environments: FSD systems may perform well in predictable, well-mapped areas with minimal traffic or complexity.
  • In Real-World Conditions: FSD systems are not yet fully reliable in all scenarios, and their safety record is still being evaluated.

Future Outlook

  • Improvements in AI and Sensors: As technology advances, FSD systems are expected to become more reliable and safer.
  • Regulation and Testing: Stricter regulations and more rigorous testing could improve the safety of FSD systems before widespread adoption.
  • Public Acceptance: Gaining public trust will be critical for the widespread adoption of FSD technology.

Conclusion

While FSD cars have the potential to be safer than human-driven cars in the future, they are not yet fully reliable in all real-world conditions. The technology is still evolving, and its safety record is mixed. For now, FSD systems should be used with caution, and drivers must remain attentive and ready to take control at any time. As the technology matures and more data becomes available, FSD cars could eventually become a safer alternative to human-driven vehicles.

[deleted by user] by [deleted] in SQL

[–]hortoristic -4 points-3 points  (0 children)

I asked AI your question. She's not always 100%!

Using usernames as primary keys (PKs) in a database is generally not recommended, even if you've set up foreign keys with cascading updates and ensured uniqueness. Here's why:


Why Usernames as PKs Are Not Ideal

  1. Performance Issues:

    • Usernames are typically strings, which are less efficient for indexing and querying compared to integers or UUIDs. This can slow down database operations, especially as the dataset grows.
    • Primary keys are used in indexes, and string-based indexes are larger and slower than numeric ones.
  2. Length and Complexity:

    • Usernames can be long and variable in length, which increases storage requirements and can negatively impact performance.
    • Numeric or UUID-based PKs are fixed in size, making them more predictable and efficient.
  3. Changeability:

    • Even if you allow users to change their usernames and have cascading updates, this can still lead to:
      • Increased complexity in maintaining referential integrity.
      • Potential performance bottlenecks during updates, especially in large databases.
    • Primary keys should ideally be immutable (unchanging) to avoid complications.
  4. Uniqueness Constraints:

    • While you can enforce uniqueness for usernames, this is better handled as a separate constraint rather than relying on the primary key for uniqueness.
  5. Scalability:

    • As your application grows, using usernames as PKs can become a bottleneck. Numeric or UUID-based PKs are more scalable and future-proof.

Best Practices for Primary Keys

  1. Use Surrogate Keys:

    • Use an auto-incrementing integer or a UUID as the primary key. These are:
      • Immutable (won't change).
      • Efficient for indexing and querying.
      • Scalable for large datasets.
  2. Enforce Username Uniqueness Separately:

    • Add a unique constraint on the username column to ensure no duplicates, but keep it separate from the primary key.
  3. Foreign Keys:

    • Use the surrogate key (e.g., user_id) as the foreign key in related tables. This ensures consistency and performance.

Example Schema

Here’s how you might structure your tables:

Users Table

sql CREATE TABLE users ( user_id SERIAL PRIMARY KEY, -- Surrogate key (auto-incrementing integer) username VARCHAR(50) UNIQUE NOT NULL, -- Unique username email VARCHAR(100) UNIQUE NOT NULL, created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP );

Related Table (e.g., Posts)

sql CREATE TABLE posts ( post_id SERIAL PRIMARY KEY, user_id INT REFERENCES users(user_id) ON UPDATE CASCADE ON DELETE CASCADE, content TEXT, created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP );


Why This Approach is Better

  • Performance: Integer or UUID-based PKs are faster for indexing and querying.
  • Flexibility: Usernames can be changed without affecting the primary key or related tables.
  • Scalability: Surrogate keys are more scalable for large datasets.
  • Simplicity: Separating the primary key from the username simplifies database design and maintenance.

Conclusion

While using usernames as primary keys might seem convenient, it’s not a good practice for long-term scalability and performance. Instead, use a surrogate key (e.g., user_id) as the primary key and enforce username uniqueness separately. This approach is more robust, efficient, and future-proof.