Latest Announcemnent
New thread

Byse Discussion

Byse

Byse

Active Member
Corporate Membership
1,069
2022
862
13,780
Hello,

This is not official thread, we came with this thread in order to transition into new platform correctly, feel free to report any bugs or share your thoughts and suggestions about our new system in this thread.
 
788 comments
5nkl.png

I prefer to go back up, small bug in “Processed” (Jan 1, 1, 12:09 AM) when it's requested at the end of February ^^.
After that, it may be normal, but I prefer to go back up. @Byse
 
I've always defended Byse, but now I think it's dying.

The remote upload API isn't working.
The premium plan is impossible to buy.
Numerous service interruptions in the last 10 days.
Support tickets are ignored every day.

I believe it's over.
 
kamikaze1997 said:
I've always defended Byse, but now I think it's dying.

The remote upload API isn't working.
The premium plan is impossible to buy.
Numerous service interruptions in the last 10 days.
Support tickets are ignored every day.

I believe it's over.
Click to expand...
I don't know others but at least for me the earnings are frozen, I usually switch bewteen custom ads and platform ads from time to time, after switching back to platform ads for 2 days, the earnings didn't go up a cent...
 
kamikaze1997 said:
I've always defended Byse, but now I think it's dying.

The remote upload API isn't working.
The premium plan is impossible to buy.
Numerous service interruptions in the last 10 days.
Support tickets are ignored every day.

I believe it's over.
Click to expand...

Everyone definitely misses Filemoon :(

Byse is really disappointing for some users, but I think they'll fix the issues over time since they're still in beta.
 
Byse API - Bug Reports & Feature Requests

1. BUG: file/set_folder returns "Invalid operation"The documented endpoint file/set_folder (for moving files to folders) returns {"msg": "Invalid operation", "status": 400}. Tested with valid key, file_code, and fld_id parameters.

2. BUG: file/edit with fld_id doesn't workfile/edit?key=...&file_code=...&fld_id=123 returns {"status": 200, "result": "true"} but the file's fld_id remains unchanged (still 0). The API says OK but nothing happens.

3. BUG: file/clone with fld_id clones instead of movingAccording to API docs, file/clone?key=...&file_code=...&fld_id=123 should be "File Set Folder - Moves a file into the specified folder." In reality, it creates a duplicate file with a new file_code in the target folder. The original file stays at fld_id=0. This doubles storage usage instead of simply moving the file.

4. BUG: file_length metadata is unreliableSome files report file_length: 2555 (42 minutes) in the API but only play 3 minutes 19 seconds in the actual player. The canplay: 1 flag is also set for these broken files. There's no way to detect corrupted files through the API.

5. MISSING: No file/delete endpointfile/delete returns "Invalid operation". There's no way to delete files through the API.

6. MISSING: No file_size in API responsesNeither file/info nor file/list return the file size (in bytes/MB). This would be useful for verifying upload integrity and detecting corrupted/incomplete uploads.

7. SUGGESTION: Add a real file/move endpointA simple endpoint to move a file to a different folder without cloning: file/move?key=...&file_code=...&fld_id=123

8. SUGGESTION: Add file health/integrity checkAn endpoint or flag that indicates whether a file is fully intact and playable (not just canplay which can be true for broken files). Something like file_healthy: true/false or actual playable duration vs reported duration.
 
Back
Top