Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

TRENDING NOW: RackNerd’s BLACK FRIDAY! NEW DEALS, NEW LOCATIONS, NEW HARDWARE + 100’s of GIVEAWAYS!

1135713581360136213631678

Comments

  • @noob404 said:

    @PuDLeZ said:

    @noob404 said:
    True, but, for testing purposes, I believe you can most conveniently use a closed thread as well, if I am not wrong. Even if not, you should be fine, cause if I remember, the NY thread stays for a long time and is prolly closed only when a new thread is up.

    Yeah, I mean it will only be reads but I don't want to deal with all these comments/pages right away in case I want to change the entries I put into a DB. Plus, there won't be much activity afterwards so I wouldn't be able to truly verify it picks up on the last page it previous did. I mean all else, I could use some other random thread on LET that I know will get comments/multiple pages. I mean they will be perfect for making sure I have all the core logic down. Searching for dub requests/etc. would just be find the proper DB query.

    Oh, you are right. The activity might not be the same as these months. Anyways, I wish you luck.
    BTW, what are you planning to use - Python?

    probably node

  • @PuDLeZ said:

    @noob404 said:

    @PuDLeZ said:

    @noob404 said:
    True, but, for testing purposes, I believe you can most conveniently use a closed thread as well, if I am not wrong. Even if not, you should be fine, cause if I remember, the NY thread stays for a long time and is prolly closed only when a new thread is up.

    Yeah, I mean it will only be reads but I don't want to deal with all these comments/pages right away in case I want to change the entries I put into a DB. Plus, there won't be much activity afterwards so I wouldn't be able to truly verify it picks up on the last page it previous did. I mean all else, I could use some other random thread on LET that I know will get comments/multiple pages. I mean they will be perfect for making sure I have all the core logic down. Searching for dub requests/etc. would just be find the proper DB query.

    Oh, you are right. The activity might not be the same as these months. Anyways, I wish you luck.
    BTW, what are you planning to use - Python?

    probably node

    Oh good. Let me know if I can help with the testing or such.

  • @noob404 said:

    @PuDLeZ said:
    I have opened up a notepad and made a note about all the data I should capture

    • comment id
    • username
    • timestamp
    • comment text/string
    • is comment a reply
      -- who the user replied to
      -- comment id that was replied to

    I'dunno though, just what I quickly made notes on. Only added the reply thing because I think it would be interesting to also have a way to see like "PuDLeZ most replied to noob404" or similar type things. Though I wouldn't be generating those details constantly, maybe like an "end of day" type of thing at most. Either way, just trying to think of everything right away...

    The reply to thing sounds cool. BTW, trk was asking for suggestions, and I recommended post count prediction, as well. I mean how many comments would the person have at their current pace on a set date. Dunno how hard it is to implement though.

    No clue either though I think it would be all about the data that's getting captured. Now that's I'm thinking about it, I don't really need the "who the user replied to" since I would be capturing the comment id and I could always just lookup the username from it. I'dunno, that's why I started to "scribble" some notes on it. Programming isn't my day job so I have to think about it more than someone who is one.

  • @noob404 said:

    @PuDLeZ said:

    @noob404 said:

    @PuDLeZ said:

    @noob404 said:
    True, but, for testing purposes, I believe you can most conveniently use a closed thread as well, if I am not wrong. Even if not, you should be fine, cause if I remember, the NY thread stays for a long time and is prolly closed only when a new thread is up.

    Yeah, I mean it will only be reads but I don't want to deal with all these comments/pages right away in case I want to change the entries I put into a DB. Plus, there won't be much activity afterwards so I wouldn't be able to truly verify it picks up on the last page it previous did. I mean all else, I could use some other random thread on LET that I know will get comments/multiple pages. I mean they will be perfect for making sure I have all the core logic down. Searching for dub requests/etc. would just be find the proper DB query.

    Oh, you are right. The activity might not be the same as these months. Anyways, I wish you luck.
    BTW, what are you planning to use - Python?

    probably node

    Oh good. Let me know if I can help with the testing or such.

    Well like I said, right now it's just thinking about it and hopefully I get some time/feel like it over Christmas to do it. I mean, even if it's not perfect, it would still be nice to test it out while the NY thread is active. Worst case, I will have something for next year

  • @PuDLeZ said:

    @noob404 said:

    @PuDLeZ said:

    @noob404 said:

    @PuDLeZ said:

    @noob404 said:
    True, but, for testing purposes, I believe you can most conveniently use a closed thread as well, if I am not wrong. Even if not, you should be fine, cause if I remember, the NY thread stays for a long time and is prolly closed only when a new thread is up.

    Yeah, I mean it will only be reads but I don't want to deal with all these comments/pages right away in case I want to change the entries I put into a DB. Plus, there won't be much activity afterwards so I wouldn't be able to truly verify it picks up on the last page it previous did. I mean all else, I could use some other random thread on LET that I know will get comments/multiple pages. I mean they will be perfect for making sure I have all the core logic down. Searching for dub requests/etc. would just be find the proper DB query.

    Oh, you are right. The activity might not be the same as these months. Anyways, I wish you luck.
    BTW, what are you planning to use - Python?

    probably node

    Oh good. Let me know if I can help with the testing or such.

    Well like I said, right now it's just thinking about it and hopefully I get some time/feel like it over Christmas to do it. I mean, even if it's not perfect, it would still be nice to test it out while the NY thread is active. Worst case, I will have something for next year

    and honestly, until I'm sure it's properly capturing all the data/etc, I'm not even going to have a webpage to display it or anything. To me, the important thing is just getting the data into a db as everything else depends on the data

    Thanked by 1BasToTheMax
  • @PuDLeZ said:

    @noob404 said:

    @PuDLeZ said:

    @noob404 said:

    @PuDLeZ said:

    @noob404 said:
    True, but, for testing purposes, I believe you can most conveniently use a closed thread as well, if I am not wrong. Even if not, you should be fine, cause if I remember, the NY thread stays for a long time and is prolly closed only when a new thread is up.

    Yeah, I mean it will only be reads but I don't want to deal with all these comments/pages right away in case I want to change the entries I put into a DB. Plus, there won't be much activity afterwards so I wouldn't be able to truly verify it picks up on the last page it previous did. I mean all else, I could use some other random thread on LET that I know will get comments/multiple pages. I mean they will be perfect for making sure I have all the core logic down. Searching for dub requests/etc. would just be find the proper DB query.

    Oh, you are right. The activity might not be the same as these months. Anyways, I wish you luck.
    BTW, what are you planning to use - Python?

    probably node

    Oh good. Let me know if I can help with the testing or such.

    Well like I said, right now it's just thinking about it and hopefully I get some time/feel like it over Christmas to do it. I mean, even if it's not perfect, it would still be nice to test it out while the NY thread is active. Worst case, I will have something for next year

    In any case, it's a cool project. I would be interested in seeing how it turns out.

  • @PuDLeZ said:

    @PuDLeZ said:

    @noob404 said:

    @PuDLeZ said:

    @noob404 said:

    @PuDLeZ said:

    @noob404 said:
    True, but, for testing purposes, I believe you can most conveniently use a closed thread as well, if I am not wrong. Even if not, you should be fine, cause if I remember, the NY thread stays for a long time and is prolly closed only when a new thread is up.

    Yeah, I mean it will only be reads but I don't want to deal with all these comments/pages right away in case I want to change the entries I put into a DB. Plus, there won't be much activity afterwards so I wouldn't be able to truly verify it picks up on the last page it previous did. I mean all else, I could use some other random thread on LET that I know will get comments/multiple pages. I mean they will be perfect for making sure I have all the core logic down. Searching for dub requests/etc. would just be find the proper DB query.

    Oh, you are right. The activity might not be the same as these months. Anyways, I wish you luck.
    BTW, what are you planning to use - Python?

    probably node

    Oh good. Let me know if I can help with the testing or such.

    Well like I said, right now it's just thinking about it and hopefully I get some time/feel like it over Christmas to do it. I mean, even if it's not perfect, it would still be nice to test it out while the NY thread is active. Worst case, I will have something for next year

    and honestly, until I'm sure it's properly capturing all the data/etc, I'm not even going to have a webpage to display it or anything. To me, the important thing is just getting the data into a db as everything else depends on the data

    Oh, alright. So, mostly backend stuff. Good luck, Pudlez. Gotta get started with my morning chores, a few calls for work and emails, and get some work done as well. I will see you later.

  • Hello, I would like to double my bandwidth.
    invoice #19377261
    Thanks!

  • Hello, I would like to double my bandwidth.
    Invoice #19906971
    Thanks!

  • @noob404 said:

    @PuDLeZ said:

    @PuDLeZ said:

    @noob404 said:

    @PuDLeZ said:

    @noob404 said:

    @PuDLeZ said:

    @noob404 said:
    True, but, for testing purposes, I believe you can most conveniently use a closed thread as well, if I am not wrong. Even if not, you should be fine, cause if I remember, the NY thread stays for a long time and is prolly closed only when a new thread is up.

    Yeah, I mean it will only be reads but I don't want to deal with all these comments/pages right away in case I want to change the entries I put into a DB. Plus, there won't be much activity afterwards so I wouldn't be able to truly verify it picks up on the last page it previous did. I mean all else, I could use some other random thread on LET that I know will get comments/multiple pages. I mean they will be perfect for making sure I have all the core logic down. Searching for dub requests/etc. would just be find the proper DB query.

    Oh, you are right. The activity might not be the same as these months. Anyways, I wish you luck.
    BTW, what are you planning to use - Python?

    probably node

    Oh good. Let me know if I can help with the testing or such.

    Well like I said, right now it's just thinking about it and hopefully I get some time/feel like it over Christmas to do it. I mean, even if it's not perfect, it would still be nice to test it out while the NY thread is active. Worst case, I will have something for next year

    and honestly, until I'm sure it's properly capturing all the data/etc, I'm not even going to have a webpage to display it or anything. To me, the important thing is just getting the data into a db as everything else depends on the data

    Oh, alright. So, mostly backend stuff. Good luck, Pudlez. Gotta get started with my morning chores, a few calls for work and emails, and get some work done as well. I will see you later.

    yeah, backend is all I'm going to care about right away. Have fun with those calls! Hopefully you don't need to be on webcam like some of my meetings. I find it annoying because the main folks that always want them on are ones that don't want you to be doing anything else during it but they want you to do stuff for them/instantly reply when you're in other meetings. I've actually made it a point to ignore their DMs while I'm in a meeting, even if I'm multitasking with other things.

  • Hello, I would like to double my bandwidth.
    Invoice #19996095
    Thanks!

  • Hello, I would like to double my bandwidth.
    Invoice #5995283378
    Thanks!

  • Hello, I would like to double my bandwidth.
    Invoice #19995675
    Thanks!

  • Hello, I would like to double my bandwidth.
    Invoice #19995528
    Thanks!

  • Hello, I would like to double my bandwidth.
    Invoice #1205533041
    Thanks!

  • Hello, I would like to double my bandwidth.
    Invoice #19993218
    Thanks!

  • Hello, I would like to double my bandwidth.
    Invoice #6249454263
    Thanks!

  • Hello, I would like to double my bandwidth.
    Invoice #19992357
    Thanks!

  • Hello, I would like to double my bandwidth.
    Invoice #19992105
    Thanks!

  • Hello, I would like to double my bandwidth.
    Invoice #1273612840
    Thanks!

  • yangyang is like "I'm not out of this engagement competition yet!" :lol:

  • Hello, I would like to double my bandwidth.
    Invoice #19989648
    Thanks!

  • Hello, I would like to double my bandwidth.
    Invoice #19990698
    Thanks!

  • Hello, I would like to double my bandwidth.
    Invoice #19990341
    Thanks!

  • Hello, I would like to double my bandwidth.
    Invoice #19993785
    Thanks!

  • yangyang with more posts

  • Hello, I would like to double my bandwidth.
    Invoice #19886349
    Thanks!

  • @freeprogram said:
    Hello, I would like to double the bandwidth.
    Order: 1417638287
    Thanks!

    Order Number: 1417638287
    Invoice ID: #19586552

  • Well, I'm off to bed. Hopefully there's on when I get online!

Sign In or Register to comment.