[ home / bans / all ] [ qa / jp ] [ spg ] [ f / ec ] [ b / poll ] [ tv / bann ] [ toggle-new / tab ]

/b/ - Boson Technology

Also known as Boson /g/

New Reply

Options
Comment
File
Whitelist Token
Spoiler
Password (For file deletion.)
Markup tags exist for bold, itallics, header, spoiler etc. as listed in " [options] > View Formatting "


[Return] [Bottom] [Catalog]

File:c752b1f0c9.png (13.39 KB,290x362)

 No.5941[View All]

this makes me want to cry...

also why is it more annoying to input an embed file now
115 posts and 42 image replies omitted. Click reply to view.

 No.6085

>>6080
Made a fix for it, but it won't be up until I release update 2.1.0

 No.6087

File:wut.jpg (30.12 KB,1440x620)

When I visit /qa/ (and only /qa/, the rest of the boards are fine) I get pic related. It's perfectly normal under the vichan interface, which means it must be caused by the new UI.

 No.6088

>>6087
going to need better information than that...

- browser and version
- are you running javascript
- can you get into your dev console and show me any errors

 No.6089

>>6088
-Pale Moon 28.17.0 64 bit on Windows 10
-Yes
-I can, but it doesn't say that there's any errors

 No.6090

>>6089
well it certainly is an epic bug

I will switch over to windows and see

 No.6091

I'm getting this error you talk about. It's very odd..

 No.6092

File:d2873dccc4.png (84.52 KB,1920x1040)

>>6091
think I found the problem

 No.6093

>>5941
In my opinion, having the banners like they are now kind of ruins them. They work so well on the vichan interface because they're just kind of sat there. It felt like a fun parody of banner ads that fell in line with the site's sense of humor by being silly instead of mocking.

 No.6094

>>6093
that talking points' been covered already. It's going to be moved in tomorrow's work session

 No.6096

File:d8bc3bafff.png (49.16 KB,620x186)

Looking nice, only thing really left visually is this

 No.6098

>>6097
Or just remove OP highlighting altogether.

 No.6099

>>5941
New update's pretty great!

 No.6100

File:Untitled.jpg (7.88 KB,225x73)

The notification-ey-thing (not sure what to call it) at the top of the page covers up the >> when you have the sidebar hidden.

 No.6103

THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.
THERE IS STILL NO REPLY FORM.
YOU HAVE NOT ADDED BACK THE REPLY FORM.
ADD BACK THE REPLY FORM.

 No.6104

>>6103
Not vermin, but I'm not sure how necessary it is to have it when the quick-reply box does basically the same thing. Most imageboards have both, but that's less because it's a good design choice and more because everyone either uses or mimics the vichan, which itself (or more properly tinyboard) was just a clone of yotsuba with the 4chan x extension.

Taking tradition out of the equation, I feel like it's actually pretty poor design. You have two fairly prominent UI elements that both do the exact same thing. One of the two methods is generally better than the other, but it's hidden by default, while the inferior one is the first thing you see when you load the page.

 No.6105

>>6103
please stop shouting

 No.6107

>>6104
BAD DESIGN IS HAVING NO FIXED POSITION FOR A REPLY FORM.
BAD DESIGN IS HAVING CLUTTER ALL OVER YOUR READING SPACE.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.
WE HAVE BEEN THROUGH THIS.

 No.6114

File:3A76EA50-FF6C-470F-972D-3….jpeg (103.29 KB,1080x1080)

why are codemonkeys so concerned with [other thing] when we still cant effectively hide threads (and not see them in catalogue).

try hiding this post. You cant!!!1! pissmin doesnt even have this feature

 No.6121

File:GbP6NQF.png (287.8 KB,1856x942)

I might need to place a post form at the bottom of threads. The void between thread and footer is too jarring. Given that similar threads won't appear without a certain post threshold it seems like the only option

 No.6122

>>6114
You can hide it with 4chan X. Oh wait, that's a phone filename. Uhh...
Yeah, that'd be a good idea

 No.6125

File:4JJSfOD.png (255.84 KB,1072x785)

i don't like the idea of having it as much as it being a buffer between content and footer that will conveniently appeal to some people

 No.6126

a bit of redundancy in this feature isn't a bad idea anyways

 No.6131

I love having the reply box at the bottom. I'm honestly surprised that there aren't more imageboards that do this sort of thing.

 No.6132

There should be links to things like the catalog on the sidebar.

 No.6133

>>6132
what if it doubles down on redundancy and the sidebar also has everything in the main column. This was done in the original design

 No.6162

*smacks the toggle to classic ui button*
ah much better

 No.6163

>>6162
I'd do the same thing even if the ui was more functional. I'm just too stubborn to learn new things.

 No.6164

Unless there's something i can change I'm going to start thinking about something else to do. I am a bastard incapable of self-reflection.

 No.6165

File:[SubsPlease] Yuru Camp S2 ….gif (182.12 KB,360x441)

json api stopped working again

 No.6166


 No.6167

>>6165
oops

 No.6168

>>6165
works again

 No.6169

this is fucking bullshit looking, how do you manage to ruin your site design so easily?

 No.6170

>>6169
What's wrong with it, elaborate

 No.6171

>>6170
Too boxy, too much clutter, doesn't update any post after being made.
Thank god we can change back to the older style because it's barely functional.

 No.6172

File:kissu.png (184.33 KB,979x423)

Being welcomed to this is the best feeling

 No.6173

>>6172
sick screen height. Guess I need to add more conditionals

 No.6174

I think I'm going to finally kill the floatbar, I can't get it to work and I don't think there's anything I'd be able to put anything worthwhile in it.

 No.6175

>>6168
api only seems to work with the "ui" cookie that's set when you toggle the UI

 No.6176

>>6175
Check again, it works in all configurations

https://kissu.moe/b/res/5941.json
was my test

 No.6177

oh, i think you mean using /qa/thread/4165.json

Alright, I'll add that

 No.6178

File:1.png (56.71 KB,932x794)

>>6177
i thought that was it at first too but it's not that

 No.6179

>>6178
ah, i see

 No.6180

>>6179
it's something easy to patch on my end but it seems like something you should patch because requiring that cookie is no longer vichan api

 No.6181

whatever you did fixed it
thanks

 No.6182

I wanted to get /b/thread/5941.json to work in case, but that's seeming to be harder than i thought with all the rules in the server block

 No.6183

will replace the floatbar concept with a window that appears on page startup when there's a new news item.

This will contain the message of the day concept that was attached to the vichan UI and reduce the number of info messages on first load.

 No.9133

the good old days...

 No.11305

yes, this was quite bad, but I was still in the right

 No.11306

It surprises me just how recent the current implementation of the custom UI is. I always think it was introduced earlier than it actually was. I guess that speaks to how good of a design it is.




[Return] [Top] [Catalog] [Post a Reply]
Delete Post [ ]

[ home / bans / all ] [ qa / jp ] [ spg ] [ f / ec ] [ b / poll ] [ tv / bann ] [ toggle-new / tab ]