No real organization....
testing6 replies and 1 images, Click here to view all.
>tfw no gf6 replies and 1 images, Click here to view all.
>>https://0x00000000.xyz/b/159C3F2G Are you being picky with a girl to be your girlfriend? I'm sure there is a girl out there for you anon. But some who say they have no girlfriend or cant get one usually are picky on the girls they like.
>be me >write life story >attach svg image >fatal mistake >post gets eaten by fchan
>>https://fchan.xyz/prog/1PWMGYAK The MIME types was referenced from here https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#svg The supported files from the faq at the bottom are "image/gif","image/jpeg","image/png","image/svg+xml","image/webp","image/avif","image/apng","video/mp4","video/ogg","video/webm","audio/mpeg","audio/ogg","audio/wav", "audio/wave", "audio/x-wav" If the mime type differs from this it will not upload. svg formats were not tested to catch alternative mime types, but they can be added.
bottomtext14 replies and 5 images, Click here to view all.
fchan uses 8-digit hexadecimal numbers as post ids. This means that there are 16^8 = ~4.3 billion unique ids. This is not that big of a number. What's worse, these IDs are selected at random. The birthday paradox states that a 50% chance collision occurs at sqrt(n), which in this case is only sqrt(16^8) = 65536 posts. 65 thousand posts, after which the federated chan network becomes a complete clusterfuck. If you can't even rely on your id being unique, why bother with an id system at all?8 replies and 2 images, Click here to view all.
>>https://0x00000000.xyz/b/3ZESC121 from the FAQ at bottom >sequential numbers have run their course. random base 16 (now base 36) is better. according to OPs concern there would be even more collisions with seqential numbers. What happens when two federated instances have the post 1,2,3,4,5,6,7,100,234,21003? But even with sequential numbers what makes a post unique is the domain it comes from so nothing would happen. Any instance is free to change their IDs to any system they like
>>https://fchan.xyz/b/EK49ITBG You sure the IDs aren't chosen from a pre-determined randomized order? Say every possible ID was stored on file somewhere (which would only be ~4.3GB without extra data) and shuffled them around. An index of the next ID to use could be stored somewhere else, and be incremented every time someone makes a post. No more chance of collision. I agree 16^8 is rather small for an ID size, but in all seriousness it's not something to be worried about now. For the sake of argument, say this board got the same 1,000,000 posts a day that 4chan gets (https://www.4chan.org/advertise). Let's also assume that this board generates the IDs with no chance of collision using the method I mentioned before. At 1M posts per day, this board could go over 11 years without running out, and that's with 4chan level traffic. Worst case scenario and there weren't any more IDs for some reason, it isn't that hard to increase the ID size and create a new pre-determined list of IDs.
Did you really think you could escape me iToddlers? Lol. ITODDLERS ETERNALLY BTFO25 replies and 6 images, Click here to view all.
Is this the final red pill?6 replies and 1 images, Click here to view all.