Skip to content
View in the app

A better way to browse. Learn more.

Tip.It Forum

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.

acenator

Members
  • Joined

  • Last visited

Everything posted by acenator

  1. 770 Finally, some movement!
  2. :geek:
  3. /\ In this context, the Goon is correct. < Is into many things that many people would consider weird, but they mostly have to do with computers or explosions. \/ Has never blown anything up and is, therefore, quite deprived.
  4. Banned because ... Wait, that was Comical's car?
  5. :arrow:
  6. 750 I did not blink. How would you know if I blinked anyways? :unsure:
  7. The tag is a custom tag that was added by the site admin(s) (one of the cool things about BBCode is the ability to make custom tags; the [media] tag is also a custom tag, I believe), which also means they can remove/deactivate them. I do not know what purpose they were made to serve, but that is the only logical way they could have come into being. It's probably for ease of use by the admins. As all of our posts are surrounded by tags without us typing them. Our sigs too. So, they'd probably just make it an admin only function. I don't see how it could make anything easier for anyone. The only use we've found so far is breaking pages. They might have it surround posted text in their database, but that would make removing its functionality a big mess. They'd have to remove all instances of it in the database (otherwise the tags would show up in all previous posts) and string comparison of that magnitude could take a long time. Not to mention the fact that they'd have to reconfigure how posts are handled. That is not a project anyone I know would look forward to. I'm guessing there's some special use for it that we have not found yet because setting yourself up for a mess like the project described above is just downright bad horrific coding. It's either that or, more likely, the only reason it has not been removed yet is the very fact that they don't want to face such a project (the fact that it has not been used anywhere but here also helps, but just the potential for anyone to break a bunch of pages is not cool when you're a site admin). :ugeek: Tell me if I'm over-analyzing this. As a geek and a nerd, I never can tell when I'm over-analyzing anything. Also, if I'm missing anything obvious here, let me know. I also have a tendency to miss obvious things when analyzing issues with multiple unknowns. [/hide] It's possible that they added it innocently without knowing that it was capable of breaking pages. I'm not sure how likely it is that they would have tested all of the tags for page breaking properties but they could have overlooked somehow. They probably never anticipated that some people would decide to test out random codes one day. That's possible, pig. I'm still curious as to what it's actual intended use was, though. Having it in each post in the database is a bit redundant considering each post (likely) has a unique id that can be used to pull out just that post. Oh, well... I'll probably never know until an admin tells me and when that happens, they're likely to either have it fixed or be in the process of doing so.
  8. Banned for a gopher. "Gopher, Everett?"
  9. /\ Slacker. < Procrastinators unite! ... Tomorrow. \/ Moo.
  10. The tag is a custom tag that was added by the site admin(s) (one of the cool things about BBCode is the ability to make custom tags; the [media] tag is also a custom tag, I believe), which also means they can remove/deactivate them. I do not know what purpose they were made to serve, but that is the only logical way they could have come into being. It's probably for ease of use by the admins. As all of our posts are surrounded by tags without us typing them. Our sigs too. So, they'd probably just make it an admin only function. -snip- :ugeek: Tell me if I'm over-analyzing this. As a geek and a nerd, I never can tell when I'm over-analyzing anything. Also, if I'm missing anything obvious here, let me know. I also have a tendency to miss obvious things when analyzing issues with multiple unknowns. Nope, you explained quite well. I understood what you were talking about. Which is important. That is important. There's nothing worse than writing (or just saying) a bunch of stuff and then having everyone who reads it not understand what's being said (another problem I have, especially at work; loan officers know nothing about computers :wall: ).
  11. The tag is a custom tag that was added by the site admin(s) (one of the cool things about BBCode is the ability to make custom tags; the [media] tag is also a custom tag, I believe), which also means they can remove/deactivate them. I do not know what purpose they were made to serve, but that is the only logical way they could have come into being. It's probably for ease of use by the admins. As all of our posts are surrounded by tags without us typing them. Our sigs too. So, they'd probably just make it an admin only function. I don't see how it could make anything easier for anyone. The only use we've found so far is breaking pages. They might have it surround posted text in their database, but that would make removing its functionality a big mess. They'd have to remove all instances of it in the database (otherwise the tags would show up in all previous posts) and string comparison of that magnitude could take a long time. Not to mention the fact that they'd have to reconfigure how posts are handled. That is not a project anyone I know would look forward to. I'm guessing there's some special use for it that we have not found yet because setting yourself up for a mess like the project described above is just downright bad horrific coding. It's either that or, more likely, the only reason it has not been removed yet is the very fact that they don't want to face such a project (the fact that it has not been used anywhere but here also helps, but just the potential for anyone to break a bunch of pages is not cool when you're a site admin). :ugeek: Tell me if I'm over-analyzing this. As a geek and a nerd, I never can tell when I'm over-analyzing anything. Also, if I'm missing anything obvious here, let me know. I also have a tendency to miss obvious things when analyzing issues with multiple unknowns.
  12. The tag is a custom tag that was added by the site admin(s) (one of the cool things about BBCode is the ability to make custom tags; the [media] tag is also a custom tag, I believe), which also means they can remove/deactivate the tags. I do not know what purpose they were made to serve, but that is the only logical way they could have come into being.
  13. Banned for having all English in your profile, post, avatar, and signature.
  14. 750 I'm not sure how this will work, but you're on.
  15. 750 And I must insist that you count up, so it seems we are at an impasse... I'd say we should solve it with a battle of wits, but I'm not entirely sure how that would work online. Not to mention that I do not currently have any iocane powder on me. I guess we could try to start a land war in Asia, but that'd just be foolish.
  16. /\ Probably more bored than drugged. < Not bored. \/ Drugged.
  17. That's a pretty good synopsis. Why, thank you. @Napalm, Halo and who: lol
  18. Banned for a thought.
  19. 1914 - The beginning of WWI
  20. No. TPUM thinks they should make a movie about Catwoman when she's 60 years old.
  21. /\ Has substituted the word nuts for insane when describing me. < Possibly insane/nuts, but will likely never go to a professional to find out. \/ Has gone to a professional to find out.
  22. Banned for death of cat by curiosity.
  23. 750 No, you stop that. Start counting up.
  24. Welcome, newcomer to TIF's (un)official thread of spam and all around weirdness. It has not killed anyone... yet... well, at least as far as I know, but I must warn you that it can lower you IQ on certain days. Happy spamming!

Important Information

By using this site, you agree to our Terms of Use.

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.