Skip to content
View in the app

A better way to browse. Learn more.

TalkBears Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

DABEARSDABOMB

Admin
  • Joined

  • Last visited

Everything posted by DABEARSDABOMB

  1. Morgan did pretty good under Getsy from a run blocking perspective. I think Waldron hasn’t figured his unit out yet. He may just suck - I don’t know but he leaves a lot to be desired thus far. Oline was awful..Caleb wasn’t good but he was better than the previous week and damn did he take some shots. You can see he still needs to build chemistry with his wideouts etc. At least we saw Kmet a bit..every time he was targeted something good happened.
  2. He would be for a 2nd rounder too - it’s not happening. I doubt they would get a 3rd or 4th…but all of this is why they should have kept Justin Fields…cause they might have gotten a 2nd or 3rd at this point for him….but I get the distraction part of it.
  3. It sounds liek Flus is a bit concerned with Odunze's knee. I'm a bit worried here - hopefully it is minor and no longer term issues/concerns.
  4. I was having flashbacks of that game too. We need Ryan Bates healthy quick cause Shelton was abused in week 1. With that said - Caleb finally sees a real defense (preseason doesn’t count)….so this is first step of development now to see how he grows and emerges this first quarter of the season. Taking the season as week 1 is the throwaway and now we have 4 quarters of the season left - looking for growth in each quarter out of Caleb.
  5. Bears are not ready for what Titans are doing on offense.
  6. I hope you are right. I think our d is overhyped. Dline has serious flaws in my opinion that prevent it from being top 5. They will have room to beef up via next draft and / or free agency (just like the oline)…but I think this is more a 5-10 defense than a top 5 due to in my opinion a mediocre dline.
  7. DABEARSDABOMB replied to bears_gal_aly's topic in Bearstalk
    Welcome aboard - let’s go Bears!!!
  8. Will be curious to see who they pick up tomorrow. Clear there will be a bit more churn still. Not overly surprised though with any of the moves - other than say Stroman and Carter. For those wondering - Hosmer sticks around not because he is a good running back but because he’s a really good special teams player. Carl Jones is a guy I liked at Lb so hope to see him make practice squad.
  9. DABEARSDABOMB replied to AZ54's topic in Bearstalk
    Should caveat know nothing about the player.
  10. DABEARSDABOMB replied to AZ54's topic in Bearstalk
    We needed a dt - and we had lots of 6th/7th rounders so totally fine with this.
  11. Does your WIFI use a VPN by chance? I know VPN can take a bit longer to fully cycle through the "new address" changes that happened.
  12. I know what your issue is - I had it briefly on my phone (but no the relogin) but where you get the site is down message. When you are getting that message - your phone is still looking to its old history - which is pointing you to the old server (meaning it is just going off of memory of where talkbears was located in the past (underneath the name there is an address the basically points the domain name to the specific IP the server is at). Right now it just keeps thinking your home is that old server (which is still up and will be shut down in another day or two)....it just needs to work itself out of that funk - for 99% of the cases that happens within first 24 hours. For others it can be as long as 72 hours. In your case it seems to be persisting longer - which is really frustrating. If you haven't already, try the below instructions from your google phone:
  13. That shows up if you try password and fail a couple times. What browser do you use? Is this only on mobile? Or you running into any issue on computer?
  14. Boo. Let me see what else I can try.
  15. Final refresh is all done.
  16. Mongo - try clearing your cookies/cache on your phone. It looks like your dns hasn’t yet fully kicked over to new server (for some internet providers it can take a bit longer)…but it should get better in next couple days and clearing cookies may take instantaneous.
  17. Final steps are going to happen today
  18. Evidently Albert Breer was reporting today that the Bears have been in touch with Ngakoue's reps recently. I have to imagine he is there plan B - depending on how things shake out. I don't know how much he has left - but got to imagine Bears could get him between 5-7M for 1YR. He has flaws - but not bad from a depth perspective and you don't feel bad if other guys play their way into his role (in fact you prefer it). I presume he would be the passing down end - and it would allow you to slide Walker inside on those plays.
  19. Knocking on wood so you don’t jinx us haha
  20. Chiefs have announced they are sitting all of their starters. No word yet from the Bears. I presume the starters will sit though.
  21. One caveat - we will have a minor outage later this week; Fingers crossed this should be a pretty minimal one (1-2 hours max). The big lift is behind us and Az - we held it up a few days for you and were able to ensure no posts being lost
  22. With us on the new server and new software - please let us know how it is working. If you are running into any issues let us know. My immediate reaction is wow is this site running fast. I also recognize we will have some hiccups as the dns propagates.
  23. Let’s get to this game healthy and let this be the start of a truly new era of Bears football - one that puts the Bears back on the map as a truly elite franchise!!!

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.