INeedMana

First Video (PeerTube): https://makertube.net/w/cQECfDkuLGR9eUQquUEo4K
First Video (YouTube): https://www.youtube.com/watch?v=CyjumVTWtJA

nlnet announcement: https://nlnet.nl/project/GestureTyping/

wiki article: https://github.com/HeliBorg/HeliBoard/wiki/Background-Gesture-Data-Gathering

mastodon: https://mstdn.social/@theeclecticdyslexic

matrix: https://matrix.to/#/@eclexic:matrix.org

codeberg: https://codeberg.org/eclexic

Rise of the Lazy Gamemaster is a stand-alone book for lazy and aspiring lazy gamemasters. You don't need any of the previous books to get tremendous value out of Rise of the Lazy Gamemaster. It stands well side by side with other Lazy GM books, bringing new angles to the concept of lazy gamemastering and new tools to help you prepare and run awesome games.

This book isn't a rewrite of Return of the Lazy Dungeon Master. Return focuses on three main lazy GM activities: preparing your game, running your game, and thinking about your game.

Rise of the Lazy Gamemaster breaks down the concepts of lazy gamemastering into the following topics:

• The eight steps of Lazy GM Prep expanded by eight years of experiences and feedback.
• Single session, short, and long campaign prep and execution.
• Adventure types – what works well, where the traps lay, and how to customize the eight steps based on the adventures you're running.
• Quest models – those that work well and those that don't.
• The Lazy GM's Toolkit with sixty tools, tips, and tricks to run your games.
• Example adventure scenarios using the eight steps.
• Piles of random tables and maps to inspire your adventures.

I really liked "the return..." I think that one also might be worth reading

This popped up in my RSS feed and I found it a good read

For some time now I've felt that D&D-like d20 mechanics is cursed to have the problem of inflation. But it was refreshing to see someone else point it out too

As in title. Create post -> link -> paste URL in URL -> nothing happens

I checked after someone else asked, so it's not only me

In Admin->Moderation (/admin/reports) I see a bunch of reports. I open one and I see that the object of report has been already deleted. I think in such case the report should be taken down from the list or grayed out - the latter idea so admin team don't loose history
Or maybe the list should be split in two, like registration does?

Also, I would like to be able to mark reports "resolved" - hidden or grayed out just for me, so I know I already decided that report is not for me. For WebUI maybe store the list of "resolved" reports in browsers' store, so it doesn't pump up the db?

Cross-posted from https://piefed.social/c/historyphotos/p/2012112/stereoscopic-photo-of-three-children-british-mandate-of-palestine-1935

I've heard the system referenced a few times and it's on sale currently

So I'm wondering what it is exactly. I understand it's d6, low crunch, more or less Planescape
But I'd like to know a bit more. Anyone has played it and has some more verbose take?

I've heard a lot about Burning Wheel that made me interested. But is it only good for playing in the included fantasy setting?

How hard is it to hack/reskin it into some other setting?

NLnet grant announcement: https://github.com/Helium314/HeliBoard/issues/2226
NLnet project description: https://nlnet.nl/project/GestureTyping/

Swipe-o-Scope repository: https://codeberg.org/eclexic/swipe-o-scope

CC BY-SA 4.0 license: https://creativecommons.org/licenses/by-sa/4.0/

Article on data anonymization: https://www.science.org/doi/10.1126/sciadv.adn7053

Contact me:
My Mastodon: https://mstdn.social/@theeclecticdyslexic
My Matrix: https://matrix.to/#/@eclexic:matrix.org

Text based tutorial: https://github.com/Helium314/HeliBoard/wiki/Tutorial:-How-to-Contribute-Gesture-Data

It is recommended you install Heliboard through the F-Droid app, unless you know what you are doing!
How to install F-Droid: https://f-droid.org/en/docs/Get_F-Droid/
Heliboard on F-Droid: https://f-droid.org/en/packages/helium314.keyboard/
Heliboard on Github: https://github.com/Helium314/HeliBoard/releases

Gesture typing library links from MindTheGApps:
ARM64: https://gitlab.com/MindTheGapps/vendor_gapps/-/blob/fe250848941171fe339ca9a44bc9a42aefb0be7d/arm64/proprietary/product/lib64/libjni_latinimegoogle.so
ARM: https://gitlab.com/MindTheGapps/vendor_gapps/-/blob/fe250848941171fe339ca9a44bc9a42aefb0be7d/arm/proprietary/product/lib/libjni_latinimegoogle.so
X86_64: https://gitlab.com/MindTheGapps/vendor_gapps/-/blob/fe250848941171fe339ca9a44bc9a42aefb0be7d/x86_64/proprietary/product/lib64/libjni_latinimegoogle.so

---

Other ways to contribute:
Providing packaging scripts for Swipe-o-Scope:

• for Windows
• for macOS
• for Flatpak. This is a big task; Swipe-o-Scope uses QT modules that are not currently supported by the KDE SDK (QTGraphs module). Swipe-o-Scope is also written using the PySide6 python library, rather than in C++. To build Swipe-o-Scope for flatpak, you are probably going to have to talk with KDE developers and the PySide6 baseapp maintainer. You will need them to update the SDK and the baseapp to support PyQTGraph. This is all in addition to needing to know a little about building flatpaks.
• for Linux via means other than Flatpak (e.g. the AUR)

Providing input or code if you are knowledgeable about any of the following:

• gesture typing using hand-designed algorithms... (bonus points if you have worked on a paper or product that you could help us make an open implementation of WITHOUT violating anyone's intellectual property)
• gesture typing using neural nets and constrained compute, such as on mobile devices without TPUs... (unfortunately you may not be able to contribute here effectively until we have the data collected, organised, and released at the end of the collection period)
• the JNI in Android... (bonus points if you have a working knowledge of the AOSP Latin IME JNI library)
• natural language processing for next word prediction, specifically comparing the suitability of a set of candidate words against one another... (either by ngrams or any other low-compute method available to a mobile device with no internet connection)
• building a diverse small-to-medium sized multi-lingual corpus of natural language text we could legally use to simulate context... (not stealing copyrighted content in bulk, like certain companies.)
• making desktop apps more user-friendly... (Swipe-o-Scope doesn't currently give user feedback that would be helpful to anyone that doesn't feel comfortable in a terminal)
• being patient while performing thorough code review and audits of rust code... (the gesture recognition library is most likely to be in rust, despite me being more experienced in other languages, as I am making a bet on it still being popular in a decade or three)

Full disclosure: out of concern for copyright issues and code quality, we will not be accepting ANY LLM generated contributions to this project. Neither in the form of code, nor corpus text. Thank you!

If you work on another on-screen keyboard, have the ability to collect data from it, and you want to add to the data set - you can contact me about some more particulars of the file format. Not all requirements of the file format are obvious and should not be assumed!

We are still in early stages, and this project is likely to continue for quite a while. It may continue well past the end date of me getting paid by the NLnet. Don't hesitate to reach out if you think you can help in some other way! We can use all the help we can get; gesture typing is a hard problem with a very high ceiling. Every little improvement matters!

Remember, even sharing this project around will be helpful at the moment. I can't be boosting this all the places I maybe should be; I have to be working on code, and this video took long enough!

I thought it might get some reach when cross-posted here

First I got notified about Para Bellum. Now I got pinged about a bit of short-fiction.

I think that's cool, I haven't looked into those books but IMO there haven't been much about Desert Wars in the official lore

This post got me thinking: on Discord we've been using "HammerTime tags" so the time in a message was being translated to everyone's local time. Here it would, of course, necessitate everyone to set up their timezone in the settings but apart from that, I guess it could be doable too, right?

I hope it's ok to ask for some feedback here. Of not, please let me know. The rules did not sound like against it

I'm very new to Rust. And while in general my coding background is ok, Rust still feels alien to me. I think I'm just still at "how to think in Rust" part of the curve.

So I would like to ask here for opinions on the following bit of code. I know that those unwrap are too optimistic for production, and I could figure out how to pass io::Error from the function all the way up to the shell. But what are other choices that I don't see?
What would you write differently? What looks like Pythonisms/C++isms? Or is missing the mark completely?

use std::{fs, io};  
use std::path::PathBuf;  
use std::convert::TryFrom;  

use clap::Parser;  
use parquet::file::reader::SerializedFileReader;  
use parquet::record;  
use csv::WriterBuilder;  

#[derive(Debug, Parser)]  
#[command(version, about, long_about = None)]  
struct Args {  
    dir: String,  
    #[arg(default_value = "0")]  
    count: usize  
}  

fn get_files_in_dir(dir: &str) -> Option<Vec<PathBuf>>  
{  
    let dir = fs::read_dir(dir);  
    if dir.is_err() {  
        return None  
    };  
    let files = dir.unwrap()  
        .map(|res| res.map(|e| e.path()))  
        .collect::<Result<Vec<_>, _>>();  
    if files.is_err() {  
        return None  
    }  
    files.ok()  
}  

fn read_parquet_dir(entries: &Vec<String>) ->  impl Iterator<Item = record::Row> {  
    entries.iter()  
        .map(|p| SerializedFileReader::try_from(p.clone()).unwrap())  
        .flat_map(|r| r.into_iter())  
        .map(|r| r.unwrap())  
}  
                            
fn main() -> Result<(), io::Error> {  
    let args = Args::parse();  
    let entries = match get_files_in_dir(&args.dir)  
    {  
        Some(entries) => entries,  
        None => return Ok(())  
    };  


    let mut wtr = WriterBuilder::new().from_writer(io::stdout());  
    for (idx, row) in read_parquet_dir(&entries.iter().map(|p| p.display().to_string()).collect()).enumerate() {  
        let values: Vec<String> = row.get_column_iter().map(|(_column, value)| value.to_string()).collect();  
        if idx == 0 {  
            wtr.serialize(row.get_column_iter().map(|(column, _value)| column.to_string()).collect::<Vec<String>>())?;  
        }  
        wtr.serialize(values)?;  
        if args.count>0 && idx+1 == args.count {  
            break;  
        }  
    }  
    
    Ok(())  
}