×

Notice

The forum is in read only mode.

TOPIC:

Beoir forum on mobile devices 14 years 8 months ago #7

Thanks Fran!

Beoir forum on mobile devices 14 years 8 months ago #8

Eh Fran? I checked out HomebrewChatter and two of the new posts this morning were 'So I got a new rifle' and 'Wherein we make thinly veiled racist remarks about Asians'. I shit you not! :-O

*scurries back to the (relative) safety of Beoir* <!-- s;-) --><img src="{SMILIES_PATH}/icon_wink.gif" alt=";-)" title="Wink" /><!-- s;-) -->

Beoir forum on mobile devices 14 years 8 months ago #9

&amp;quot;SOS_OPA&amp;quot;:uvlhigol wrote: Eh Fran? I checked out HomebrewChatter and two of the new posts this morning were 'So I got a new rifle' and 'Wherein we make thinly veiled racist remarks about Asians'. I shit you not! :-O

*scurries back to the (relative) safety of Beoir* <!-- s;-) --><img src="{SMILIES_PATH}/icon_wink.gif" alt=";-)" title="Wink" /><!-- s;-) -->[/quote:uvlhigol]
Ah yes that's the "not safe for work" non beer part of the forum. There can be some odd stuff there alright. It is a US site after all!!

Beoir forum on mobile devices 14 years 8 months ago #10

you can say that again <!-- s:P --><img src="{SMILIES_PATH}/icon_razz.gif" alt=":P" title="Razz" /><!-- s:P -->

Actually this is probably still on topic of the title - whats the story with the tapatalk bug with double posts - seems to happen alot - hasn't hapened me yet though, i dont think. In fairness i dont use it too often.

Beoir forum on mobile devices 14 years 8 months ago #11

I think it's happening because people are sending their messages twice. If so, it's easy enough to work around: if you hit send and Tapatalk doesn't bring you to a screen with your new message on it, don't hit back and hit send again; hit back, copy your text, check if it posted the first time, and re-send if it didn't.

Beoir forum on mobile devices 14 years 8 months ago #12

Ahhhh I think you're right actually - i have seen occasions where after posting it comes back saying failed and if you go back in the post is there - so it was only the re-display of the thread that failed.
Good tip.
Time to create page: 0.132 seconds