There are many interesting things to observe in this recent Twitter exodus (and the boost it is giving to Mastodon’s adoption). One of them is that I haven’t read even once yet about someone who’s “leaving Twitter for Facebook” or something like that: officially, Facebook is no longer a “social media alternative” to Twitter users.
@movq@www.uninformativ.de @eaplmx@twtxt.net there’s an online service for that, https://www.lulu.com/pricing
@eaplmx@twtxt.net Yes, the regardless part is what scares me… In Portugal the major parties want it for general elections, despite what I said above applying to us. There have been talks about a constitutional revision to allow it, but they’re purposefully ignoring that no amount of national legislation is going to make it GDPR-compliant…
@eaplmx@twtxt.net To add to those challenges, there is yet another legal requirement in many electroral systems: it needs to be understandable and scrutinizeable by “random people”. There is an understanding that, in the EU, this requirement exists independently on any specific requirement for it, due to nr. 1 of art. 5 of the GDPR (the “transparent manner” bit).
@eaplmx@twtxt.net @movq@www.uninformativ.de ask me again in an year 🙊
Sometimes I get terrified for some moments with the naïvity of the greedy. As an example, when people advocate AI-generated stuff can/should be copyrightable, under the expectation that they’ll be making some money from that, without realizing about the impact of the repercussions of what they propose, also to themselves…
@prologic@twtxt.net @movq@www.uninformativ.de I lived the first ten years of my life in an apartment, the upstairs neighbors had a piano, the only music played there, at least once a day every day, was Für Elise. She didn’t master the song before I moved, but I think of this every time I hear the song.
SIMON KOFE: “EMBORA EXISTAM VÁRIOS FUNDOS CLIMÁTICOS, TEMOS MUITA DIFICULDADE EM ACEDER-LHES”, uma entrevista ao Governo de um país cuja terra está a desaparecer.
@eaplmx@twtxt.net Well, wow! Only now I am learning about Microsoft Game Shop… But I was a Nibbles player!
Worms 2 was released a quarter of century ago. A game I’ve played countless hours, many of them with a Moonspell CD on the drive, which would make the game play songs from it (specially “Opium”).
Portuguese Prime Minister: In September, he wants a new airport, in October he wants a
@prologic@twtxt.net @movq@www.uninformativ.de I created an issue so we can have this conversation outside of twtxt.
@prologic@twtxt.net @movq@www.uninformativ.de :
Thanks!, reading that was useful.
It seems to me that the choice of ‘relative’ was meant to consider users’ use cases (multi-protocol, moving the feeds from one place to another, etc.), without any added convenience to the clients, specifically. Thus, I’d argue that there is nothing against extending the spec to also allow full paths: current users are unnafected, and we’d be catering for new/other use cases.
Yes, I do realize that would mean this would have to go into a new version of the spec, and clients would have to implement it in order to comply with the new version of the spec.
@prologic@twtxt.net @movq@www.uninformativ.de I’ll need to re isit the old thread to be sure if there isn’t more to it than that, but if multiprotocol is the only reason, then we can allow “relative or full”, so both scenarios are catered for, right?
@prologic@twtxt.net oh, yes, they’ll remain the same (tilde’s being a backup).
@hacker-news@feeds.twtxt.net Uh-oh. Will we finally start focusing on RISC-V?
@lyse@lyse.isobeef.org @tkanos@twtxt.net An interesting setting for an alternative reality fiction novel!
Mappy is a game from 1983, but it was 30 years ago that I’ve seen it for the first time, in a neighbor’s NES.
Three decades later, but at least now I get to play it for as long as I want 😇
As in standards, it would actually be healthy for the twtxt network if it became heterogeneous, with pods running competing implementations (yarn and something else) of the protocol. Perhaps we’re not there yet, but I suppose we should design taking that into account…
@prologic@twtxt.net assuming the pod is running a recent version of yarn, unmodified. But we can assume that…
@prologic@twtxt.net well, this is embarrassing, I manage to reach the result on the web interface, but not to find an URL that will point to them…
@prologic@twtxt.net I suppose https://search.twtxt.net/search?q=%23opev6mq&t=term&f=conv is the right link…
@movq@www.uninformativ.de @prologic@twtxt.net Redirects will work for on feed removals, if the poderator is interested in providing them - it depends on its benevolence and good will. In any case, removals must be implemented somehow (at least in pods operating under EU law), so there’s no downside in implementing it with a redirect option.
Regarding # prev, maybe it is best to recover the old thread (which I think was (#opev6mq)).
@abucci@anthony.buc.ci @prologic@twtxt.net we had a conversation about this a few months ago… While the redirect option is nice to have, I still feel it might not be enough, specially since it depends on the support of the poderator. Having the possibility to point a new feed to a specific old one would help (ie, prev allowing full URIs instead of relative paths, and pods letting users define their feeds prev).
Sorry I’m pulling this topic into an already complex thread ;-), specially when I was supposed to write a proposal for this change, and never did (yet?)…
Hey @prologic@twtxt.net , yarn’s deployment documentation refers to cloudflare, but it isn’t really a requirement, is it? If not, should we enhance this doc to have ‘without cloudflare’ steps?
@prologic@twtxt.net not a priority for me right now, but that’s useful, thanks for the tip!
@prologic@twtxt.net I’m listening… what does that provide beyond what I can get with a cron’d wget?
For those that might be a little bit lost regarding my twtxt presence:
- I host my own twtxt feed here so I can remain independent of 3rd party providers, and “owner of my own feed”. However;
- Currently my feed is being generated and managed at twtxt.net, which allows me, amongst other things, to use goryon, a nice mobile app, to manage my feed (even if twtxt.net’s web interface works pretty well on mobile);
- On a geeky sidenote, I haven’t still set aside the idea of running my own single-user yarn pod instead of relying on twtxt.net, but I didn’t want to postpone this movement any longer, now that there’s a new twitter exodus;
- For historic purposes, you can still find my old twtxts on the old feed, now rotated into a new address;
- Finally, there’s still a twtxt feed of my tweets.
Hi @prologic@twtxt.net, question regarding responsible use of twtxt.net’s services. How much is “too intensive” an use of its endpoints? For eg, an “every minute” fetch of a twt feed is considered OK? (I honestly have no idea about the default frequency of communication between pods and all that…)
@prologic@twtxt.net yes, both point to the same “no credible pathway in place”, which is to say that… finally approving a watered-down measure is not something we should applaud, as, in order to still manage 1.5C, we need more, stronger measures.
@slashdot@feeds.twtxt.net Too bad the article doesn’t remind us that the original target date (when we still didn’t know how bad things really are) was 2030… But sure, let’s pretend the EU is doing something brave, just a couple of days after being warned they’re far from planning to do enough (#mlqubkq)…
@prologic@twtxt.net there’s a new version: https://www.instructables.com/ArduinoPhone-20-an-Open-Source-Mobile-Phone-Based-/
@prologic@twtxt.net tbh, as a maintainer participation only makes sense if your projects are already hosted either in github or gitlab - or if you are starting a new project. In any case, there is still plenty of time to participate!
@prologic@twtxt.net interesting. I don’t really know anything about accessibility needs, but what does the screen zoom on Mac OS do that others, Ubuntu’s for instance, does not?