GitHub - lmorchard/feed-to-mastodon: A command-line tool that fetches RSS/Atom feeds and posts new entries to Mastodon with customizable templates. https://github.com/lmorchard/feed-to-mastodon #OpenSource #automation #mastodon #GitHub #claude #golang #feed #RSS #AI
GitHub - lmorchard/feed-to-mastodon: A command-line tool that fetches RSS/Atom feeds and posts new entries to Mastodon with customizable templates. https://github.com/lmorchard/feed-to-mastodon #OpenSource #automation #mastodon #GitHub #claude #golang #feed #RSS #AI
Also on the topic of #hytale : that flatpak shit they've thrown at us linux users is just bad. Not only didn't it install for me until I ran the flatpak command myself in an terminal bc it needs some random ass dependencies, no, it also contains just an plain #golang blob, compiled with #wails and #vuejs ; where all assets are INSIDE the binary.
Also for those out of the know: golang typically compiles statically so no dependencies, and wails is pretty-much dependency free and can use your systems browser to do all the displaying stuff for you.
Also also: why tf do you NEED access to my home dir while aparently downloading everything in an just-fine flatpak-managed storage place? Even your downloads are placed there! I can't even fucking CHANGE THE DOWNLOAD FOLDER. I have an SEPERATE LVM DISK for my damn games, I want them to be there! But nope: flatpak is shitty and wants to live either in /var or ~/.var, and hytale dosn't care.
Why can't we just all agree to use appimage? So much nicer to use.
#rant #sorrybutnotsorry #linux #archlinux #pleaserespectmysystem
Also on the topic of #hytale : that flatpak shit they've thrown at us linux users is just bad. Not only didn't it install for me until I ran the flatpak command myself in an terminal bc it needs some random ass dependencies, no, it also contains just an plain #golang blob, compiled with #wails and #vuejs ; where all assets are INSIDE the binary.
Also for those out of the know: golang typically compiles statically so no dependencies, and wails is pretty-much dependency free and can use your systems browser to do all the displaying stuff for you.
Also also: why tf do you NEED access to my home dir while aparently downloading everything in an just-fine flatpak-managed storage place? Even your downloads are placed there! I can't even fucking CHANGE THE DOWNLOAD FOLDER. I have an SEPERATE LVM DISK for my damn games, I want them to be there! But nope: flatpak is shitty and wants to live either in /var or ~/.var, and hytale dosn't care.
Why can't we just all agree to use appimage? So much nicer to use.
#rant #sorrybutnotsorry #linux #archlinux #pleaserespectmysystem
There's a new release of #epuppy available: version 0.0.8.
It adds a new flag to create a default config and it fixes a bug with page breaks in epub files generated using mobitool.
https://codeberg.org/scip/epuppy/releases/tag/v0.0.8
#golang #epub #ebook #ebookreader #commandline #cli #terminal #tui #linux
There's a new release of #epuppy available: version 0.0.8.
It adds a new flag to create a default config and it fixes a bug with page breaks in epub files generated using mobitool.
https://codeberg.org/scip/epuppy/releases/tag/v0.0.8
#golang #epub #ebook #ebookreader #commandline #cli #terminal #tui #linux
As a bit of a diversion, I somehow ended up working through the #golang #tutorial this weekend.
I don't remotely consider myself much of a programmer. Possibly, a bit of a code janitor. I was just looking for a bit of an introduction to an unfamiliar language.
I have to say, #Go has some really clear, clean, and helpful #Documentation for a beginner wanting to get started with the language. I'm impressed.
Between the interactive tour(https://go.dev/tour/welcome/1) and the Getting Started tutorial(https://go.dev/doc/tutorial/), I honestly had fun dipping my toes into Go.
Additional resources:
https://gobyexample.com/
At this point, I think I'm satisfied with the vim-go plugin providing me with a stoopid simple template for prototyping very basic example programs.
It's definitely not a #REPL like I'm used to with #Python or running from the #CLI; but, it's a bit of a useful workflow to get started. *shrug*
These keybindings help a bit:
```
augroup go
autocmd!
autocmd BufNewFile,BufRead *.go setlocal
\ noexpandtab
\ tabstop=4
\ shiftwidth=4
autocmd FileType go nmap <leader>b :<C-u>call <SID>build_go_files()<CR>
autocmd FileType go nmap <leader>d <Plug>(go-doc)
autocmd FileType go nmap <leader>f <Plug>(go-fmt)
autocmd FileType go nmap <leader>i <Plug>(go-info)
autocmd FileType go nmap <leader>l <Plug>(go-lint)
autocmd FileType go nmap <leader>r <Plug>(go-run)
autocmd FileType go nmap <leader>v <Plug>(go-vet)
autocmd FileType go nmap <leader>t <Plug>(go-test)
autocmd FileType go nmap <Leader>c <Plug>(go-coverage-toggle)
augroup END
```
Anyone know why the #golang library causes applications to crash on #GrapheneOS when memory tagging is enforced?
(Example application "Orbot")
The related issue was closes as a kinda won't fix: https://github.com/guardianproject/orbot-android/issues/1026
Anyone know why the #golang library causes applications to crash on #GrapheneOS when memory tagging is enforced?
(Example application "Orbot")
The related issue was closes as a kinda won't fix: https://github.com/guardianproject/orbot-android/issues/1026
