@φ @win vim is a successor of ed. It uses ex internally. Though ed is a line editor and vim is a screen editor. I use vim daily though I would not wish ed on someone I don't like. Though sed is a stream editor and I use that regularly as well. All three are related. And both sed, vi and vim were based on ed.
@φ @win I have no idea as I have only used friendica and mastadon. I am using a modified scheme on frio called bookface though that would not effect anything unless you were on my server. I believe.
@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win that is weird. I would expect some consistency though I released when I installed the scheme that it would mainly effect my server.
@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win Fedi is full of css. Look in the source to the many interfaces. Now, I can only speak of friendica as that is what I have installed on my server. Though the template files for Smiley3 (the template engine used by friendica) strongly uses css. They are in the themes and schemes to those themes.
Now, yes, you could write an app that accessed the api and never process any css. And not be a webui at all. Though most of what I have seen uses a webview and does use the css that is available for theming. Personally, I do not like any of the apps I have found and use a browser to access my instance. The
... show more
@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win Fedi is full of css. Look in the source to the many interfaces. Now, I can only speak of friendica as that is what I have installed on my server. Though the template files for Smiley3 (the template engine used by friendica) strongly uses css. They are in the themes and schemes to those themes.
Now, yes, you could write an app that accessed the api and never process any css. And not be a webui at all. Though most of what I have seen uses a webview and does use the css that is available for theming. Personally, I do not like any of the apps I have found and use a browser to access my instance. The apps just leave so much out, they are barely functional.
Now the transport layer of course does not use css. Because css is for the view. If you look at the attached screenshot from a terminal instance of my ssh connection to my VPS you will see that there are plenty of css files and more than those be sure. Those are just the basic css files for frio and the others are for the schemes for enhancing frio (a friendica theme).
@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win Thank you, I am well aware of that. I am a developer. What I was trying to explain to you is that as @φ @win mentioned they could see the changes that the schemes caused to the tags, and you could not. So they are obviously using a client that uses a webview. So the css propagates. You are likely not using a client that uses a webview, or the webview in your client supplies its own css.
This is not uncommon at all.
Now, as I mentioned, of course the transport does not use css. That is not were the view is established or maintained.
Now anything that I view from other sources on my view will only be rendered against my theme. Though this obviously was not the case for the akkoma client being used by the person that asked me why the tags looked like that. The only thing that makes the tags look like that is the css files in the scheme I added.
i'm also a developer and you seem to have woefully misunderstood how fedi clients work. i'm pretty sure we're all using the web frontend of our respective server software (if we weren't, why would a client use a webview, and if it did, where would this css be propagating from, what??). fedi posts have a text content in a specific format—on friendica, probably html, and on akkoma and misskey, markdown. usually, the markdown parsers parse @-mentions and turn them into links that link to the user's profile, however, since friendica uses html and not markdown, the anchor tags stay as they are. for some reason, on misskey, they don't. this is why i'm confused, because last time i checked, they did show like that.
There is limited markdown support in fediverse implementations but if i remember correctly it's expected that a Note's content is actually in HTML unless it's declared as something else. I have yet to see that in the wild though, I know misskey converts everything to html and then has their own misskeysummary (and other related fields) that are the RAW version without any formatting (so mentions just look like @x@whatever instead of being converted into href.)
2) kitsunes.club for some reason does not have authorized fetch enabled for requesting objects. it only signs requests to fetch stuff from other instances. i should probably fix that
@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win Yes, fair enough. It would not be the actual css files that would propagate. It would be the generated markup. And to tell you the truth I do not know what actually exchanges in the transport layer. As 3 weeks ago I had no idea that Fedi even existed and I just put this server together last week. I have not had time to examine the code base.
Though what I do know is that the only thing that influences the appearance of those tags is the css in the bookface scheme. Some how that propagated to the other users client. So the client had to have received the generated html from my server. Unless you c
... show more
@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win Yes, fair enough. It would not be the actual css files that would propagate. It would be the generated markup. And to tell you the truth I do not know what actually exchanges in the transport layer. As 3 weeks ago I had no idea that Fedi even existed and I just put this server together last week. I have not had time to examine the code base.
Though what I do know is that the only thing that influences the appearance of those tags is the css in the bookface scheme. Some how that propagated to the other users client. So the client had to have received the generated html from my server. Unless you can think of some other way a client for another server would see changes made by a css file of a theme's scheme?
After I have had time to actually examine the code base it will be apparent. For the moment that is the best explanation I can think of, can you think of a better one?
It really does not make sense. As why would anything besides the content make it to the transport layer? Though, as I said I am tired and I am going to get some rack now.
@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win There is more than one way to implement a webview. In one case a person developing a client might use an electron approach that internalizes everything and just uses what is baked into the app. On the other hand you could use a gtkview, or the Qt equivalent, that would parse the html and css though you would have to incorporate a JavaScript engine to handle that, if you needed or wanted to. It would basically be a special purposed browser.
Though I agree with you, it would not make sense for the html, css and js of the frontend to be bounced around on the transport layer, unless the api gives tha
... show more
@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win There is more than one way to implement a webview. In one case a person developing a client might use an electron approach that internalizes everything and just uses what is baked into the app. On the other hand you could use a gtkview, or the Qt equivalent, that would parse the html and css though you would have to incorporate a JavaScript engine to handle that, if you needed or wanted to. It would basically be a special purposed browser.
Though I agree with you, it would not make sense for the html, css and js of the frontend to be bounced around on the transport layer, unless the api gives that option for client developers? And as I have not looked at the friendica api at all I have no idea what it offers.
So I guess it is just back to the beginning. The style propagated somehow and I have no idea at the moment how. I am good with that. I will look more into it when I actually have time to examine the code base.
The other thing that gets me is that if it was a friendica the gtkview idea could make sense though why would a akkoma client be using the friendica api?
Yeah, it all pretty much does not make sense 😁 but that is okay. There is an answer though at the moment I am not sure what it is. I was surprised to hear that someone not on my server actually saw at least some of the effects of that scheme.
i think we're just misunderstanding each other. i thought we were talking about css files on your server that style the posts.
On the other hand you could use a gtkview, or the Qt equivalent, that would parse the html and css
you wouldn't need to. there's no point loading the entire frontend just to parse a post when you can use the api
The other thing that gets me is that if it was a friendica the gtkview idea could make sense though why would a akkoma client be using the friendica api?
it's not, it's using its own api. it could be that akkoma's html sanitiser just left the html that your server federated pretty much as is, whereas misskey's did something more drastic to it (i haven't seen you use post formatting, i'm not sure what it would do in that case)
@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win Well over my weekend (which is Saturday to next Tuesday) I will be looking more at the code base and api. If I find anything interesting I will bounce it off you ;).
@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win I just got off a 12 hour shift that I have a 1 hour (one way) commute to. So forgive me if I am doing a horrible job of explaining what I mean. I am exhausted, so I am going to get some rack.
φ
in reply to win • • •what
what is that
win
in reply to φ • • •φ
in reply to win • • •win
in reply to φ • • •φ
in reply to win • • •win
in reply to φ • • •φ
in reply to win • • •> ed is the emacs of unix
thats
a sentence
φ
in reply to φ • • •win
in reply to win • • •φ
in reply to win • • •win
in reply to φ • • •i
glkdfglksdfglksdfg
.
wq
φ
in reply to win • • •win
in reply to φ • • •win
in reply to win • • •φ
in reply to win • • •win
in reply to φ • • •win
in reply to win • • •φ
in reply to win • • •EDITOR=edjustto trywin
in reply to φ • • •Unus Nemo
in reply to φ • •φ likes this.
φ
in reply to Unus Nemo • • •Unus Nemo
in reply to φ • •φ likes this.
Unus Nemo
in reply to φ • •φ likes this.
φ
in reply to Unus Nemo • • •Unus Nemo
in reply to φ • •φ likes this.
φ
in reply to Unus Nemo • • •🌸 lily 🏳️⚧️ θΔ ⋐ & ∞
in reply to φ • • •φ likes this.
Unus Nemo
in reply to 🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ • •φ likes this.
Unus Nemo
in reply to 🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ • •φ likes this.
🌸 lily 🏳️⚧️ θΔ ⋐ & ∞
in reply to Unus Nemo • • •φ likes this.
Unus Nemo
in reply to 🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ • •@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win Fedi is full of css. Look in the source to the many interfaces. Now, I can only speak of friendica as that is what I have installed on my server. Though the template files for Smiley3 (the template engine used by friendica) strongly uses css. They are in the themes and schemes to those themes.
Now, yes, you could write an app that accessed the api and never process any css. And not be a webui at all. Though most of what I have seen uses a webview and does use the css that is available for theming. Personally, I do not like any of the apps I have found and use a browser to access my instance. The
... show more@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win Fedi is full of css. Look in the source to the many interfaces. Now, I can only speak of friendica as that is what I have installed on my server. Though the template files for Smiley3 (the template engine used by friendica) strongly uses css. They are in the themes and schemes to those themes.
Now, yes, you could write an app that accessed the api and never process any css. And not be a webui at all. Though most of what I have seen uses a webview and does use the css that is available for theming. Personally, I do not like any of the apps I have found and use a browser to access my instance. The apps just leave so much out, they are barely functional.
Now the transport layer of course does not use css. Because css is for the view. If you look at the attached screenshot from a terminal instance of my ssh connection to my VPS you will see that there are plenty of css files and more than those be sure. Those are just the basic css files for frio and the others are for the schemes for enhancing frio (a friendica theme).
🌸 lily 🏳️⚧️ θΔ ⋐ & ∞
in reply to Unus Nemo • • •Unus Nemo
in reply to 🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ • •@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win Thank you, I am well aware of that. I am a developer. What I was trying to explain to you is that as @φ @win mentioned they could see the changes that the schemes caused to the tags, and you could not. So they are obviously using a client that uses a webview. So the css propagates. You are likely not using a client that uses a webview, or the webview in your client supplies its own css.
This is not uncommon at all.
Now, as I mentioned, of course the transport does not use css. That is not were the view is established or maintained.
Now anything that I view from other sources on my view will only be rendered against my theme. Though this obviously was not the case for the akkoma client being used by the person that asked me why the tags looked like that. The only thing that makes the tags look like that is the css files in the scheme I added.
🌸 lily 🏳️⚧️ θΔ ⋐ & ∞
in reply to Unus Nemo • • •Unus Nemo likes this.
Amber
in reply to 🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ • • •@x@whateverinstead of being converted into href.)Activity Vocabulary
www.w3.orgUnus Nemo likes this.
Amber
in reply to Amber • • •Unus Nemo likes this.
🌸 lily 🏳️⚧️ θΔ ⋐ & ∞
in reply to Amber • • •Unus Nemo likes this.
Amber
in reply to Amber • • •returns me(note, a lot of that was truncated because I didn't find the other fields relevant, you can just run the command to see the full output)
Akatsuki Levi likes this.
🌸 lily 🏳️⚧️ θΔ ⋐ & ∞
in reply to Amber • • •text/x.misskeymarkdownthing2. how can you run that? don't you need authorised fetch?
Amber
in reply to 🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ • • •Unus Nemo
in reply to 🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ • •@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win Yes, fair enough. It would not be the actual css files that would propagate. It would be the generated markup. And to tell you the truth I do not know what actually exchanges in the transport layer. As 3 weeks ago I had no idea that Fedi even existed and I just put this server together last week. I have not had time to examine the code base.
Though what I do know is that the only thing that influences the appearance of those tags is the css in the bookface scheme. Some how that propagated to the other users client. So the client had to have received the generated html from my server. Unless you c
... show more@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win Yes, fair enough. It would not be the actual css files that would propagate. It would be the generated markup. And to tell you the truth I do not know what actually exchanges in the transport layer. As 3 weeks ago I had no idea that Fedi even existed and I just put this server together last week. I have not had time to examine the code base.
Though what I do know is that the only thing that influences the appearance of those tags is the css in the bookface scheme. Some how that propagated to the other users client. So the client had to have received the generated html from my server. Unless you can think of some other way a client for another server would see changes made by a css file of a theme's scheme?
After I have had time to actually examine the code base it will be apparent. For the moment that is the best explanation I can think of, can you think of a better one?
It really does not make sense. As why would anything besides the content make it to the transport layer? Though, as I said I am tired and I am going to get some rack now.
🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ likes this.
🌸 lily 🏳️⚧️ θΔ ⋐ & ∞
in reply to Unus Nemo • • •Unus Nemo
in reply to 🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ • •Unus Nemo
in reply to 🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ • •@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win There is more than one way to implement a webview. In one case a person developing a client might use an electron approach that internalizes everything and just uses what is baked into the app. On the other hand you could use a gtkview, or the Qt equivalent, that would parse the html and css though you would have to incorporate a JavaScript engine to handle that, if you needed or wanted to. It would basically be a special purposed browser.
Though I agree with you, it would not make sense for the html, css and js of the frontend to be bounced around on the transport layer, unless the api gives tha
... show more@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win There is more than one way to implement a webview. In one case a person developing a client might use an electron approach that internalizes everything and just uses what is baked into the app. On the other hand you could use a gtkview, or the Qt equivalent, that would parse the html and css though you would have to incorporate a JavaScript engine to handle that, if you needed or wanted to. It would basically be a special purposed browser.
Though I agree with you, it would not make sense for the html, css and js of the frontend to be bounced around on the transport layer, unless the api gives that option for client developers? And as I have not looked at the friendica api at all I have no idea what it offers.
So I guess it is just back to the beginning. The style propagated somehow and I have no idea at the moment how. I am good with that. I will look more into it when I actually have time to examine the code base.
The other thing that gets me is that if it was a friendica the gtkview idea could make sense though why would a akkoma client be using the friendica api?
Yeah, it all pretty much does not make sense 😁 but that is okay. There is an answer though at the moment I am not sure what it is. I was surprised to hear that someone not on my server actually saw at least some of the effects of that scheme.
🌸 lily 🏳️⚧️ θΔ ⋐ & ∞
in reply to Unus Nemo • • •i think we're just misunderstanding each other. i thought we were talking about css files on your server that style the posts.
you wouldn't need to. there's no point loading the entire frontend just to parse a post when you can use the api
it's not, it's using its own api. it could be that akkoma's html sanitiser just left the html that your server federated pretty much as is, whereas misskey's did something more drastic to it (i haven't seen you use post formatting, i'm not sure what it would do in that case)
Unus Nemo likes this.
Unus Nemo
in reply to 🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ • •@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win Well over my weekend (which is Saturday to next Tuesday) I will be looking more at the code base and api. If I find anything interesting I will bounce it off you ;).
Take Care!
Unus Nemo
in reply to 🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ • •@🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ @φ @win I just got off a 12 hour shift that I have a 1 hour (one way) commute to. So forgive me if I am doing a horrible job of explaining what I mean. I am exhausted, so I am going to get some rack.
Take Care!
🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ likes this.