so i have meguca running on a server and have a homepage i made, is it possible to add more pages of html/css so the homepage leads to website.com/about with html/css i make?
Anonymous
Yes, but that requires programming.
Anonymous
Hmm, or if you are using a reverse proxy like Apache or Nginx, could just add the static page routes there. Yeah, that would be easier to do.
Thread for the future updating of the Koi Pixiv Extension. I now have ~70 weekly users on it so I feel I should start nailing out the bugs (the file extension bug in particular) As well as hopefully, maybe, adding a "manga viewer" that will allow for viewing the many pages of a multi image submission and being able to choose which of those images to download. Life and love is a work in progress.
>documentation WORSE It'll have to be some kind of UI tutorial. With idiot bubbles that tell people how to do things. I guess it's my fault for being lazy and scared of UI.
The best way to manage that is to make everything you want people to use turned on by default. And then hover an idiot bubble pointing to it. >Point to the wrench in the corner >Point to Sn and Iq and Ex above images >point to the X in the tab to tell people to gtfo
That said, I don't actually know how to make those things and I think it'll be vastly easier to just HIJACK the current UI as I've been doing and edit the text to explain how to use it. I also need to make an update that tells people what submissions are multi-image before they click to download.
First the basics ow websockets. Once everything is established, websockets come and go both ways in frames. I am thinking of having all our frames be binary. Ideas so far. >first byte determines message type (uint8) >parsing can be done by itteraring a switch statement over an array (for complex structs with optional fields) >fixed format messages can just be passed to a function
More on parsing structs with optional fields: >in optional field structs, each field starts with a type byte, similar to messages >if a field is constant length, it can be followed by another field just like that >if a field is dynamic length (strings, slices) it ends with a null byte (this is probably problematic and needs more thought; maybe defined field order something)
That is all I have for now. Implementation on the JS side can parse the ArrayBuffer directly returned by the websocket into a DataView or typed array. I have not looked into the two API yet. Any thoughts?
Anonymous
I have an idea, instead of all these optional fields, why not have a post message type and post with image message type. And a separate image type. In each of those, a certain field would have a certain position in the array. If a field is empty, it's length uint16 will be zero. I think this will save us space and complexity. Or better yet, we can have a defined order of fields. At the start of the message there will be a byte or so that specifies which fields are present in the message. So much optimisation could be done.
Some optimisations to the Image struct can also be done. We can have one image field, that stores the extension // name of the image resource and make mid thumbnails mandatory for all images. Src, Mid and Thumb can all be derived from Image and Ext, Ext can be a uint8, instead of a string. I don't this will be easily migratable from the current meguca, but oh well. Or the migration script would have to be pretty complex.
Now the optional fields on Post are Name, Trip, Email, Auth, Backlinks and Links. That's 6 and can fit nicely in a byte. Image has only the Length field optional after refactoring, so that's not much of a concern. In fact the seventh byte inside the optional // the 7th bit inside the optional field byte can be Image presence. So an Image will be tacked on to the back of message and have no optional fields of itself. An empty length can just be null. at the end of the struct.
This is so much fun figuring out.
Anonymous
Right, JS now has binary literals. Forgot about those.
I have decided to stick to JSON strings for now, until protobuf gets an official JS implementation (currently in alpha). When it does, I can switch both the Websocket and JSON APIs to protobuf.
how can i have a banner only appear on one board? I know its going to be fixed in Meguca V2 but i really want to hack something together to make it work now. different boards on my instance are accessed through different domains i was thinking i could use that to make the banners know which one to load?
>>1490194 Can you show me your idea in mockup? I'm author of CatChan(>>1355772) and I'll add "a board select function from banner" 2-3 months later. If your demand is similar to mine, I'll add it with priority.
Ah, I see. So when encoding a struct to JSON explicitly nilled values are treated as empty, with the "omitempty" tag. https://play.golang.org/p/En2HJZCy6o
Anonymous
https://twitter.com/brianhatfield/status/692778741567721473 This is looking really good
Hello, I'm author of CatChan, which is a script which can generate cross board/domain catalog with tag filter. Do you admin want meguca to be supported by this script?
About 3: Use boards group. 3-1. CC -> settings -> Board Group 3-2. Write in it, for example, meguca_all,meguca/a/,meguca/an/,meguca/cr/,meguca/g/ mecuga_4chan_a,meguca/a/,4chan/a/ 3-3. Select them, for example, meguca_all (Pic.7)
Anonymous
I'm going to make a bug report to chromium projects about memory leak, and its reproduce code contains url of meguca. If you have any inconvenience with this, let me know in 2 days. It's easy to replace it, but then I must re-check reproducibility.
Because you know I only code when it helps me fap. I got the majority of it working for meguca already. All I need now is to make it work whenever a post closes rather than just on page load. I should test to see if it works that way on 4chan already now that I think about it. Maybe the functionality I need is already in here.
What was the point of RS again...? something about persistent history maintenance Because it's as if it causes everything I write for meguca to break on page change.
