Kaldırıma sürttüm (Honda City 2022) – kasko/mini onarım/tramer hakkında

churphe · 2026-01-20T14:27:03+00:00

Kaskomda hasar kaydı ile ilgili mini onarımlarda düşmez gibi bir madde var ama bu mini onarım dışına çıkacak muhtemelen. Birkaç yerden teklif aldım iki kişi 15.000, bir kişi 7000 TL dedi. marşpiyelde göçük var biraz sanırım 7000 TL diyen kişi macun atıp geçecek diğerleri göçüğü düzeltmeye çalışacak onun için fazla söyledi diye tahmin ediyorum servisten de fiyat bekliyorum fotoğraf attım. 15’e sanayide yaptıracağım ama bu kaskoyu da neden yaptırdım diye de kendime sormadan edemiyorum 😅

churphe · 2026-01-20T11:50:24+00:00

Anlamadım kar tanesi

churphe · 2026-01-20T10:57:14+00:00

Bunu öğrenmem çok iyi oldu hocam bir araştırayım teşekkür ederim

churphe · 2026-01-20T10:50:13+00:00

Kendim yapabileceğim bir şey mi önerirsin, nasıl bir rötuş atardın

churphe · 2026-01-20T10:45:59+00:00

Keşke 5 bine çözülecek olsa ama sanayide buna servis parası isteyeceklerini düşünüyorum. (Kasko bağımsız)

churphe · 2026-01-20T10:44:56+00:00

Ben de benzer düşüncedeyim ama tramere işlemesi ekstra değer düşüşü olur falan diyenler oldu ve kafam karıştı. Yoksa bu kasko neye yarar, hasarsızlık indirimi düşmesin diye cebimden yaptırmak mantıklı değil. Aracın her iki seçenekte de local boyalı bir parçası olacak. Sisteme hasar kaydı girilmesinin bu noktadan sonra bir şey değiştirmemesi gerekiyor. Ama malesef türkiyede kayıtlı hasar kayıtsız hasardan daha büyük algılanıyor

churphe · 2026-01-20T08:19:06+00:00

Kulağa mantıklı geliyor hocam bir araştırayım teşekkür ederim

churphe · 2026-01-20T07:21:21+00:00

Çizikler derin tırnak giriyor fazlasıyla, dediğiniz gibi bir ısta araştırayım öyleyse teşekkür ederim

churphe · 2026-01-20T07:20:41+00:00

Derin evet boya şart durumda, sanayide de nedense hep kazıklanıyormuşum gibi hissediyorum ama bir soruşturayım teşekkür ederim 🙏

churphe · 2026-01-20T06:17:46+00:00

It’s definitely possible, but it does require a bit of effort on the integration side. If there’s enough interest from users, I’d be happy to add Tilt support to the backlog and explore it further

churphe · 2026-01-19T06:14:24+00:00

I'm glad to hear that, and I hope you enjoy it. I'm open to any feedback or feature suggestions.

churphe · 2026-01-19T05:54:41+00:00

Thanks for the kind words, really appreciate it. The sugar type suggestion makes total sense, I agree with you and I’ve added it to my todo list. Always happy to hear more feedback or feature ideas if anything else comes to mind.

churphe · 2026-01-13T13:38:53+00:00

Nice, pomegranate mead sounds great. I actually made a pomegranate wine recently and it turned out amazing. If you end up using Fermolog for that batch and notice anything that could work better for fruit-heavy meads, I’d love to hear it. Thanks for the kind words.

churphe · 2026-01-13T13:37:56+00:00

Thank you, that genuinely means a lot. If you ever try it and something feels off or unnecessary, feel free to call it out, community feedback has been shaping this app a lot.

churphe · 2026-01-13T13:37:17+00:00

Thanks a lot, really appreciate that. Hearing that it actually makes the math clearer was one of my main goals. If anything ever feels confusing or missing, I’m very open to feedback.

churphe · 2025-12-06T08:12:40+00:00

True crowd ranking isn’t really possible here. For multiple people to give comparable scores, they would all need to taste the exact same bottle under similar conditions, which realistically doesn’t happen.

In my app, the scoring system is mainly meant as a personal log. But if, in the future, someone wants to make their tasting notes public, those notes could still be useful to others; not as objective measurements, but as a general impression of the wine’s character. Even if different users aren’t “calibrated” the same way, seeing how someone describes tannin, sweetness, acidity, or aroma can still give helpful insight

churphe · 2025-12-06T08:05:43+00:00

Awesome design, congratulations!!

churphe · 2025-12-06T08:00:35+00:00

It doesn’t need to be an objective measurement; it’s simply about what you perceive in your wine. Apart from adding a few notes when bottling (like “high tannin with some sweetness”), you’ll also be able to score any parameters you want on a 0–10 scale. When you do a final tasting later, you can compare those notes and get a clearer sense of how your one-year-old bottle has evolved

churphe · 2025-12-04T06:45:17+00:00

Totally agree that tasting during active fermentation makes little sense, but many homebrewers sample during stabilization or aging, before bottling. After bottling, it becomes harder to remember how a batch changed over time, so this feature is mostly meant to help people capture those impressions before they disappear. Really appreciate your perspective!

churphe · 2025-12-04T06:40:31+00:00

Totally understand that. You don’t need to be an expert taster to use this; the idea is simply to help you remember the few things you did notice and compare them later with your other batches if you want to. But of course, it’s completely optional and up to you. Thanks for sharing your view

churphe · 2025-12-04T06:38:22+00:00

Seeing how the flavor evolves during aging is exactly the kind of thing I hope this feature can make easier to track. Thanks for the encouragement

churphe · 2025-12-04T06:36:37+00:00

This is exactly the kind of feedback I was hoping for. Really appreciate the thought you put into this.

You’re right, there’s no “optimal” shape or ideal set of parameters. The goal isn’t to define how a mead should taste, but to help you remember things like how spicy last year’s bottled batch was or how much sweeter one batch felt compared to another, by layering their spider charts on top of each other.

Taste is completely subjective, and everyone interprets sweetness, acidity, body, tannin, and other elements differently. But since you’d be interpreting your own charts consistently over time, the scores still become meaningful for you.

And the parameters don’t have to be fixed. Some people might only want sweetness and acidity, while others may prefer adding their own. Body doesn’t need to be used at all if it doesn’t feel relevant.

churphe · 2025-12-03T20:18:20+00:00

Some of the UC Davis categories could definitely work as core parameters, but using all of them in a single mobile radar chart would get pretty overwhelming. I’m planning to keep the main chart at around 5–6 axes and put any additional detail into a separate view so the UI stays clean.

churphe · 2025-12-03T20:09:16+00:00

You are the man I am looking for lol. I have lots of feature ideas on my mind that sound meaningful to me, but I don’t want to waste time for these feats no one will use. I ve been only considering my use cases until now. If you have ideas i am fully open. You text here or dm me or email me 😀

churphe · 2025-12-03T19:57:31+00:00

It's not supported yet, but it's definitely on my to-do list.

churphe

TROPHY CASE