[help] [img] [forum]
[Catalog] · [Search] [News] [Manage]
Post thread
Name
Email
Subject
Message
CAPTCHA CAPTCHA Challenge Click to refresh.
File
Password For post deletion.
Submit  
  • Helpful information is available in the visitor guide. Currently 10 unique user posts.
  • Supported file types are JPG, PNG and GIF.
  • Maximum file size allowed is 2MB.
  • Images greater than 250x250 will be thumbnailed.
  • Supported BBCode tags are b, code, i, pre, sjis, spoiler, s and u.

1782863975405.jpg
 [Reply]
Welcome to /help/, a board where you can get official and unofficial support for the Sriracha imageboard and forum server.

Feel free to share any questions or feedback related to Sriracha here.

If you found a bug in an official release of Sriracha, and you aren't using any custom templates, please report it by opening a new issue in the Sriracha repository.

If you aren't sure whether you found a bug, or if you are using custom templates, this is the place to ask for assistance.

If you are having problems with creating custom templates, I recommend asking for help in a Go programming language support channel instead, because the issue is likely not specific to Sriracha.

Please do not include any external links in your message. Keep all messages and attachments on-topic. Feel free to share screenshots of issues or mock-ups of suggestions.


1786404182044.png
While systems with only one CPU core are supported, Sriracha runs best on systems with multiple CPU cores. Systems with even two or four cores enable greatly improved performance versus single core systems.

This screenshot shows Sriracha running on a system with 16 CPU cores. In this case, compared with a single core system, pages were built 15x faster. Pages could be built 16x faster on 16 core systems, but in this case, PostgreSQL is running on the same system as Sriracha.


 [Reply]
is it possible to add an archive system when the thread amount per board reaches its limit?


>>90
- threads will be locked from any new replies being added and the posting is disabled/omitted, once a thread goes over the max threads count it will be moved to the archive.
- it would be accessed from normal board index pages.
- it won't be accessed from overboard index pages.

this would be an option in the settings like the overboard with its own directory similar to a board.


>>91
Thanks. I've opened a tracking issue for this suggestion:

https://codeberg.org/tslocum/sriracha/issues/131

If anyone else has any thoughts on how this feature should behave, feel free to share.


>>89(OP)
This feature is now supported, starting with Sriracha v2.0.0.


 [Reply]
I currently have my account saved in google password manager and it keeps auto filling it.


>>95(OP)
Thanks for the suggestion. Auto-complete will be disabled for post form fields starting with the next release (v2.0.0).


 [Reply]
have the rotating banner refresh when clicked


Thanks for the suggestion. This is possible by customizing the template extra_logo.gohtml, because the template appears after the banner image. Use JavaScript to add a "click" handler to the banner img element. Use Go HTML template actions to access the list of available banners. All available banners (including ones not just configured for boards) are accessible to custom pages and custom templates via $.Opt.Banners.

The variable $.Opt.Banners is a map populated by refreshBannerCache:

https://codeberg.org/tslocum/sriracha/src/commit/f6a246019581d55f8f7aa695a48629a77eb909ca/internal/server/server.go#L1149

The following Go HTML template code demonstrates how to access the banners which are configured to show for the current board:


>>88
thanks


 [Reply]
could you make the nameblock blue when you sage a thread?


Thanks for the suggestion. Tracking issue:

https://codeberg.org/tslocum/sriracha/issues/130


>>83(OP)
This feature is now supported, starting with Sriracha v1.9.8.


 [Reply]
could you have a 12 hour format for the post date?


Thanks for the suggestion. I will plan on adding support for customizing the date/time format in the next release. Tracking issue:

https://codeberg.org/tslocum/sriracha/issues/129


>>81(OP)
This feature is now supported, starting with Sriracha v1.9.8.


 [Reply]
could there be an option for the board page to auto update once a thread has been posted?


Thanks for the suggestion. Tracking issue:

https://codeberg.org/tslocum/sriracha/issues/124


>>66(OP)
This feature is supported starting with Sriracha v1.9.6. Only imageboard index pages may be auto-refreshed.


 [Reply]
>https://codeberg.org/tslocum/sriracha/issues/122
well i'd like to see support for vichan since it reached its end of life and has a zero day apparently, but to reach that sriracha probably should have feature parity like flags (which i hate) and ids (not post numbers more like what's in 4chan /pol/ which i hate for example) could be added


>>72
I think this covers everything, I also made a bumplocked and cyclical thread:

https://files.catbox.moe/vlerum.zip

If there's still anything missing, please let me know.
Also, probably doesn't matter, but backlinks/reflinks do not show up on the post that's being referenced by default in vichan (it relies on loading a js script in the config), but I'm assuming this shouldn't change anything in the database itself. The database dump was made without this script being loaded.


>>75
Thanks. I've just tested importing posts from the recent dump and things look good. Support for importing vichan posts is now ready for testing.

Until Sriracha v1.9.5 is released, you can try this feature by downloading the latest source code of the main branch and building Sriracha yourself. I've updated the manual to include instructions for importing vichan posts.


Sriracha v1.9.5 is now available, featuring support for importing posts from vichan.


 [Reply]
for replying to the thread poster, could there be an (OP) at the end of it?


Thanks for the suggestion. Do you mean at the end of reflinks? Such as >>73(OP) being rendered as ">>73(OP)(OP)"?


>>74
yes


>>76
This feature will arrive in Sriracha v1.9.5.


1785094725561.png
 [Reply]
Hi,

I'm not quite sure what's causing this behavior, or if it's just something on my end (I suspect it is), but these aren't supposed to show up on desktop view, are they?

I tried clearing cache/cookies, tried Firefox, Chromium, same thing happens.
I assumed this was caused by me being on Linux, because everything looks normal on Windows (no long bar, post hover activates only when you hover over the number), but I've spinned up a linux VM and it's not happening there as well.
The weirdest thing it didn't use to happen on my machine either, when it suddenly started happening after I reloaded a Sriracha instance and now it's happening everywhere.

When looking at the html It seems I'm triggering the mobile view version of the backlinks? I really have no idea why because it happens on different browsers with cache/cookies completely wiped and no extensions installed at all, only user agents should trigger these to appear shouldn't they? Is there anything else that could cause this behavior?

Html I'm seeing:
<a href="/help/res/52.html#54" class="refreply touchreflink" refid="54">&gt;&gt;54</a>


>>60
Sriracha v1.9.0 is now available, which includes the mobile input changes I mentioned. Please refresh your page cache by pressing Shift+Refresh or by long-pressing the refresh button, then give the mobile reflink previews another try. Page scrolling should work now, even when a reflink is tapped.


1785284114399.png
>>61
Hi,

Reflinks are present and I'm still getting
Coarse pointer: false

I figured out what's causing it though, it's only happening when using Moonlight to remote into my machine, it seems Moonlight creates a virtual touch device which is what I'm guessing is triggering this, so it's not really an issue with Sriracha.

>>63
Thanks, scrolling is much less disruptive now.


>>64
Once v1.9.1 is released, Sriracha will rely on coarse pointer detection instead, which should resolve the issue you mentioned. I have also deployed the fix here just now.


Delete Post