Anyone coming to today’s meetup? 🤔
Just added support for deleting and editing arbitrary Twt(s) at anypoint in your timeline. Some things to note:
- I’m not really that happy with the code between
PostHandler()
andDeleteTwtHandler()
anymore 😢 It really needs some major refactoring, and better tests.
- This only works for users (for now), no support for Persona(s) / Feeds sorry.
One side-effect I’ve noticed (which was always the case); an Edited Twt whilst preserves the original timestamp, gets appended to your feed at the bottom of the file. This is counter intuitive when you think about editing text files with a text editor, but it does make sense in the way yarnd
treats feeds as append-only (I had just forgotten). I’m not doing anything about this though.
b98b9 I think the only holes that get that much traffic and eat that much bandwidth would be floodgap or bitreich. You can maintain a phlog and that shouldn’t be eating that much bandwidth per month.
Done
@lyse@lyse.isobeef.org Ahh! I can do that, at least the first part. That’s trivial!
@lyse@lyse.isobeef.org pretty nice colors there 😍
On my blog: Toots 🦣 from 06/17 to 06/21 https://john.colagioia.net/blog/2024/06/21/week.html #linkdump #mastodon #socialmedia #week
Oh boi! 🤦♂️ I totally forgot to put this notice up, and the month has flown by so quickly! 😅 Sorry folks! Hope it’s not too late! ⏰ for our monthly Yarn.social Online Meetup! 🤞
Event: Yarn.social Online Meetup
When: 22nd June 2024 at 12:00pm UTC (midday)
Cadence: 4th Saturday of every Month
Agenda:
Anything we want to talk about. Twtxt, Yarn, self hosting, cool stuff you’ve been working on. chit-chat, whatever 😅
It sure would be nice to get out of this “rate race” one day 🤞
@lyse@lyse.isobeef.org Specifically:
I’d rather suggest to enable the checkbox by default
I’m no longer sure between the discussion(s) how this should behave or look like now 🤣
@movq@www.uninformativ.de Golly, you are right 😅
42km for 42 years: 26.26 miles, 00:11:50 average pace, 05:10:44 duration
crazy run… don’t have a lot of time so i’ll have to remember to complete the thread that i captured in my journal.
#running
Oh no, don’t tempt me. I’ve been on KDE for a while to not tinker and make it possible for my Windows using partner to use my laptop now and then, I’m trying to avoid the dwm/l addiction 🤣
@bender@twtxt.net Yeah I will! I don’t really use Matrix much tbh
@lyse@lyse.isobeef.org Haha 🤣
@lyse@lyse.isobeef.org I’m so confused now 🤣
@movq@www.uninformativ.de me neither 🤦♂️
@bender@twtxt.net Haha @lyse@lyse.isobeef.org exaxrly! 🤣
On my blog: Developer Diary, Desertification and Drought https://john.colagioia.net/blog/2024/06/17/drought.html Real Life in Star Trek, The Game https://john.colagioia.net/blog/2024/06/20/game.html #scifi #startrek #closereading
Forlinx’s New SoM Leverages Rockchip RK3562J Quad-Core Processor
Forlinx Embedded has launched the FET3562J-C SoM, a versatile system on module with an optional 1 TOPS NPU, optimized for a broad range of applications including industrial automation, consumer electronics, smart healthcare, energy, and telecommunications. The FET3562J-C SoM, powered by the Rockchip RK3562J processor with advanced 22nm process technology, features four ARM Cortex-A53 cores operating
Compex Introduces New Wi-Fi 7 Dual-Band Modules: WLE7002E25D and WLT7002E25D-E
Compex Systems has expanded its range of wireless solutions by introducing two new Wi-Fi 7 modules: the WLE7002E25D and the WLT7002E25D-E. These modules are designed to enhance wireless performance and reliability, offering a cost-effective alternative to Wi-Fi 6 modules according to the company. The WLE7002E25D features a standard MiniPCIe form factor, marking it as one
@prologic@twtxt.net phew 😁
@prologic@twtxt.net yep pretty much!
@eldersnake@we.loveprivacy.club Like a “I’m on a public terminal” type thing? Which has the opposite effect? With some helpful descriptive text? 🤔
@eldersnake@we.loveprivacy.club Oh! That’s a bug and pure lack of “form validation!” 😅 Thanks for pointing this out, I’ll fix this tonight 🤞
Could you perhaps just have a check box to do the opposite, like “Don’t remember me”? I’ve seen that a couple of places I think. Sort of an opt in short lived login, if you’re at a public library or something etc.
@prologic@twtxt.net hey mate, all working well here so far. The login issue isn’t really an issue as far as actually logging in goes, rather if I get my password wrong it gives the response error code in console, the response of which contains the HTML for the wrong password page if you inspect it, but on the frontend itself nothing actually happens which is the confusion. Just stays on the login page as if it was never submitted. Am I alone in having this issue as well?
@bender@twtxt.net I do! I think it’s prologic:mills.io
Can we trust the bots not to fake their identity? 🤔
@aelaraji@aelaraji.com Hmmm looks like the core idea is to intercept requests, Inspect the UserAgent
header and respond accordingly.
Hey @movq@www.uninformativ.de !! here’s an article you might find interesting: Blocking Bots with Nginx … this person is actually blocking AI
Bots based on a list of User Agents in an interesting way. 👍
But what would you prefer if you were rethinking the architectural design of your next web app? A bazillion lines of Javascript™ with all kinds of indirections and acrobatics that are impossible to understand? 🤔 – Or just write your web application as a normal set of pages in the Hypermedia Driven Application (HDA) style/architecture, than sprinkle a few
hx-*
attributes and get the same user experience? 😅 #htmx
@aelaraji@aelaraji.com Yeah it’s more along the lines of “everything sucks” at least a bit 🤣
@bender@twtxt.net Actually the video is a reaction to: HTMX Sucks that is originally an essay by Carson Gross (the creator) in the “The worse-is-better design philosophy” and what not style. So No, it isn’t … or at least not in the sense one would get from such a title. 😄
@lyse@lyse.isobeef.org I’ll buy that argument 👌
@lyse@lyse.isobeef.org Can you get an AI to summarize this 🤣
@bender@twtxt.net Hmmm god question 🤣 @shreyan@twtxt.net Can you tell @bender@twtxt.net what my Matrix handle is 🤣
@lyse@lyse.isobeef.org Yeah I’m not a fan of all this YouTube / Discord / Twitch studs 🤣 I was more interested in the presentation itself which is also covered by the cook
Haha yeah that video on htmx sucks is pretty funny really! 🤣 And no it obviously doesn’t suck 😅
@prologic@twtxt.net Watched that one the other day after seeing that much chatter about #HTMX on the feed. And now I’m watching HTMX Sucks - Youtube by the same person (or should I say people?) 😂
127.0.1 (64-bit)
tonight and tested and it worked just fine. Try upgrading and roll that commit back and see if it still repros? 🤔 I'm almost willing to bet this is a bug 🐛
@lyse@lyse.isobeef.org Haha, sadly no, that is the version number Firefox is up to 🤣
Interview with Senior JS Developer 2024 [NEW] - YouTube Bahahahahaha 🤣 So funny!
@lyse@lyse.isobeef.org 10s rule? 🤔
@movq@www.uninformativ.de True! Complexity Budget 👌
@eldersnake@we.loveprivacy.club No worries! Any time 🤗 Sorry it took this long to sort out, I’m not happy about how we did it (work around et all) but yeah if that’s what we have to do, so be it 🤣
@movq@www.uninformativ.de Oh come now, this isn’t the first Browser bug we’ve seen right? 😅
@prologic@twtxt.net Yes very very strange! I truly don’t know where to start on that one 🤣 Must be one of those really weird edge cases. Thanks for your help on this, I can at least post normally now.👌
I’ll check logging in etc tomorrow, time for bed lol 😴
Referer
is /post
then consider that total bullshit, and ignore? 🤔
@eldersnake@we.loveprivacy.club Good good 👍
@eldersnake@we.loveprivacy.club But not me against your pod, so that’s even weirder right? 🤔
Referer
is /post
then consider that total bullshit, and ignore? 🤔
Test
EDIT: Okay, convo works properly now at least
Referer
is /post
then consider that total bullshit, and ignore? 🤔
@prologic@twtxt.net It’s weird though cos I could reproduce it on any of my browsers on either my laptop or phone 🤔
@movq@www.uninformativ.de You wouldn’t believe it, but I’m pretty sure @eldersnake@we.loveprivacy.club and I found a nasty little bug in Firefox 126.0.1
🤣
Referer
is /post
then consider that total bullshit, and ignore? 🤔
@eldersnake@we.loveprivacy.club I just installed 127.0.1 (64-bit)
tonight and tested and it worked just fine. Try upgrading and roll that commit back and see if it still repros? 🤔 I’m almost willing to bet this is a bug 🐛
Referer
is /post
then consider that total bullshit, and ignore? 🤔
@prologic@twtxt.net Firefox 126.0.1 is my primary
Referer
is /post
then consider that total bullshit, and ignore? 🤔
What browser and version is this btw? Not sure if you mentioned?
Referer
is /post
then consider that total bullshit, and ignore? 🤔
@eldersnake@we.loveprivacy.club Fuck’n hell 🤣 This has to be a browser bug!
Referer
is /post
then consider that total bullshit, and ignore? 🤔
@prologic@twtxt.net Fix works!
Test
Referer
is /post
then consider that total bullshit, and ignore? 🤔
@eldersnake@we.loveprivacy.club Looks legit 👌
Referer
is /post
then consider that total bullshit, and ignore? 🤔
Okay just pushed:
* aa2f3ae9 - (HEAD -> main, origin/main) Workaround for this invalid Referer BS (6 seconds ago) <James Mills>
Referer
is /post
then consider that total bullshit, and ignore? 🤔
@prologic@twtxt.net Woops my blockquote got mangled but you get the gist haha
Referer
is /post
then consider that total bullshit, and ignore? 🤔
@prologic@twtxt.net I was wondering if my reverse proxy could cause something but it’s pretty standard…
server {
listen 80; server_name we.loveprivacy.club;
location / {
return 301 https://$host$request_uri;
<a href="https://txt.sour.is/search?tag=proxy_pass">#proxy_pass</a> http://127.0.0.1:8000;
}
}
server {
listen 443 ssl http2;
server_name we.loveprivacy.club;
ssl_certificate /etc/letsencrypt/live/we.loveprivacy.club/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/we.loveprivacy.club/privkey.pem;
client_max_body_size 8M;
location / {
proxy_pass http://127.0.0.1:8000;
}
}
Should I just code in a work-around? If the Referer
is /post
then consider that total bullshit, and ignore? 🤔
Why would a Web Browser set the Referer
header incorrectly?! 🤔
Can’t reproduce with Iridium either.
Can’t reproduce with Firefox.
Test
A initial post, reply and conv -> post (bottom of page) and nothing 🤔 All 6 requests are POST /post
followed by a GET <from>
where ever I was coming from. Hmmm 🧐 This is nuts 🌰
Test
Test
Test
/post
) on either the POST
or the GET
🤔
@eldersnake@we.loveprivacy.club Yeah no worries!
You can see here, at least, htmx knows what the current URL is:
HX-Current-URL: https://we.loveprivacy.club/conv/vcpt7gq
Referer: https://we.loveprivacy.club/post
But the freak’n browser is setting the wrong value for Referer
. There is simply no way to be on the /post
endpoint normally anyway.
/post
) on either the POST
or the GET
🤔
@prologic@twtxt.net Firefox but it happens on Brave and Chromium on my laptop, or any browser (Brave, Chromium, Vanadium) I try on my Android phone.
/post
) on either the POST
or the GET
🤔
What Browser is this again? Does it happen with any other browser?
/post
) on either the POST
or the GET
🤔
@prologic@twtxt.net Sorry, my messages don’t get included in the current convo unless I tag you. Guess something gets lossed in translation with this weird posting issue. ANYWAY, it is rather perplexing. Clearly only an issue on my Pod, but what could the source of it be 🤔
/post
) on either the POST
or the GET
🤔
@eldersnake@we.loveprivacy.club Ahh missed this. Fuck, that’s just silliness and not right. wtf?!
The POST /post
XHR (that is being run by htmx) should never, ever be Referer: .../post
🤦♂️
For example, this is what you should see:
Yeah sorry just realised, but just checked again and the referrer is the same (/post
) on either the POST
or the GET
🤔
@eldersnake@we.loveprivacy.club I mean on the POST /post
request itself. That’s the Referer
that’s looked up and used as the redirect.
Testing
@prologic@twtxt.net Okay lemme see
The only way this is possible is if the Referrer
is /post
and not /
or /discover
like it should be. Can we confirm/deny this if you inspect the POST /post
requests? 🤔
See this code
if htmx.IsHTMX(r) {
htmx.NewResponse().
Location(RedirectRefererURL(r, s.config, "/")).
Write(w)
} else {
http.Redirect(w, r, RedirectRefererURL(r, s.config, "/"), http.StatusFound)
}
There is only one explanation for this… Lemme see…