« first day (1132 days earlier)      last day (331 days later) » 

12:05 AM
Idea: when using vyncode, it tries all versions to find which gives the least bits
And switches to that when generating the answer template
 
 
2 hours later…
1:36 AM
Congratulations on reinventing metagolfscript
 
MGS is inventing a language specifically for a challenge
I'm talking about automating something that can be manually done anyway
Vyncode is not MGS
And being able to use the different versions of vyncode isn't MGS either
 
it's definitely not mgs but i would say it's getting close to actively facilitate it
but if there's going to be multiple versions anyways i wouldn't say it's a huge deal
 
The only difference in vyncode versions is the corpus and maybe the prediction algorithm used
It's all the same range coding algorithm just with different and possibly better data
 
!!/status
 
@emanresuA I am eating some strange canned meat.
 
 
4 hours later…
6:00 AM
Lyxal pushed a commit to Vyxal/v3-add-a-bunch-of-things: Update codepage.txt
Lyxal pushed a commit to Vyxal/v3-add-a-bunch-of-things: Update Modifiers.scala
Lyxal pushed a commit to Vyxal/v3-add-a-bunch-of-things: Update Lexer.scala
 
Not me once again changing the modifier characters for grouping lambdas
ߣ for single item lambda
 
github-actions[bot] pushed a commit to Vyxal/v3-add-a-bunch-of-things: Refresh element documentation from recent commit
 
Uh oh it seems to screw up rtl writing
⸠ maybe instead
 
Lyxal pushed a commit to Vyxal/v3-add-a-bunch-of-things: Update ModifierTests.scala
Lyxal pushed a commit to Vyxal/v3-add-a-bunch-of-things: Update Modifiers.scala
Lyxal pushed a commit to Vyxal/v3-add-a-bunch-of-things: Update Lexer.scala
Lyxal pushed a commit to Vyxal/v3-add-a-bunch-of-things: Update info.txt
Lyxal pushed a commit to Vyxal/v3-add-a-bunch-of-things: Update codepage.txt
github-actions[bot] pushed a commit to Vyxal/v3-add-a-bunch-of-things: Refresh element documentation from recent commit
 
That's what I call "making changes on mobile"
 
 
5 hours later…
11:17 AM
I swear I was going to do something tonight and well now I forgot
 
trolling?
 
no no something development related
eh I'll just play clone hero I think
haven't done that for a while, already have everything set up, and very grindable
and of course I manage to change my keyboard layout to APL
 
11:48 AM
nice
 
!!/status
 
@Ginger I am doing some warcrimes.
 
ಠ_ಠ
 
@VyxalBot good bot
 
!!/groups members member
 
12:01 PM
@Ginger Members of group member: Ginger, Seggan, lyxal, hyper-neutrino, emanresu A, Niko, Jacob, The Thonnu, Steffan, mathcat, zoomlogo, parz
 
hrm
there are definitely fewer regular contributors than that
also, uh, our GH pages deployment failed
 
mm which one
 
oh that's fixed in #1741
 
cool
which will be merged when?
:p
 
12:04 PM
@Ginger when we decide how we want to handle transposition of infinite lists :p
 
that does not mean anything to me
 
if you did more code golf, it would :p
 
imagine
 
do you know what transposing a list means?
 
I do not
 
12:07 PM
 
ah
and how'd that work with infinite lists?
 
something to do with anti-diagonals
but there's questions about whether it should work on infinite number of rows of finite length
 
and if so, how
it is worth noting that at worst it's just extra bytes if you'd happen to have a use for it, since it shouldn't hang if you manually truncate the output to the known maximum length
 
12:47 PM
right now the 05ab1e algortihm is used
which apparently doesn't work on infinite rows of finite length
a digraph for infinite of finite was suggested
which I think is the best way to proceed
and is for when we get to a stage where infinite list digraphs are a thing that can be considered
 
how would the digraph work
some kind of heuristic?
 
1:33 PM
there's syntax examples in the readme?
how the hell don't I remember this?
 
Lyxal pushed a commit to Vyxal/Lyxal-patch-1: Update README.md
Lyxal created branch Lyxal-patch-1 in Vyxal/Vyxal
Lyxal opened pull request #1760 (Update README.md) in Vyxal/Vyxal
Lyxal pushed a commit to Vyxal/main: Update README.md
Lyxal pushed a commit to Vyxal/main: Merge pull request #1760 from Vyxal/Lyxal-patch-1
Lyxal merged pull request #1760 (Update README.md) in Vyxal/Vyxal
Lyxal deleted branch Lyxal-patch-1 in Vyxal/Vyxal
 
!!/status
 
@Ginger I am doing a nice long walk to earn some SWEAT.
 
ick
 
@VyxalBot bro really be doing crypto
 
1:44 PM
> I am doing cryptography
!!/help
 
I'm Vyxal Bot 2.0.0 made by Ginger and Vyxal Corp.
All of my commands start with !!/
If you want help for a specific command, do !!/help <command name>.
New to Vyxal? Try !!/info for more information.

Command list: amilyxal, blame, coffee, cookie, die, goodbye, groups, hello, help, hug, idiom, info, issue, maul, permissions, ping, prod, pull, register, repos, run, status, sus
 
!!/blame
 
@Ginger It was Niko's fault!
 
cool
me when niko oneshot breaks vyxal
 
not to be confused with the code golf user also named niko
 
1:47 PM
of course
!!/help idiom
 
@Ginger !!/idiom add __name__ `code` "Description" tag tag tag...: Add an idiom to the idiom list.
 
 
4 hours later…
5:36 PM
!!/blame
 
@TheThonnu It was Steffan's fault!
 
!!/status
 
@Ginger I am reading My Immortal to Ginger. Good thing they don't know where I keep my off switch- oh wait.
 
you fool
 
6:09 PM
GingerIndustries pushed a commit to VyxalBot2/more-statuses-2-electric-boogaloo: More statuses!
GingerIndustries created branch more-statuses-2-electric-boogaloo in Vyxal/VyxalBot2
GingerIndustries opened pull request #71 (More statuses!) in Vyxal/VyxalBot2
GingerIndustries pushed a commit to VyxalBot2/more-statuses-2-electric-boogaloo: Update statuses.txt
 
6:28 PM
10 messages moved to Sandbox
 
6:43 PM
@lyxal me after never doing that
 
ysthakur approved #71 (More statuses!)
 
6:56 PM
!!/amiadmin
 
Sorry Ginger, I'm afraid I can't do that.
GingerIndustries pushed a commit to VyxalBot2/more-statuses-2-electric-boogaloo: Update data/statuses.txt
GingerIndustries merged pull request #71 (More statuses!) in Vyxal/VyxalBot2
GingerIndustries pushed a commit to VyxalBot2/dev: Merge pull request #71 from Vyxal/more-statuses-2-electric-boogaloo
GingerIndustries deleted branch more-statuses-2-electric-boogaloo in Vyxal/VyxalBot2
 
!!/pull
 
@Ginger Restarting...
Ah'll be bahk.
 
very good
 
Well, here we are again.
 
 
2 hours later…
9:10 PM
ysthakur pushed a commit to Vyxal/v3-tests-yaml: Use circe-yaml
github-actions[bot] pushed a commit to Vyxal/v3-tests-yaml: Scalafix changes
 
!!/status
 
@Ginger I am doing origami. My latest creation is called "crumpled ball of paper."
 
ooh, a new one!
 
Insert meme of Leonardo DiCaprio pointing at a thing
Me when VyxalBot uses one of my statuses
@VyxalBot Do we really need to be notified about every single commit?
 
lyxal said yes
 
9:23 PM
Hrmph
 
10:04 PM
@user as a matter of fact yes
If you'd seen my justification for asking for it, you'd understand why
Basically, in order to get version 3 rolling with a bit more momentum, I'm thinking less PRs more just commit to one branch
Because PRs take time to resolve and mean that other things can't really be added at the same time without the risk of merge conflicts
But then if there's no PRs to keep track of what's being added, how will people know what's happening?
Hence why individual commits are being reported
If there's ever a block of commits that is somewhat spam, it can always be moved to trash
Which y'all can do given that basically everyone is a room owner here
Commit reporting is a good solution for the current stage of "adding something might completely change everything else in version 3"
Which isn't very efficient with the PR system
And also, commit reporting allows me to easily see what's happening around the organisation
Not all commits get reported in email form, and when there's a lot of emails, it's easy to just ignore the notifications
At least here, the transcript is something I 100% read every day
 
10:39 PM
Lyxal approved #1595 (Create tests.yaml and an accompanying test suite)
 
11:01 PM
ysthakur pushed a commit to Vyxal/v3-tests-yaml: Move small classes to top of YamlTests.scala
ysthakur enqueued pull request #1595 (Create tests.yaml and an accompanying test suite) in Vyxal/Vyxal
github-merge-queue[bot] pushed a commit to Vyxal/gh-readonly-queue: Merge pull request #1595 from Vyxal/v3-tests-yaml
ysthakur pushed a commit to Vyxal/version-3: Start on tests.yaml and YamlTests suite
ysthakur pushed a commit to Vyxal/version-3: Merge branch 'version-3' into v3-tests-yaml
ysthakur merged pull request #1595 (Create tests.yaml and an accompanying test suite) in Vyxal/Vyxal
ysthakur pushed a commit to Vyxal/version-3: Merge branch 'version-3' into v3-tests-yaml
Lyxal deleted branch gh-readonly-queue/version-3/pr-1595-8304cc6c8f7b352c46a2dac435c68e4693093d8a in Vyxal/Vyxal
ysthakur deleted branch v3-tests-yaml in Vyxal/Vyxal
ysthakur pushed a commit to Vyxal/version-3: Merge pull request #1595 from Vyxal/v3-tests-yaml
 
@Ginger I thought you fixed the thing where it reports every merge commit
 
uh, I did
or I thought I did
15 messages moved to ­Trash
hopefully that was a fluke
 
11:36 PM
ysthakur pushed a commit to Vyxal/v3-add-a-bunch-of-things: Make QuitException for Q
 
11:46 PM
ysthakur pushed a commit to Vyxal/v3-add-a-bunch-of-things: Implement transposeSafe
ysthakur pushed a commit to Vyxal/v3-add-a-bunch-of-things: Merge branch 'version-3' into v3-add-a-bunch-of-things
 

« first day (1132 days earlier)      last day (331 days later) »