Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


IkarosBD last won the day on April 19

IkarosBD had the most liked content!

Community Reputation

645 Trusted

About IkarosBD

  • Rank
    LostYears Distro/Xertion IRC Network Root Administrator

Profile Information

  • Gender
  • Location
    Texas USA

Recent Profile Visitors

13,771 profile views
  1. As you are all aware by now, a server maintenance was conducted today to update the webserver and underlying TLS library that provides secure connectivity to our network of sites. Part of this upgrade, was the addition of support for the newly created TLS version 1.3. This new protocol version is supported by the latest versions of both Firefox and Chrome, and should already be enabled by default in those browsers, so if you're using the latest versions of either browser, you should now be using TLSv1.3 transparently. However, with this change, we have to also make a change to some of the older ciphers we currently support on Kametsu. Right now, we maintain a relatively sane degree of backwards-compatibility to account for older browsers. Now that we have TLSv1.3 enabled, this has to be revised. We've already disabled support for TLSv1.0, and on December 16th, 2018 - we will be making the following changes to our supported TLS cipher suites/parameters: Plain DHE (Diffie-Hellman Exchange)-based cipher suites will be completely disabled. We will only support ECDHE (Elliptic Curve Diffie-Hellman Exchange)-based suites. DHE is still relatively secure provided you use a decent-sized key, but its performance is generally lower than that of its EC-based counterpart especially with higher key sizes. TLSv1.1 will be disabled, and TLSv1.2 will become the minimum supported. The older Cipher Block Chaining (CBC) cipher suites will be depreciated and ultimately removed, in favor of the superior Galois/Counter Mode (GCM) cipher suites. These changes, especially 2 and 3, will mostly impact users on older operating systems and/or those using older/obsolete browsers (such as Internet Explorer on anything other than Windows 10, for example). These users will likely see their ability to connect to the site disappear once these changes take effect. For those of you using older operating systems and/or browsers - I implore you to update your systems and/or your browsers to the latest available versions to ensure you are still able to connect to Kametsu without a problem. If you have any concerns, please let me know. I do have a very busy work schedule so I can't always guarantee a timely response but I'll make every effort to respond to every concern raised regarding these upcoming changes.
  2. LostYears' SSSS.GRIDMAN ep 3 will be released later tonight. Einherjar batch will be done Saturday morning. Sorry for the delays, I'm dealing with quite a bit at the moment.

  3. Sorry guys I'm just really out of it today. Lot of personal issues I'm having with certain individuals, leading to a lack of motivation to do anything.


    And yes, my XDCC bot is down. Don't ask why. Personal issues.

    1. LelouchVBritannia


      May god resolve your personal issues very soon 😇.

    2. Pizza Cat
  4. Quick question for all: Would you like to see more from me, such as maybe adding another method or two of grabbing LostYears releases aside from XDCC and torrents?

    1. Show previous comments  5 more
    2. LelouchVBritannia


      That's great 😍.


      I misunderstood & thought that u were gonna remove Torrents & XDCC 😅.

    3. LelouchVBritannia


      I would like to see MEGA & Google Drive as those new methods.

    4. (AC)


      I would like a new HDD with every ly series on it posted straight to meh

  5. LAAAAAG (when exiting a game such as GTA V)...





  6. Due to continued server problems at AniDex - our automated XDCC fetching is not currently functioning at this time. New releases for LostYears are especially affected by this and will likely not be transferred to XDCC until our XDCC bot owners are able to transfer the files manually from other sources (or we get lucky and AniDex somehow responds during a feed check). We apologize for the inconvenience.

    1. DigiPokeMon


      Have you contacted anidex to let them know about this problem?



    2. Koby


      @DigiPokeMon Holo has been contacted numerous times but apparently fails to ever respond about the lack of stability.

  7. I am in an IMMENSE amount of pain right now. It hurts more when I'm up and walking after 3-4 minutes, mostly in my lower back.


    That is why I'm minimizing my activity at this time. I will be cutting back on any non-work activity (including the IRC network and the forums) so my back can get proper rest.

    1. Show previous comments  2 more
    2. DRX


      Get better, that's the important part

    3. LelouchVBritannia


      I hope that u recover soon.

    4. Nabull


      How you doing now?

  8. Just an FYI: I've done some reorganizing of the Discord server roles. I THINK I got everyone's roles correctly assigned. However, if you're a member of our Discord server, could you please go there and check your current assigned roles to make sure I didn't miss anything? If I did (e.g you're supposed to have the Donator role, for example, or Uploader, or something else), please let me know. Thanks.

    1. Show previous comments  1 more
    2. IkarosBD


      Sorry @NeutralHatred you cannot be a bot. You do not meet the qualifications. :P

    3. ElectricAngel


      I just got the uploader role and I'd like for it to be added to the Discord please 😄 (ElectricAngel#8461)

    4. Nabull


      Why do I not have a special role? 


  9. *sigh*

    1. Show previous comments  7 more
    2. Nabull


      Time for Pollux's promotion 

    3. Pollux
    4. Nabull


      I'm sorry, I don't remember asking you

      Now start banning people go go go

  10. A quick note to everyone: I will be taking a hiatus from administration. This is due to a number of things, but I also did sort of warn this could happen back at the end of May, and it's looking like that, in order to maximize my productivity at work, it is necessary.


    I haven't yet decided if I'm leaving administration entirely. I do not yet feel that itself is necessary. But I do feel my ability to make fair decisions is impacted by my work schedule and the lack of sleep caused by it.


    Effective immediately, I will no longer be handling forum matters for a period of 2 months. I will continue to perform regular work on the server itself. Just not on the forums.

    1. Show previous comments  7 more
    2. NeutralHatred



      You should see a doctor first about that cough. Sounds pretty bad.

    3. (AC)


      too much AC in here catching a cold

    4. NeutralHatred


      That was absolutely terrible. Please try again.

  11. Apologies for the sudden downtime. A pretty nasty issue was noticed with the webserver during routine updates, that necessitated its downtime in order to fix the problem. This specific problem was related to the webserver log files not rotating properly and thus were consuming excessive amounts of disk space.


    The webserver had to be stopped in order to move the log files out of the way.

    1. LelouchVBritannia


      Maintaining server is such a hassle.

  12. IkarosBD

    Private Messages not removed

    Ok, looking at the database (and doing a little date-time conversion since the timedate is stored in UNIX style timestamps), each of the conversation IDs you've given me have a last-active-at age of 1 year or greater. I'd like your permission to manually delete these IDs for you (since I'd be doing more than one this time). Note that I may not actually be able to get to it today as I have full-time work I must rest up for, but rest assured I'll poke at it Mon/Tues at the very least in the evenings (probably around 7:30 PM CDT). EDIT: I've TEMPORARILY increased your inbox size. Once I resolve the issue, I'll restore its original size.
  13. IkarosBD

    Private Messages not removed

    Yes that corresponds to a conversation ID. See if you can get me some more conversation IDs that are failing to delete.
  14. IkarosBD

    Private Messages not removed

    @misseps - I was able to delete a few of my older PM conversations fine, and the counters properly updated. No errors are being thrown in the backend far as I'm able to tell (and believe me we log EVERY error that gets thrown!). For your case I went directly into the database, found an old conversation ID (note: NOT the actual conversation itself, I can't actually read your PMs), and deleted any references from the database that referenced that conversation ID AND your user ID. You should probably notice that one conversation now missing from your list. Could you try deleting another single conversation for me? I'm starting to zero in on what I THINK the problem could possibly be.
  15. IkarosBD

    Private Messages not removed

    I can see if any errors were thrown in the backend. I haven't been able to look at the site as literally the only free time I have to do things with it is on Saturdays, and I'm really one of the only ones who can dig that deeply. I'll take a look at it Saturday and get back to you.