Let’s play a game of “Fortunately, Unfortunately“. Respond the previous post (the first comment below this post) by replying this post (not the previous post!)
I’ll start with: “I found this website.“
is my phone the only device that has cached bundle’s workspace
@jeffalo does wasteof generate the next message ID sequentially or randomly
So, I had good news and bad news:
After some negotiations with my parents, I have finally acquired my backup phone that hosts Nickel and ChanSpec that they confiscated for an unrelated reason. This means that those two bots will be back in operation, at least tomorrow.
Unfortunately, the negotiation will make me inactive starting at ~4 AM EST. This means that I'll be unable to join Shellfish meetings, since those start at 5 AM.
Note to self: Get a Pi.
Edit: After some more negotiations, my parents agreed to extend my activity to 9 AM! Well, supposedly.
If you ever ratio me, I’ll give you a really hard easy ratio-related problem
“spicy” and “fat” doesn’t seem like a fitting term for the lower-end of an audio spectrum
Pffft, it’s not difficult. Thou just need to substitute words.
If thou desire for something more difficult, how if we don’t use letters?
I bet you guys can't make a sentence without using the letters "a" or "y"!
On my last post:
Not sure when I’ll do it, since I had to overhaul the (currently very simple) init code,
I take it back, it requires an overhaul of the entire source code, especially on the formatting.
I’m thinking of add an interface for my Bridge project to the chat in here.
Not sure when I’ll do it, since I had to overhaul the (currently very simple) init code, but implementing the interface should be a piece of cake now that I’ve learned how the API works.
connect handler error
Traceback (most recent call last):
File "/home/runner/test/venv/lib/python3.8/site-packages/engineio/client.py", line 540, in _trigger_event
return self.handlers[event](*args)
File "/home/runner/test/venv/lib/python3.8/site-packages/socketio/client.py", line 685, in _handle_eio_connect
self._send_packet(self.packet_class(
File "/home/runner/test/venv/lib/python3.8/site-packages/socketio/client.py", line 543, in _send_packet
encoded_packet = pkt.encode()
File "/home/runner/test/venv/lib/python3.8/site-packages/socketio/packet.py", line 64, in encode
encoded_packet += self.json.dumps(data, separators=(',', ':'))
File "/nix/store/p21fdyxqb3yqflpim7g8s1mymgpnqiv7-python3-3.8.12/lib/python3.8/json/__init__.py", line 234, in dumps
return cls(
File "/nix/store/p21fdyxqb3yqflpim7g8s1mymgpnqiv7-python3-3.8.12/lib/python3.8/json/encoder.py", line 199, in encode
chunks = self.iterencode(o, _one_shot=True)
File "/nix/store/p21fdyxqb3yqflpim7g8s1mymgpnqiv7-python3-3.8.12/lib/python3.8/json/encoder.py", line 257, in iterencode
return _iterencode(o, 0)
File "/nix/store/p21fdyxqb3yqflpim7g8s1mymgpnqiv7-python3-3.8.12/lib/python3.8/json/encoder.py", line 179, in default
raise TypeError(f'Object of type {o.__class__.__name__} '
TypeError: Object of type Response is not JSON serializable
help?
Today, we gathered here to mourn our lost browser. The browser that kickstarted the Internet into what we have now.
On its almost 3 decades lifetime, this program has had a lot of ups and downs. Lawsuits, competitions from others, security problems, etc. And just today, after its 27-year long journey, this aging piece of software has now sent its last request, now set aside into its retirement and the underdue obsolescense.
Rest in peace, Internet Explorer. You will always be missed.