Activity for BBPTeam
-
BBPTeam created a blog post
375
-
16.2025.03.1
-
374
-
16.2025.02.1
-
373
-
15.2025.12.1
-
372
-
371
-
15.2025.10.2
-
370
-
369
-
368
-
367
-
15.2025.10.1
-
366
-
365
-
15.2025.07.1
-
364
-
363
-
362
-
361
-
360
-
359
-
358
-
15.2025.03.1
-
357
-
356
-
355
-
Now, if you have Tor Browser Bundle, you can connect to a NULLNET over Tor within the Tor Browser Bundle. Open the darkNetDemo.zip file. Extract it to a folder of your choicec. Launch BlackBeltWASTE.exe. This is a portable solution connecting you to a NULLNET.
-
How, if you have Tor Browser Bundle, you can connect to a NULLNET over Tor within the Tor Browser Bundle. Open the darkNetDemo.zip file. Extract it to a folder of your choicec. Launch BlackBeltWASTE.exe. This is a portable solution connecting you to a NULLNET.
-
354
-
15.2025.01.1
-
353: We've been working to improve Upload-file-to-User. Users can remove all user-uploads if they wish or selectively choose whats being sent to them and throw the rest away. This is because 'Balloon Tip' notifications are not active elements on Linux WINE (v9). WASTE UI experience is now smoother under heavy load. The Dynamic Transfer Window has been increased to 10x what it was. This helps on Tor and i2p., where response times across the network are high. Transfers are up from ~200Kbps to up-to...
-
353
-
352
-
351
-
350
-
349
-
348
-
347
-
346
-
345
-
345: Encrypted RSA/Blowfish Chat targetting bug fix, for NULLNET’s where a default key is shared among users. These types of NULLNET’s are the simplest kind. The DarkBIOS NULLNET we use for support is this type of NULLNET.
-
445: Encrypted RSA/Blowfish Chat targetting bug fix, for NULLNET’s where a default key is shared among users. These types of NULLNET’s are the simplest kind. The DarkBIOS NULLNET we use for support is this type of NULLNET.
-
14.2024.11.1
-
344
-
14.2024.10.1
-
343
-
342
-
341
-
340
-
14.2024.08.2
-
14.2024.08.2
-
338 is now out. BBP team members recommended releasing as soon as ready.
-
338
-
OpenSSL is now at v3.0.14 : https://openssl-library.org/source/index.html Tor is now at v0.8.12 : https://forum.torproject.org/t/stable-release-0-4-8-12/13060 There will be a new version of BBP out to reflect this.
-
Hello Users, Build 337 had some of its resume code removed. We are refactoring and improving. It will be back in the forthcoming 338 build. Also, we are improving nick handling in the code. Build 338 will be released in the coming weeks.
-
14.2024.08.1
-
337
-
336
-
335
-
334
-
User Testing and Community Testing is still unearthing opportunities for improvements. We'll take these opportunities as we want this product to work well.
-
We are still noticing app freezes under linux (WINE) with volume transfers ( > 1000 ). We'll continue to work to resolve this.
-
333
-
332
-
331
-
Builds 329, 330 an the coming 331 are all focused on transfers at scale in both directions from Node A to B and B to A, in the regions of thousands of files. Resolving app freezes and lockup. The internal model is also tightened up in these releases. This yields better Transfer reporting, and Voice handling.
-
330
-
329
-
329 is being put through its paces ahead of imminent release.
-
WASTE is now much more capable of Backup of raw file systems, be they on Linux (WINE) or Windows.
-
We have also switched to POSIX compatible file I/O. This should ensure better behavior on Linux under WINE, a target audience.
-
We are also doing work to ensure that WASTE's internal systems multiplex properly together. We use a ton of timers within WASTE to ensure systems only operate when absolutely necessary. This technique enables a smoother operation, visible when operating at scale.
-
329 - will fix an Audio Bug that could see delays in the start of Audio Streaming. This could affect Voice Conferences.
-
We are likely to continue building WASTE until its behaving exactly how we+others want it. 328 - fixes a critical crash bug dequeuing files. Its also much smarter when queuing files between nodes. The AI within the AI Connect system is now set to fire at 30 second intervals. Down from 90 seconds. We may review this over time. It only fires when the bandwidth raises above a 1k byte per second floor. Thank you !!!!
-
328
-
327
-
We have also noticed that some compiler optimization options cause WASTE to fail. When under duress (4000 files from A to B and B to A simultaneously) WASTE could crash or freeze. As a result we have had to relax some compiler optimizations, resulting in a larger run-time on disk and slightly lower performance. A future 327 build will be coming once fully tested. Thank you for sticking with us !
-
We have been using WASTE at scale 4000-260,000 files transferring. At this scale WASTE could be smoother in operation. This is our current goal.
-
326
-
326
-
325
-
321
-
320
-
Stability of WASTE. Build 320. We have been doing very silly things to try and break WASTE. The worst we can think is killing the process mid file-transfer and dropping 1000's of files on chat windows and then killing the window before its finished :-P Both of these use-cases are catered for and stability fixes when bulk-transferring are included in Build 320. You should expect better behavior when bulk-transferring files in the order of 2000 to 1million+.
-
There is a slight correction we'd like to make. On inspection, WASTE IS 'dockerizable'. You must ensure the password is saved for auto-login and also the RNG within WASTE has been seeded. It's possible to then 'swarm' WASTE in docker images. WASTE has been specifically designed to sit happily in hub-spoke architectures or exotic ones that may arrive from docker mass-setups, if that's of interest to you. Have fun and please keep bringin' those ideas !!!
-
319
-
13.2024.06.2
-
318
-
317
-
We think you deserve a fuller answer in hindsight. We have been asked once in the 15 years this, and sister, project for WASTE have been running. This is a low frequency of requests. This is one reason why we have not taken IPv6 as something to focus on. We wanted rock-solid Tor and i2p connectivity though, which has always superceded a desire to see IPv6 supported. The code within WASTE allows for IPv6 addresses to be shipped about and handled internally, with minor modification. The trickier bit...
-
13.2024.06.1
-
Hello. We don't currently support IPv6 addressing. We haven't plans as yet to do so.
-
316
-
Hello, A NAS sounds exciting. Someone did once docker(ize) WASTE but as you noted, the GUI is required at key points. These are the RNG seeding when starting the profile and logging into the profile, unless the password has been saved. In summary WASTE doesn't play well with Docker.
-
Hello again Smiling Burrito, We were initially considering multi-source downloads. The conditions to allow it, within the WASTE 'way of doing things' would be very restrictive. You'd need multiple nodes with identical configuration for it to have a chance of working. This is not where we are likely to go. Also, multi-source downloading opens the door to poisoning of content. Something that is hard to combat. Its likely WASTE will remain point-to-point. We enjoy hearing from you, and would never consider...
-
Hello again Smiling Burrito, This is indeed odd behavior. The only option is to try and duplicate it somehow. Unfortunately we do not currently have a windows 11 test bed. If this behavior continues, please drop us a line and we'll try and get it duplicated.
-
315
-
312
1 >
