Hackers' Pub

Syntax	Description	Examples
`"` keyword `"`	Finds the string within quotes, including spaces. Case-insensitive. (Escape quotes inside with `\"`)	`"Hackers' Pub"`
`from:` handle	Finds content written by the specified user.	`from:hongminhee` `from:hongminhee@hollo.social`
`lang:` ISO 639-1	Finds content written in the specified language.	`lang:en`
`#` tag	Finds content with the specified tag. Case-insensitive.	`#HackersPub`
condition condition	Finds content that satisfies both conditions on either side of the space (logical AND).	`"Hackers' Pub" lang:en`
condition `OR` condition	Finds content that satisfies at least one of the conditions on either side of the OR operator (logical OR).	`#HackersPub OR "Hackers' Pub" lang:en`
`(` condition `)`	Combines the operators within the parentheses first.	`(#HackersPub OR "Hackers' Pub" OR "Hackers Pub") lang:en`

rahix @rahix@chaos.social

12/11/2025, 1:28:19 PM

Public

@q3kq3k @whitequark✧✦Catherine✦✧ @ignaloidasIgnas Kiela Not in the screenshot: If the JSON contains any whitespace, the parsing result "may contain errors"

q3k @q3k@hackerspace.pl

12/11/2025, 1:32:05 PM

Public

@rahix @whitequark✧✦Catherine✦✧ @ignaloidasIgnas Kiela Holy shit I missed this. What the fuck.

Restrictions and Requirements
Because of system behavior of the SIMATIC PLC and because datatypes of strings / characters have been chosen to be String / Byte (because of memory optimization) it is only possible to serialize/ deserialize streams with ASCII encoding. Any other encoding will lead to undefined behavior and might cause issues while serializing/ deserializing.
Additionally, the length of strings (e.g. values of XML / JSON elements/ attributes) is restricted to a maximum of 256 characters. There is no workaround for these restrictions; if the functionality is required the user must adjust the library code.

Requirements JSON
The incoming JSON stream must be formatted in a compressed form:
• Line breaks are not allowed
• No spaces or whitespaces outside of values

This format has been chosen to optimize the use of memory and performance for serialization and deserialization.
Serialization will always output a compressed format. When the input is not compressed the behavior of the function is undefined and might lead to issues while deserializing.

If you have a fediverse account, you can quote this note from your own instance. Search https://social.hackerspace.pl/users/q3k/statuses/115701181669150560 on your instance and quote it. (Note that quoting is not supported in Mastodon.)