1992casey
Verified Member-
Posts
15,393 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Events
Milwaukee Brewers News, Rumors & Analysis
2026 Milwaukee Brewers Top Prospect Rankings
Milwaukee Brewers Videos
2022 Milwaukee Brewers Draft Picks & Signing Bonuses
Milwaukee Brewers Trade & Free Agent Rumors
Milwaukee Brewers Fan Guides & Resources
2023 Milwaukee Brewers Draft Picks & Signing Bonuses
2024 Milwaukee Brewers Draft Picks & Signing Bonuses
The Milwaukee Brewers Players Project
2025 Milwaukee Brewers Draft Picks & Signing Bonuses
2026 Milwaukee Brewers Draft Picks & Signing Bonuses
Store
Downloads
Gallery
Everything posted by 1992casey
-
Pretty cool. http://forum.brewerfan.net/images/smilies/smile.gif Thanks for passing this along!
-
I'm sure there'll be another "entertaining" story soon. In the interest of full disclosure, here's what RPX's web site says about this login, which uses their technology. Except for testing, I think I'll stick to the regular Yuku login. To test, I've been using newly created accounts specifically set up for that purpose.
-
Some of you have likely seen that Yuku now allows you to log in using your credentials from any of twelve different services, including: FacebookMySpaceYahooTwitterGoogleAOLWindows LiveBloggerLinkedinFlickrWordPressOpenIDThere are two ways to reach this page: Hitting the Log In button in the navigation bar without putting any information in the username and password fields.Hitting a Reply button while logged out.The concept is cool, but the implementation is not. As long as the outside account uses the same e-mail address as your Yuku account, you're able to use that login to gain access to Yuku. This might be handy for those who have trouble keeping track of multiple passwords. Here's the security rub. When you log out, a cookie is saved that stores your password. When you want to log in again, you just hit a button, and you're logged in without entering a password. Obviously, that defeats the purpose of logging out. Therefore, if you use an alternate login on a computer that's used by others, delete your cookies after logging out. Here are a couple of screen captures. The one directly below shows the login screen. On the right, you'll see graphical buttons that will generate popups to log you in via the twelve other services. Six buttons display when the page is loaded. By hitting an arrow on the right, you can access the other six. http://images.yuku.com/image/png/ea3359039d05cb2754ad12d21a1eddba713973b.png If you log out and subsequently want to log in again, the "welcome back" interface below replaces the buttons. This image uses Google as an example. http://images.yuku.com/image/png/a93355d65737410a503240fa01d8fe3207bbdea.png When one hits the Sign In button, s/he is logged in without a request for a password. Unfortunately, Yuku staff thinks this is fine. I was told: This information is wrong. Closing one's browser window doesn't clear cookies. Quitting (exiting) the browser application only clears cookies when set to do so. No browser clears cookies upon exit by default. My advice? If you're the only one using your computer or if you're good at remembering to toss your cookies when you're through browsing, go ahead and use this feature. If not, stick to the regular Yuku login.
-
FOG. And people driving in the fog with their headlights off. I'm betting that these people are driving cars whose headlights turn on automatically. I had to turn on the lights manually the other day. Cars should really turn on headlights under lighter conditions than they're currently set up to do.
-
Never blindly believe what you read or hear in the media, especially when there's nothing tangible there to make one believe it's true.
-
When Brian and Peavey ran the PHP LambeauLeap board, they found that security was a hassle. I don't think it was necessarily difficult, but dealing with it was constant. Peavey was kept busy on a daily basis. Besides security, the other reason for going with a hosted solution is cost. Essentially, we're pooling our costs with other boards to share the system, and the monetary aspect is reasonable. Yuku does have daily backups, but we don't have direct access to them. If we were to experience data loss, we'd have to submit a help ticket and hope that our problem was considered a high enough priority for them to assign a developer to attend to the issue. Yuku's terms of use would prevent us from exporting our board to another system. Mainly, the issue would be the membership list. Your account is with Yuku rather than with Brewerfan. I guess that's to protect Yuku members from unscrupulous board owners. Ironically, right now, it seems that we're protecting our members from Yuku. Their terms of use would also prevent us from automatically scraping data for the purpose of transferring it elsewhere. I believe we could do manually it a page at a time if we wanted to. Of course, that would be a daunting task. If we were to move elsewhere at some point, we'd actually be able to keep the Yuku board open as a read-only archive at minimal cost--or we could allow Yuku to serve ads and pay nothing. We'd be covered as far as being able to keep our posting history. I haven't talked to Brian about the latest Yuku issues, so I don't know where he stands. My personal feeling is that things would either have to get worse--or persist for a longer period of time--before we should consider the huge job of moving elsewhere. Also, the staff and moderators feel that the main site is the bigger priority right now. It's currently hard to deliver new content on a regular basis. A new infrastructure would allow us to address that.
-
The gift boxes are now displaying for some "longtime" members, whether they're Supporters or not. I don't know how Yuku defines "longtime," but from what I can gather, it's quite a number of years of membership. (If a lot more people were seeing these for the first time, all hell would have broken loose at Support by now. http://forum.brewerfan.net/images/smilies/smile.gif) Again, I don't recommend converting at this time.
-
If Lofgren is still on waivers, Cleveland hasn't yet had the opportunity to take him back. There's still time to work out a trade to a team who'd be willing to keep him on its Major League roster. It's still possible that there'll be no trade, Cleveland doesn't take him back, and Lofgren agrees to go to Nashville.
-
Scott, because Hernan's never been outrighted, I believe the Brewers would be able to bypass waivers if they wanted to outright him. (Someone please correct me if I'm wrong. http://forum.brewerfan.net/images/smilies/smile.gif) Here are his career transactions: http://www.brewerfan.net/...sactions.do?playerId=295 EDIT: Strike that about waivers and outrighting.
-
If a player's contract is guaranteed, he's paid for the full season no matter when he's cut. If a player with a non-guaranteed contract is cut in the first half of spring training, he receives 1/6 of his salary. If a player with a non-guaranteed contract is cut before Opening Day, he receives 1/4 of his salary. The contracts of all players on the roster on Opening Day become guaranteed.
-
Patrick425: -never tweeted or have joined any other social network Yuku counts as a social network--or so they say. However, you joined ezBoard and Brewerfan dragged you into Yuku, so I guess your record is intact. GAME05: possibly wrong, but i don't think i've ever posted on an in-game thread =81&submit=search&advanced=1]Four times in 2008. http://forum.brewerfan.net/images/smilies/smile.gif
-
It's seems like they are hung up on their own agenda without providing adequate support to the product most of us are utilizing. Bingo. The general tacks are: to dismiss an issue by attempting to tell us it's not an issueto offer a complicated workaround for something that should be easy to tell us that when a bug is fixed, something will be announced, and in the meantime we should sit back and waitWe know all about sitting back and waiting. The page and reply numbering issues have been going on since August, 2008. There's been an issue with using the back button in Mozilla browsers that's been on the table since June, 2008. It's started to go away because of new browser releases (Firefox 3.5 and SeaMonkey 2.0), but it still affects Firefox 3.0, Camino, and Flock. These three browsers are still being actively maintained; each of them has had a new release within the past month. On August 5, 2008, a troll "alerted" us to the fact that Yuku's default profanity filter didn't contain any plural cusses. It was also noted that a common 13-letter cuss isn't filtered. This still isn't fixed. We know the fix is easy. Immediately after we migrated, we requested that "dick" be removed from the default filter. Among other respected gentlemen, that's Mass Haas' dad's name. http://forum.brewerfan.net/images/smilies/smile.gif It was taken care of, pending a code push, within 45 minutes of the time the request was posted. We've addressed the cusses at Brewerfan/LambeauLeap by adding them to our custom filter, so we're covered. There are a ton of boards out there, however, who wouldn't be aware of this and think they have cuss filter protection, when in fact there are big gaps. Here's another example. In December, I submitted a help ticket about this issue: blocks, the information contained within is still viewable by savvy members unless one first sets the block's permissions to be viewable to "only me." The "official" response from...">Disabled profile blocks still viewable . I explained that when one "disables" profile blocks, they're still viewable if someone knows how to "crack the code"--which isn't very hard to do. Quoting the staff response: "Disable = hide it from view." No, it's not. Hiding from view isn't the same as disabling. To disable something means to prevent it from working, or to make it unable to be used, or to make it inoperative. When your intelligence is insulted like that, you end up being too dumbfounded to respond. In the meantime, these "disabled" blocks are still totally accessible. A recent code push caused people to lose PMs. OK, fine; things happen. It's comforting to know that when a member reported that her PMs were missing on August 14, 2009, her messages were restored promptly... on March 2, 2010. It wasn't always this way. Boards received excellent attention until KickApps purchased Yuku in early 2008. By late 2008, staff members were leaving en masse. I believe at least seven left within the span of about four months. This group included Kristin and Ransom, the two who were so helpful in seeing us through our migration from ezBoard. Having said all that, it would certainly make sense to look at alternatives. However, with 3,600 members and two boards, a decision like that can't be made quickly. Before undertaking such a task, it would be absolutely necessary to make sure the grass is greener on the other side of the fence.
-
I guess I owe everyone something more explicative than the terse lead. When the gift box suddenly popped up, I figured that I'd better get something posted quickly. As I mentioned, Yuku is in the process of rolling out new profiles based on the Facebook Open Platform. They're currently in beta and are in very rough shape. While the huge majority of the Brewerfan/LambeauLeap membership doesn't appear to do a whole lot at the profile level, this still affects us. The biggie is that the majority of us use the PM interface; that's part of one's profile. Putting it bluntly, it's not ready for prime time. Examples: If you're sent a PM as part of a group, your only option is to reply to the group. You can't reply only to the sender. Yuku is addressing this.The PM interface lacks CC, BCC, the ability to change the subject upon replying, the ability to exclude people when replying to all, Forward, Save to Drafts, and a Trash folder.It uses a conversation format, which would be fine if it were done right. Picture a long Gmail conversation with nothing collapsed. This separates the "To" field from the box where you compose your reply. Also, you can't choose to reply to an individual message. All you can do is add to the conversation.When you go to read your new PMs, there's no clear indication as to which messages are new. Entire conversations are highlighted in a different color. The new message should be highlighted, not the whole conversation. Also, you can't depend on color to convey meaning. sbrylski06 can tell you about that. http://forum.brewerfan.net/images/smilies/smile.gif There needs to be some indicator (such as an icon) next to each new message.Unfortunately, when Yuku staff is asked about PM-related issues, they awkwardly try to defend the interface by saying it's just fine. It would be much more comforting if we could be assured that the awful condition of PMs is due to beta and that we can expect improvements. Staff won't commit to anything other than offering the choice of replying to the sender of a group PM vs. replying to all. Other areas of concern: Privacy. When converting, private stuff doesn't necessarily remain private. I'd assume this would get better as the beta process goes on. Also, privacy settings are complex and incompletely documented at this point.Conversion glitches. Sometimes images and PMs don't transfer and have to be taken care of manually by staff. A new album conversion script was pushed last Friday; that should be given some time to shake out before trusting it.The juvenile nature. We can hug, kiss, bite, and dropkick each other. Currently, we can also *********1[/sup] each other. Yuku is removing that one.To give you an idea of where Yuku is coming from, "kick *ss"1[/sup] is the central point of their advertising. Yes, that's how they spell it. Worse, the information presented isn't necessarily accurate. Yuku can't be bothered with details like grammar and usage. If you ever run across a 401 page, please don't think the verbiage you see came from us. These are currently in place for everybody.What really hurts Brewerfan/LambeauLeap is that Yuku has essentially abandoned work on the boards while profiles have been under development. We have serious bugs that are a year and a half old (or older): funky reply numbers and page numbers would be the top bug that comes to my mind. There's been no commitment on the part of Yuku staff to deal with those. Even when Yuku staff says the focus isn't shifting from boards to profiles, there's no reason to believe them. Their credibility has eroded considerably. Examples: The fact that it took 17 months to make Convert URLs work as intended.The fact that until late January, there were no significant code pushes for 11 months, even though there were plenty of bugs on the table to fix. For the most part, longtime board bugs are still present. Board search engines break routinely, and over the past year, they've taken up to three months to be fixed. (The fix is actually a five minute process.) The worst part of this is that search pages are paid views; people use the search, see nothing, and the community is charged. The searches on Brewerfan and LambeauLeap were never down for as long as three months, but the search on BPS was. The general excuse for the delay in fixing searches was that the developers were busy on other projects (i.e. the new profiles). One real doozie of an explanation was that if Yuku fixed the search engines on the boards that reported issues, it wouldn't be fair to the boards that didn't report. http://forum.brewerfan.net/images/smilies/frown.gif Chat was down for two weeks in early November. "Because of member complaints," a substandard replacement was instituted. When members would ask about getting the "real" chat back, we were constantly told that "chat isn't broken; it's just different." Obviously, that's an insult to members' intelligence. Chat was finally fixed (more or less) in January. While our members don't really use the profile comment feature, this is really telling. Over the past year, issues related to profile comments were constantly reported in the Bugs forum. A common response from staff was that comment issues would go away in the new profiles. I don't think anyone ever dreamed that the staff response meant that comment issues would go away because comments were being eliminated. Staff has backtracked and decided to return comments as a feature in the new profiles, but that doesn't erase the disingenuous and misleading nature of the information being posted at the time. Rolling out these profiles with hype rather than explaining the truth about beta adds to existing credibility issues. Nothing in the conversion interface even mentions beta. Instead, it focuses on stuff about how conversion is reserved for "premiere" members. (It's isn't; all 15 million Yuku members can convert if they wish.) It's not as if the new profiles lack positives. Image management is improved. Members will be able to crop, rotate, and re-size images. It'll be easier to get rid of "stock" HTML boxes that are going to go unused. And the PM interface (which sucks in every other way) can be skinned; members can "fix" stuff that's hard to read or that simply doesn't appeal to them. The bottom line is that if you're curious and want to take a look, create a test profile on a new account (different e-mail address), and convert that. Don't convert the "real thing" at this point. Non-supporter profiles can be converted via an "invitation" from a converted profile. If that's something you're interested in doing, I can invite you from a converted test profile. I know there's a lot to absorb here, so if you have questions, feel free to ask. And actually, there's a lot more I could have included. Consider this to be the "condensed" version. ------------------------ 1. Please don't use "*********" in your posts (unless you want to comment on this soon to be defunct feature). And if you need to say "kick *ss," feel free to say "kick ass" (please restrict "kick *ss" to this narrow context). The only reason I posted those terms was to quote Yuku. It's ironic that the first half of "*********" is in Yuku's default cuss filter.
-
RyDogg, are looking for a home grown team based on how players did with the Brewers, or are you looking for a home grown team based on how players' entire careers worked out?
-
Sheets: "Zero bad blood" with Melvin, Brewers
1992casey replied to OldSchoolSnapper's topic in Milwaukee Brewers Talk
And if Ben didn't pitch that day, the same caller would have still called him the most selfish player in baseball for not pitching. -
Sheets: "Zero bad blood" with Melvin, Brewers
1992casey replied to OldSchoolSnapper's topic in Milwaukee Brewers Talk
Same old Ben. http://forum.brewerfan.net/images/smilies/smile.gif Not really, Tom. Issues with one's employer don't necessarily have to be elevated into "bad blood." -
Some recent server maintenance has caused pre-2009 private messages to disappear for some members. If that's happened to you and you'd like them restored, please do one of the following: Post your request to the lost private messages topic at Yuku Support. The lead is old, but the recent replies are current.Post your request to this topic, and I'll relay it to Yuku.PM your request to me.It's possible that for some, more than just pre-2009 messages could be missing. If that's the case, it'd still be appropriate to let Yuku know.
-
Brewers seek passage of scalping bill
1992casey replied to Invader3K's topic in Milwaukee Brewers Talk
Here are this year's Giants ticket prices: http://sanfrancisco.giant...ting/dynamic_pricing.jsp -
Whenever I go to a Pick 'n Save, I look to see which signs are laminated.
-
A friend of mine has a new HP that's way too slow for Windows 7 (yes, it was sold with 7). I think the issue might be that she has a single core processor (whatever AMD's equivalent to the Celeron is). I see that the computer you're looking at has a dual processor, but I'd still check it out personally for speed.
-
I can't help you at all on Miami, but congratulations on the grad school offer. http://forum.brewerfan.net/images/smilies/smile.gif

